Black screen on startup and broken gamemode (gamescope)
hahelui opened this issue · comments
Describe the bug
I'm experiencing a black screen after adding games from Lutris to Steam and installing Java on my Steam Deck. Here's a detailed breakdown:
Steps leading to the issue (uncertain):
Added games from Lutris to Steam
Installed Java
just casual things
Observed behavior:
Black screen on Steam Deck boot
Requires manual intervention:
Connect a keyboard
Enter TTY mode
Start Plasma manually with startplasma-wayland command
Game mode inaccessible:
Attempting to return to game mode results in a black screen
Workaround: Manually start game mode with gamescope-session-plus steam --user deck
Possible causes (uncertain):
Gamescope
Autologin script
SDDM
Request:
I'd appreciate assistance in identifying the root cause of this black screen issue and potential solutions to restore normal functionality, including automatic login to game mode.
Thank you.
What did you expect to happen?
No black screen , boot to steam gamemode
Output of rpm-ostree status
State: idle
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:stable
Digest: sha256:4dbab257ebce893a30061b63e12f10403ea06d1c93c85e9d3d68bdf568c37859
Version: 40.20240508.0 (2024-05-08T22:06:35Z)
LayeredPackages: java-11-openjdk plasma-workspace-x11 sunshine
LocalPackages: p7zip-gui-16.02-28.fc40.x86_64
ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stable
Digest: sha256:17c4d692a912a1bbd81f9a81d9dfa6182cd31a867e601194e135751941fa4692
Version: 40.20240508.0 (2024-05-08T22:04:20Z)
LayeredPackages: java-11-openjdk plasma-workspace-x11 sunshine
LocalPackages: p7zip-gui-16.02-28.fc40.x86_64
Hardware
Jupiter
Extra information or context
Troubleshooting Attempts:
Moved the Steam directory .
Uninstalled DECKY LOADER.
Installed X11 .
Rebased on BAZZITE:STABLE.
...
I'd also like to try resetting SDDM and Gamescope to see if it resolves the issue. Could you provide some guidance on how to do that safely?
Could be because you layered X11, try resetting your layers and see if this behavior persists.
Could be because you layered X11, try resetting your layers and see if this behavior persists.
Thank you for the response,
how can I do that ?
edit :
I found out to reset layers is by using
rpm-ostree reset
or
rpm-ostree uninstall --all
but none of these fix the issue which is weird.