Re: wayward wayland.

On 26/04/2021 12:29, Ed Greshko wrote: Or if using KDE plasma-shell.  FWIW, since the OP is getting a blank screen  with plasma it may be useful to reboot the system and use "journalctl -b -1 | grep plasma-shell" This may be an issue with plasma wayland in F33. https://bugs.kde.org/show_bug.

Re: Restored f33 on new drive from a tarball now a problem

On 4/25/21 8:32 PM, Michael D. Setzer II via users wrote: Just wondering how you copied the old drive to the new one? If you manually copied the data, the blkids are different, so the boot and fstab information will have to manually be updated, or you will have to use blkid to change the blkids t

Re: wayward wayland.

On 26/04/2021 11:52, Samuel Sieb wrote: On 2021-04-25 8:21 p.m., home user wrote: On 4/25/21 9:18 PM, Samuel Sieb wrote: Have you checked the journal to see if there's any indication of why it's not working? That's huge. Please give me something to look for, or a full command. It's hard t

Re: Restored f33 on new drive from a tarball now a problem

On 4/25/21 7:23 PM, Ed Greshko wrote: On 26/04/2021 07:09, Robert McBroom via users wrote: On 4/25/21 5:34 PM, George N. White III wrote: On Sun, 25 Apr 2021 at 17:04, Robert McBroom via users > wrote:     New drive has the same msdos partition structure

Re: wayward wayland.

On 2021-04-25 8:21 p.m., home user wrote: On 4/25/21 9:18 PM, Samuel Sieb wrote: Have you checked the journal to see if there's any indication of why it's not working? That's huge. Please give me something to look for, or a full command. It's hard to give anything specific and I'm not sure

Re: wayward wayland.

On 4/25/21 9:18 PM, Samuel Sieb wrote: On 4/25/21 7:57 PM, home user wrote: Might Fedora possibly maybe quietly disabled or turned off wayland sometime between F-25 and F-33 inclusively? maybe just for Nvidia graphics card users? possibly just for certain categories of users? No, but there

Re: wayward wayland.

On 4/25/21 7:57 PM, home user wrote: Might Fedora possibly maybe quietly disabled or turned off wayland sometime between F-25 and F-33 inclusively? maybe just for Nvidia graphics card users? possibly just for certain categories of users? No, but there's always a possibility of it not working

Re: wayward wayland.

On 4/25/21 6:21 AM, Patrick O'Callaghan wrote: On Sat, 2021-04-24 at 19:41 -0600, home user wrote: general FYI for everyone... This Fedora docs web page says that wayland has been the default gnome display server, and has been the default since F-25: "https://docs.fedoraproject.org/en-US/quick-

Re: System Failure?

On 4/25/21 8:23 PM, Samuel Sieb wrote: On 4/25/21 7:14 PM, home user wrote: one more question about filing bugs... After filling in the required fields and any optional fields that I think are helpful, is there something more I should do before clicking the submit button?  The past few bugs I'

Re: System Failure?

On 4/25/21 7:14 PM, home user wrote: one more question about filing bugs... After filling in the required fields and any optional fields that I think are helpful, is there something more I should do before clicking the submit button?  The past few bugs I've submitted seem to just stay in the n

Re: System Failure?

On 4/24/21 10:36 PM, Joe Zeff wrote: On 4/24/21 10:04 PM, Samuel Sieb wrote: You don't need a backtrace to report a bug.  "This program crashed and I don't know why" is still a valid bug report. Also, be sure to include as much detail about what you were doing when it crashed because if/when

Re: System Failure?

On 4/24/21 10:04 PM, Samuel Sieb wrote: On 4/24/21 7:26 PM, home user wrote: On 4/24/21 4:01 PM, Samuel Sieb wrote: On 2021-04-24 12:37 p.m., home user wrote: The problem report implies that a bug should not be submitted because the backtrace does not contain enough meaningful function frames

Re: wayward wayland.

On 4/25/21 6:21 AM, Patrick O'Callaghan wrote: On Sat, 2021-04-24 at 19:41 -0600, home user wrote: general FYI for everyone... This Fedora docs web page says that wayland has been the default gnome display server, and has been the default since F-25: "https://docs.fedoraproject.org/en-US/quick-

Re: wayward wayland.

On 4/25/21 1:21 AM, Tim via users wrote: On Sun, 2021-04-25 at 06:24 +0800, Ed Greshko wrote: Read Tim's comment again. "He" wrote the notes in a file. Not dnf or another process. Not quite. I've written my post-installation-log, but the system has written anaconda-ks.cfg files on two insta

Re: wayward wayland.

On 4/24/21 10:02 PM, Ed Greshko wrote: On 25/04/2021 10:12, home user wrote: Read Tim's comment again.  "He" wrote the notes in a file.  Not dnf or another process. The basis for my question was the sentence "I think the installation routine leaves a couple of files about the install in there

Re: Restored f33 on new drive from a tarball now a problem

Just wondering how you copied the old drive to the new one? If you manually copied the data, the blkids are different, so the boot and fstab information will have to manually be updated, or you will have to use blkid to change the blkids to match. I generally clone disks to the new one, which

Re: Restored f33 on new drive from a tarball now a problem

> On 26/04/2021 07:09, Robert McBroom via users wrote: >> On 4/25/21 5:34 PM, George N. White III wrote: >>> On Sun, 25 Apr 2021 at 17:04, Robert McBroom via users >>> mailto:users@lists.fedoraproject.org>> >>> wrote: >>> >>> New drive has the same msdos partition structure as the old. >>> Le

Re: success Re: machine will not boot after moving root

On Sun, Apr 25, 2021, 10:36 AM Michael Hennebry < henne...@web.cs.ndsu.nodak.edu> wrote: > On Sat, 24 Apr 2021, Chris Murphy wrote: > > > You need to use -B to bind mount the pseudo filesystems, and probably > also > > need to include /sys > > > grub2-install /dev/sda > > mount /dev/sda3 /mnt/a3

Re: Restored f33 on new drive from a tarball now a problem

On 26/04/2021 07:09, Robert McBroom via users wrote: On 4/25/21 5:34 PM, George N. White III wrote: On Sun, 25 Apr 2021 at 17:04, Robert McBroom via users mailto:users@lists.fedoraproject.org>> wrote: New drive has the same msdos partition structure as the old. Legacy system with boot p

Re: Restored f33 on new drive from a tarball now a problem

On 4/25/21 5:34 PM, George N. White III wrote: On Sun, 25 Apr 2021 at 17:04, Robert McBroom via users mailto:users@lists.fedoraproject.org>> wrote: New drive has the same msdos partition structure as the old. Legacy system with boot partition on a separate drive and from the root p

Re: NOKEY warning from yum update

On 26/04/2021 03:34, Michael Hennebry wrote: On Mon, 26 Apr 2021, Ed Greshko wrote: Well, for sure you have rpmfusion-nonfree-appstream-data installed on your system. And, in the update process it is found that the signing key needs and update as well. As a guess, I tried yum update --excl

Re: Restored f33 on new drive from a tarball now a problem

On Sun, 25 Apr 2021 at 17:04, Robert McBroom via users < users@lists.fedoraproject.org> wrote: > New drive has the same msdos partition structure as the old. Legacy > system with boot partition on a separate drive and from the root > partition. System boots in mode 3 as specified but entering id a

Re: NOKEY warning from yum update

On 4/25/21 12:34 PM, Michael Hennebry wrote: On Mon, 26 Apr 2021, Ed Greshko wrote: I don't know why you'd see this request to update the key as a "problem". I took it as a request to continue without a valid key. >>> Importing GPG key 0x94843C65: >>> Userid : "RPM Fusion nonfree reposi

Restored f33 on new drive from a tarball now a problem

New drive has the same msdos partition structure as the old. Legacy system with boot partition on a separate drive and from the root partition. System boots in mode 3 as specified but entering id and password flashes some text and returns to the login. Edited the grub entry to try a graphical b

Re: NOKEY warning from yum update

On Mon, 26 Apr 2021, Ed Greshko wrote: On 26/04/2021 02:09, Michael Hennebry wrote: On F33, yum update gives me ... (195/196): vim-common-8.2.2787-1.fc33.x86_64.rp 3.6 MB/s | 6.7 MB 00:01 (196/196): java-11-openjdk-headless-11.0.11.0.9 2.4 MB/s |  38 MB 00:15 [DRPM] libburn-1.5.4-1.fc33

Re: NOKEY warning from yum update

On 26/04/2021 02:09, Michael Hennebry wrote: On F33, yum update gives me ... (195/196): vim-common-8.2.2787-1.fc33.x86_64.rp 3.6 MB/s | 6.7 MB 00:01 (196/196): java-11-openjdk-headless-11.0.11.0.9 2.4 MB/s |  38 MB 00:15 [DRPM] libburn-1.5.4-1.fc33_1.5.4-2.fc33.x86_64.drpm: done -

NOKEY warning from yum update

On F33, yum update gives me ... (195/196): vim-common-8.2.2787-1.fc33.x86_64.rp 3.6 MB/s | 6.7 MB 00:01 (196/196): java-11-openjdk-headless-11.0.11.0.9 2.4 MB/s | 38 MB 00:15 [DRPM] libburn-1.5.4-1.fc33_1.5.4-2.fc33.x86_64.drpm: done ---

drive layout

Hi. Doing some research into how devs are using their dev systems in terms of the actual layout/partition of the drives. I've seen plenty of articles, figured I'd ask here as well. If you have an interested, I'd appreciate your thoughts. 1) How is your drive/system laid out regarding your pariti

success Re: machine will not boot after moving root

On Sat, 24 Apr 2021, Chris Murphy wrote: You need to use -B to bind mount the pseudo filesystems, and probably also need to include /sys grub2-install /dev/sda mount /dev/sda3 /mnt/a3 # already done mount -B /proc /mnt/a3/proc mount -B /dev /mnt/a3/dev mount -B /dev/pts /mnt/a3/de

Re: wayward wayland.

On Sat, 2021-04-24 at 19:41 -0600, home user wrote: > general FYI for everyone... > > This Fedora docs web page says that wayland has been the default > gnome > display server, and has been the default since F-25: > "https://docs.fedoraproject.org/en-US/quick-docs/configuring-xorg-as-default-gnom

Re: wayward wayland.

On Sun, 2021-04-25 at 06:24 +0800, Ed Greshko wrote: > Read Tim's comment again. "He" wrote the notes in a file. Not dnf > or another process. Not quite. I've written my post-installation-log, but the system has written anaconda-ks.cfg files on two installations, and left me a initial-setup-ks.