Black screen after login on Bazzite 40 + Wayland redux

I had earlier talked about how I get a black screen after logging in with Wayland in Bazzite 39. I can get to a TTY but not the desktop.

I was hoping that when I upgraded to 40, there’d be a fix for my problem. But not only isn’t there one, it’s worse: there’s no X11 option to save me.

This is an HP 845 G9 notebook with 32 Gb RAM and a Ryzen 6800U processor with 680M iGPU.
Help!

rpm-ostree install plasma-workspace-x11

Reboot and X11 should appear in the login now.

1 Like

You’re a hero.

Later I’d love to figure out why Wayland worked for weeks on my hardware, until it didn’t.

My joy is short-lived. Now even selecting X11 on the Login screen leads straight to a black screen, and no ability to even bring up a TTY with CTRL-ALT-Fx. I can however SSH into the machine from my desktop.

Here is the rpm-ostree status. It’s on nightly?

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:fcb21048f072f4f4a19f7daf8a9edcb3f0d66f8af34b61b2700866aa6aec2f58
                  Version: nightly (2024-04-26T17:02:20Z)
          LayeredPackages: coolercontrol google-chrome-stable liquidctl plasma-workspace-x11
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf" ' 

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:c720c528590f8bf5bf127c49873ff3f874d982955078c98c338eeb17fcaed2a9
                  Version: main (2024-04-24T21:27:57Z)
          LayeredPackages: coolercontrol google-chrome-stable liquidctl plasma-workspace-x11
                Initramfs: '"-I /etc/crypttab /etc/modprobe.d/amdgpu.conf" '

But using the computer directly is totally dead in the water now. Help! :frowning:

For now because you aren’t the only reporting this issue, I would rebase to Fedora 39 until it’s resolved.

rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:39

Thanks for the suggestion. Unfortunately I’m getting a GPG error when rebasing.

Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:39
Importing: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:39 (digest: sha256:fe357496bb5ac67edd223e8cf27ed8d29384eb6948a082b98c265ec8a9d9ac90)
ostree chunk layers already present: 65
custom layers already present: 3
Checking out tree 07112c1... done
Inactive requests:
  plasma-workspace-x11 (already provided by plasma-workspace-x11-5.27.11-1.fc39.x86_64)
Enabled rpm-md repositories: copr:copr.fedorainfracloud.org:matte-schwartz:sunshine copr:copr.fedorainfracloud.org:rodoma92:kde-cdemu-manager copr:copr.fedorainfracloud.org:rok:cdemu fedora-cisco-openh264 updates fedora rpmfusion-free-updates-testing rpmfusion-free-updates rpmfusion-free rpmfusion-nonfree-updates-testing rpmfusion-nonfree-updates rpmfusion-nonfree google-chrome copr:copr.fedorainfracloud.org:codifryed:CoolerControl updates-archive
Updating metadata for 'copr:copr.fedorainfracloud.org:matte-schwartz:sunshine'... done
Updating metadata for 'copr:copr.fedorainfracloud.org:rodoma92:kde-cdemu-manager'... done
Updating metadata for 'copr:copr.fedorainfracloud.org:rok:cdemu'... done
Updating metadata for 'fedora-cisco-openh264'... done
Updating metadata for 'updates'... done
Updating metadata for 'rpmfusion-free-updates-testing'... done
error: Updating rpm-md repo 'rpmfusion-free-updates-testing': Failed to download gpg key for repo 'rpmfusion-free-updates-testing': Curl error (37): Couldn't read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-39 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-39]

A discord user helpfully gave the solution to the GPG problem.

cd /etc/pki/rpm-gpg
sudo ln -s RPM-GPG-KEY-rpmfusion-nonfree-fedora-2020 RPM-GPG-KEY-rpmfusion-nonfree-fedora-39

Nope. Not working again. Here’s the symbolic link

And the error I get rebasing to 39 is:

error: Updating rpm-md repo 'rpmfusion-free-updates-testing': Failed to download gpg key for repo 'rpmfusion-free-updates-testing': Curl error (37): Couldn't read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-39 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-39

I had the same gpg error after trying to rebase to F39 after updating to F40 on Bazzite (Gnome Nvidia).

I updated to F40 and it was kind of a mess. GPU performance was messed up whereas on F39 it wasn’t. Even playing Youtube videos without stuttering / artifacts was no longer possible. I was getting massive screen tearing when gaming (like on crack type of screen tearing). Also, 2 of my printers stopped working, and I no longer was able to mount my two ntfs windows drives. I was getting permissions errors when trying to mount.

When I figured “hey I’m supposed to be able to just back out right?”, I tried to rebase to F39 only to get the GPG error (same as above).

I ended up having to turn off GPG in several of the etc/yum.d.repos rpmfusion files in order to get it to rebase. Somethings not right guys… This was on a roughly one or two week old installation. I realize that I would be advised not to turn off gpg, but when you are as new / dumb as I am, you just want to get it done and move on.

Thanks for the help. I’m a little bit worried about turning of GPG. Surely this can’t be the right answer?!

Did rebasing back to 39 help?

No, its not an answer… clearly its a bug, its just a workaround until they figure out what’s going on.

Yes, all of my problems went away by rebasing to F39. My windows drives immediately automounted just like before on the very first boot back into F39, my printers work again, and video playback / gaming is now the way it was before.

How did you turn off the GPG?

Look in the etc/yum.d.repos folder and you’ll see a bunch of different files that start with “rpmfusion”… Go into those files one at a time and change “gpgcheck” from 1 to 0 and save. Do them all and retry rebasing. It should work.

1 Like

Thank you! This is the only thing that worked for me. I’m back on Aurora 39 (X11 only, Wayland gives me the black screen).

Glad it helped! We should certainly not have to do this though. I hope they get it fixed soon.

1 Like

Hi, has a solution already been found for this issue ? I’m encountering a similar Black screen issue but when I open Steam or any Flatpak application.