bazzite
bazzite copied to clipboard
Screen crashing after sleep/reboot/etc.
Context
I recently upgraded from vanilla uBlue (silverblue-main) on Fedora Silverblue 38 to the latest Gnome Bazzite for Fedora 39. I used the following command from the Bazzite GitHub page:
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:latest
Issue
When I do actions like putting my computer to sleep or restarting, my monitors will be on, but not display anything. I can get the display back if I power cycle them. While the monitors are off, the computer seems to still be running, the fans are still loud. This issue was not occurring previously
Hardware
- Intel i5-13600k
- AMD RX 6800 XT
Other
rpm-ostree status
output:
State: idle
Deployments:
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:latest
Digest: sha256:5d93a0822c10a3d53fc05130e04cdcd4a17207fbdfdf4ae0f15a84922b458535
Version: 39 (2023-11-14T04:01:20Z)
Diff: 1 upgraded
LayeredPackages: corectrl openrazer-meta razergenie
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:latest
Digest: sha256:2fa95ce1d45a3241b3c5e395c62d65d3f8003f4b0d368f1b20724ceba44156b2
Version: 39 (2023-11-13T19:08:27Z)
LayeredPackages: corectrl openrazer-meta razergenie
ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:latest
Digest: sha256:2fa95ce1d45a3241b3c5e395c62d65d3f8003f4b0d368f1b20724ceba44156b2
Version: 39 (2023-11-13T19:08:27Z)
LayeredPackages: corectrl openrazer-meta razergenie rpmfusion-nonfree-release
steam-devices
fedora:fedora/37/x86_64/silverblue
Version: 37.20230320.0 (2023-03-20T00:48:14Z)
BaseCommit: 008ef1f466e75de52c3981399f3eb5244ea730448e13f3ed2a20504e4efbe898
GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A
LayeredPackages: gnome-tweaks mozilla-openh264 neofetch steam-devices
LocalPackages: rpmfusion-free-release-37-1.noarch
rpmfusion-nonfree-release-37-1.noarch
Pinned: yes
dmesg
output after the issue occurs:
https://paste.centos.org/view/3642f66e
If you need any other logs, just say so.
The issue has been fixed after an update
Nevermind, it seems to still be happening
Let us know if you're still experiencing this