Re: Is there an equivalent to 40_custom with EFI boot?

On 10/12/22 16:28, Michael D. Setzer II via users wrote: Wondering if possible to add non-Fedora options to EFI boot menu with some method similar to the 40_Custom. Thanks. I've maintained a project on Sourceforge going back to 2004, and it was originally a cd only boot option, but over years

Re: dump/restore?

On 12/11/22 05:22, ToddAndMargo via users wrote: Has dump/restore been superseded with something else? It ain't work right! dump restores a qcows drive as a blank drive https://bugzilla.redhat.com/show_bug.cgi?id=2152393 I don't see how dump would ever work on a qcow file. You can't read

Re: Better way to refresh the Display?

On Sun, Dec 11, 2022 at 11:32 AM Patrick O'Callaghan wrote: > On Sun, 2022-12-11 at 09:21 -0500, Javier Perez wrote: > > Hi > > I have a problem. Oftentimes when I press the button on my KVM to > > return to > > my desktop and Fedora 36, the screen is black and unresponsive. > > I have to log in

Re: chrome hangs

On Sun, Dec 11, 2022 at 5:26 PM Patrick O'Callaghan wrote: > > On Sun, 2022-12-11 at 13:34 -0800, Geoffrey Leach wrote: > > So, no joy. Chrome help suggests closing other apps, and then (the > > ultimate windows fix) reboot. That's given me trouble in the past, > > but I'll try anything :-) > >

Re: genisoimage source

On 12/11/22 17:49, Bill C wrote: Well, more than anything look at it. I notice a lot of attempt to avoid C++ name mangling. That's about it. Maybe get ideas about code. Not really do anything  rpm -i cdrkit*.rpm cd ~/rpmbuild rpmbuild -bp SPECS/cdr* Then the source should be unpacked and

Re: genisoimage source

Well, more than anything look at it. I notice a lot of attempt to avoid C++ name mangling. That's about it. Maybe get ideas about code. Not really do anything  On Sun, Dec 11, 2022, 8:27 PM Samuel Sieb wrote: > On 12/11/22 16:37, Bill C wrote: > > Ok. Might anyone have any suggestions? Maybe

Re: genisoimage source

On 12/11/22 16:37, Bill C wrote: Ok. Might anyone have any suggestions? Maybe docs.fedoraptject.org . That's all I can think of right off the bat. My email client seems to be giving me some trouble tonight. What are you wanting to do with the source? Look at it?

Re: chrome hangs

Reinstalled from live and -- first thing--installed chrome, No problems. Should the problem reoccur I'l delete them, although they are very few. On Sun, Dec 11, 2022 at 5:26 PM Patrick O'Callaghan wrote: > On Sun, 2022-12-11 at 13:34 -0800, Geoffrey Leach wrote: > > So, no joy. Chrome help

Re: Dealing with "Emergency Mode"

FWIW, I reinstalled from live and installed chrome. First reboot survived. Before going into emergency, the last messages had to do with nouveau getting a timeout on some device. BUT, surely if the display controller was flakey, I would not be sending this on gmail, no? On Sun, Dec 11, 2022 at

Re: genisoimage source

Thanks perfect. On Sun, Dec 11, 2022, 7:38 PM Todd Zullinger wrote: > Bill Cunningham wrote: > > On 12/11/2022 6:51 PM, Tom Horsley wrote: > >> For source rpms you need to setup a ~/.rpmmacros file to tell it > >> where to put the unpacked source, then a command like > > The default is

Re: genisoimage source

Bill Cunningham wrote: > On 12/11/2022 6:51 PM, Tom Horsley wrote: >> For source rpms you need to setup a ~/.rpmmacros file to tell it >> where to put the unpacked source, then a command like The default is ~/rpmbuild. There's no need to create ~/.rpmmacros unless you need to change the

Re: genisoimage source

Ok. Might anyone have any suggestions? Maybe docs.fedoraptject.org. That's all I can think of right off the bat. My email client seems to be giving me some trouble tonight. On Sun, Dec 11, 2022, 6:53 PM Tom Horsley wrote: > On Sun, 11 Dec 2022 18:29:26 -0500 > Bill Cunningham wrote: > > >

Re: Dongle not talking again

On Sun, Dec 11, 2022 at 6:45 PM Tom Horsley wrote: > My best theory is that the kernel doesn't properly reset the device > from scratch, but assumes it was left in some state which the old > kernel didn't leave it in. But that's just a wild guess (and I've never > worked up the energy to try

Re: genisoimage source

On 12/11/2022 6:51 PM, Tom Horsley wrote: On Sun, 11 Dec 2022 18:29:26 -0500 Bill Cunningham wrote: cdrkit-1.11-50.fc37.src.rpm. which is what everyone else has. How can I get this installed from a local directory, even though it's a source rpm. Others have had this question, but IDK how they

Re: genisoimage source

On Sun, 11 Dec 2022 18:29:26 -0500 Bill Cunningham wrote: > cdrkit-1.11-50.fc37.src.rpm. which is what everyone else has. How can I > get this installed from a local directory, even though it's a source > rpm. Others have had this question, but IDK how they resolved it. For source rpms you

Re: Dongle not talking again

On Mon, 12 Dec 2022 09:58:07 +1030 Tim via users wrote: > Odd that it's kernel reboots only. I wonder if there's some timing > issue that's different then? My best theory is that the kernel doesn't properly reset the device from scratch, but assumes it was left in some state which the old

Re: genisoimage source

On 12/11/2022 5:03 PM, Barry Scott wrote: [...] And this is the download working: $ dnf download --source cdrkit enabling fedora-source repository enabling fedora-modular-source repository enabling updates-source repository enabling updates-modular-source repository Fedora 37 - Source

Re: Dongle not talking again

On Sun, 2022-12-11 at 17:54 -0500, Tom Horsley wrote: > Shutting down the system then powering back up also fixes the keyboard > but briefly fiddling with the dongle is much faster. I saw USB hub somewhere which had a button on each port. It was a temporary power killer to the nearby port, to

Re: Dongle not talking again

On Sun, 11 Dec 2022 16:39:12 -0600 Roger Heflin wrote: > My logi wireless keyboard/dongle works to get into the bios. So there > would not appear to be any driver needed to operate it, so that would make > me suspect the reboot is more of the cause than anything else. Yea, it always speaks to

Re: Dealing with "Emergency Mode"

You might get more information to show up if you remove the "rhgb quiet" options on the kernel boot line, then a message that comes out just before it decides to do the emergency boot might have useful information. I agree that the most common problem that causes this for me is failing to create

Re: Dongle not talking again

My logi wireless keyboard/dongle works to get into the bios. So there would not appear to be any driver needed to operate it, so that would make me suspect the reboot is more of the cause than anything else. And usb chipsets/connections in my experience aren't the most reliable devices depending

Re: Dongle not talking again

On Mon, 2022-12-12 at 09:00 +1030, Tim via users wrote: > You could try setting a USB port to "always on."  Alternatively, > perhaps you need the opposite?  So the USB port switches off then on > again during a reboot, and resets the dongle. Oops... On motherboards with jumpers you have choices

Re: Dongle not talking again

On Sun, 2022-12-11 at 14:45 -0500, Tom Horsley wrote: > Just got kernel 6.0.12-300.fc37.x86_64, and after rebooting to > get it loaded, my Logitech wireless keyboard dongle wasn't > talking. Unplugged it, plugged it back in, and the keyboard > works again. > > Every few months this happens on a

Re: genisoimage source

On 12/11/2022 5:03 PM, Barry Scott wrote: On 11 Dec 2022, at 21:55, Bill Cunningham wrote: On 12/11/2022 4:07 PM, Tom Horsley wrote: rpm -q -i genisoimage Will print the name of the source rpm (if you look close :-). Sometime the source rpm name is radically different than the binary of

Re: Dealing with "Emergency Mode"

In my experience (and I have debug 100's of emergency mode).The issue is typically a filesystem issue. Either the fstab entry is wrong, or a driver required by a critical filesystem is failing. The ugliest ones are when the issue is inside the initramfs and that issue is causing the root

Re: chrome hangs

On Sun, 2022-12-11 at 13:34 -0800, Geoffrey Leach wrote: > So, no joy.  Chrome help suggests closing other apps, and then (the > ultimate windows fix) reboot.  That's given me trouble in the past, > but I'll try anything :-) Did you disable extensions? That's usually the first thing to try. poc

Re: Dongle not talking again

On Sun, 2022-12-11 at 14:45 -0500, Tom Horsley wrote: > Just got kernel 6.0.12-300.fc37.x86_64, and after rebooting to > get it loaded, my Logitech wireless keyboard dongle wasn't > talking. Unplugged it, plugged it back in, and the keyboard > works again. > > Every few months this happens on a

Re: genisoimage source

On 12/11/2022 5:03 PM, Barry Scott wrote: On 11 Dec 2022, at 21:55, Bill Cunningham wrote: On 12/11/2022 4:07 PM, Tom Horsley wrote: rpm -q -i genisoimage Will print the name of the source rpm (if you look close :-). Sometime the source rpm name is radically different than the binary of

Re: genisoimage source

On 12/11/2022 5:03 PM, Barry Scott wrote: On 11 Dec 2022, at 21:55, Bill Cunningham wrote: On 12/11/2022 4:07 PM, Tom Horsley wrote: rpm -q -i genisoimage Will print the name of the source rpm (if you look close :-). Sometime the source rpm name is radically different than the binary of

Re: genisoimage source

> On 11 Dec 2022, at 21:55, Bill Cunningham wrote: > > > On 12/11/2022 4:07 PM, Tom Horsley wrote: >> rpm -q -i genisoimage >> >> Will print the name of the source rpm (if you look close :-). >> Sometime the source rpm name is radically different than the >> binary of one bit of it. >> >>

Re: genisoimage source

On 12/11/2022 4:07 PM, Tom Horsley wrote: rpm -q -i genisoimage Will print the name of the source rpm (if you look close :-). Sometime the source rpm name is radically different than the binary of one bit of it. Then you should be able to dnf download --source source-rpm-name neither

Re: Dealing with "Emergency Mode"

> On 11 Dec 2022, at 21:43, Geoffrey Leach wrote: > > When things come ungluded on booting,the user is offered a root login, > which seems to be referred to as "Emergency Mode" > > journalctl is suggested as a place to start looking for causes. In the > output there are no priority 0 and 1

Dealing with "Emergency Mode"

When things come ungluded on booting,the user is offered a root login, which seems to be referred to as "Emergency Mode" journalctl is suggested as a place to start looking for causes. In the output there are no priority 0 and 1 (and perhaps 2) problems. Running the reboot with display of the

Re: chrome hangs

On Sun, 11 Dec 2022 09:02:27 -0700 stan via users wrote: > On Sat, 10 Dec 2022 09:06:40 -0800 > Geoffrey Leach wrote: > > > Firefox (which is installed by the install process) runs without any > > problems. > > Does chrome then start successfully after you exit firefox? > > I just had a

Re: genisoimage source

rpm -q -i genisoimage Will print the name of the source rpm (if you look close :-). Sometime the source rpm name is radically different than the binary of one bit of it. Then you should be able to dnf download --source source-rpm-name ___ users

Re: Dongle not talking again

On Sun, 11 Dec 2022 15:13:37 -0500 Go Canes wrote: > but perhaps > you would have fewer issues using a non-external-hub port Nah, it happened just as (in)frequently when I had it plugged directly into the computer. I moved it to the hub after I got tired of having to walk around to the back of

genisoimage source

Is there a rep for non developers of the source fro the fedora version of genioimage. I checked and genisoimage is an rpm of its' own. But where is its' source? I don't mean the official maintainers of the genisoimage project, but the fedora 37 version of genisoimage. I checked

Re: Dongle not talking again

On Sun, Dec 11, 2022 at 2:46 PM Tom Horsley wrote: > > Just got kernel 6.0.12-300.fc37.x86_64, and after rebooting to > get it loaded, my Logitech wireless keyboard dongle wasn't > talking. Unplugged it, plugged it back in, and the keyboard > works again. > > Every few months this happens on a

Dongle not talking again

Just got kernel 6.0.12-300.fc37.x86_64, and after rebooting to get it loaded, my Logitech wireless keyboard dongle wasn't talking. Unplugged it, plugged it back in, and the keyboard works again. Every few months this happens on a kernel update (not on all kernel updates though). At least I have

Re: dump/restore?

You might want to look into qemu img, in using these files, qcows is indeed a sparse file. These can save into a small file, but when expanded fill up your drive with nothing. Qemu-img converts these files I guess. Maybe a qcows user can help. On Sun, Dec 11, 2022, 11:08 AM ToddAndMargo via users

Re: Better way to refresh the Display?

On Sun, 11 Dec 2022 16:30:51 + Patrick O'Callaghan wrote: > I don't know if this is relevant, but how is the KVM connected to the > display? I had one that would remove the HDMI signal on inactive > display inputs, even when they were physically connected, which made > the system think the

Re: dump/restore?

I will say, not looking at the bug report and not being to familiar with qcows, you might be running into a sparse file situation. Like I say, I don't have the bug report in front of me right now. Restoring data without meta data will get you into this. As a side note, I also like fsarchiver and

Re: Better way to refresh the Display?

On 12/11/2022 09:11 AM, Javier Perez wrote: I do not think so, I think I disabled all power saving and screen saving services / settings. I am running XFCE so I do not know if I got them all. Go to the Xfce forum (http://forum.xfce.org/index.php) and ask for help. They're very friendly.

Re: Better way to refresh the Display?

On Sun, 2022-12-11 at 09:21 -0500, Javier Perez wrote: > Hi > I have a problem. Oftentimes when I press the button on my KVM to > return to > my desktop and Fedora 36, the screen is black and unresponsive. > I have to log in through SSH and restart lightdm (systemctl restart > lightdm) > Problem

Re: Better way to refresh the Display?

On Sun, Dec 11, 2022 at 10:56 AM stan via users < users@lists.fedoraproject.org> wrote: > On Sun, 11 Dec 2022 09:21:09 -0500 > Javier Perez wrote: > > > Hi > > I have a problem. Oftentimes when I press the button on my KVM to > > return to my desktop and Fedora 36, the screen is black and > >

Re: dump/restore?

On 12/11/2022 8:22 AM, ToddAndMargo via users wrote: Has dump/restore been superseded with something else? It ain't work right! dump restores a qcows drive as a blank drive https://bugzilla.redhat.com/show_bug.cgi?id=2152393 On 12/11/22 07:58, Bill Cunningham wrote: > I love dump/restore.

Re: Are Meta/Facebook servers using Fedora Linux?

> I often recommend Fedora Server anytime I see folks using RHEL or > CentOS. I don't understand why organizations run that antique software > that is no longer in development. Fedora provides modern software and > is in active development with continuous bug fixes. > > The answer is very easy. If

Re: chrome hangs

On Sat, 10 Dec 2022 09:06:40 -0800 Geoffrey Leach wrote: > Firefox (which is installed by the install process) runs without any > problems. Does chrome then start successfully after you exit firefox? I just had a recollection that part of the vaapi stack in mesa was removed because of patent

Re: dump/restore?

I love dump/restore. Old fashioned maybe. But you have to use dnf to install dump. Restore should already be there. IDK about its status with fedora. On 12/11/2022 8:22 AM, ToddAndMargo via users wrote: Has dump/restore been superseded with something else? It ain't work right! dump

Re: Better way to refresh the Display?

On Sun, 11 Dec 2022 09:21:09 -0500 Javier Perez wrote: > Hi > I have a problem. Oftentimes when I press the button on my KVM to > return to my desktop and Fedora 36, the screen is black and > unresponsive. I have to log in through SSH and restart lightdm I don't have a kvm, but I recall seeing

Better way to refresh the Display?

Hi I have a problem. Oftentimes when I press the button on my KVM to return to my desktop and Fedora 36, the screen is black and unresponsive. I have to log in through SSH and restart lightdm (systemctl restart lightdm) Problem is that it resets my sessions and some programs like cura do not like

Re: dump/restore?

El 11/12/2022 a las 14:22, ToddAndMargo via users escribió: Has dump/restore been superseded with something else? It ain't work right! dump restores a qcows drive as a blank drive https://bugzilla.redhat.com/show_bug.cgi?id=2152393 ___ I used last

dump/restore?

Has dump/restore been superseded with something else? It ain't work right! dump restores a qcows drive as a blank drive https://bugzilla.redhat.com/show_bug.cgi?id=2152393 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an

Fedora37 NIS logins no audio in KDE/Plasma/X11

I've just updated a test machine from Fedora35 to Fedora37, most is working but users logged in using NIS authentication no longer have access to audio. The system is using the KDE/Plasma desktop and the sddm login manager all using X11. It looks like /run/user/ does not exist and

Re: chrome hangs

El 10/12/2022 a las 17:08, Geoffrey Leach escribió: New install of Fedora 37. Everything seems t be working, except for Google's chrome (both flavors). Does anyone have a workaround? Thanks. ___ Did you tried Chromium ?