Legion Go Bazzite: Black post-boot/Gamescope not working.
I was having some issues with my controller freezing on my Legion Go Bazzite-Deck, so I rebased to latest stable. Now it boots to a black screen (seems Gamescope is broken) as I can get to desktop through GRUB. I've rebased it a couple of times and still same issue: worse I can't get BACK to the original image as the keys are invalid. Does anyone know the last stable release for Legion Go where Gamescope works? Thanks all!
32 Replies
How long did you go between updates?
Maybe a month?
Last version should be working great
But seems like you're not the only one reporting this issue today
I'm rebasing, what's the number for the build?
Whatever stable is
First disable decky
If that doesn't work
Then we diagnose
I'll do that now and let you know.
fully removed decky, updated to stable, still getting a black screen post-boot.
That's very unfortunate
Anything else I could try?
I'm thinking
No problem. Appreciate the help
Resetting the steam client could help but I'm not sure of how to do that properly
@Kyle Gospo is on US hours, so if you wait a couple of hours I'm sure he will have some ideas
I want to say around 4-5 hours
I followed the commands to uninstall decky; a search says there are some residual files in the homebrew/plugins folder but it needs permissions to delete: do you know how to grant permission to remove these and I'll see if that helps.
If you are sure you want to purge decky yes
You could have also just disabled it
there is
ujust fix-reset-steamsudo rm -rf ~/homebrewshould preserve data but do backup too
Removed homebrew, that didn't load gamescope. Then tried resetting steam: its removed Steam but gives a message "Steam - Fatal Error. Steam needs to be online to update". I'm definitely online and I CAN download the file it attempts to reach. Very odd.
Tinkered some more and nothing fruitful. All saves were backed up so I think I may consider a full reinstall/reset. Does Bazzite have a streamlined way of reinstalling while retaining dualboot? Otherwise I'll wipe and follow the guide I used initially again.
Yes and no
You can start from the dual boot guide after the partitions have been created
And reuse the existing onws
Or remove the bazzite ones and remake them
I think I'll follow the latter as I know how to do that. What a bummer.
I updated as I was having issues with the controllers not working in game after a suspend: is this something that has come up in any issues?
Yes, one issue with that was fixed 2 months ago
The other one is having a wake up animation is broken
I'll wipe and reinstall and hopefully that solves my initial issue, even if I have to redownload everything. Just is what it is 👍
might be seeing this issue: https://github.com/aarron-lee/legion-go-tricks?tab=readme-ov-file#bazzite-bugs
specifically this:
- Bazzite 3.5 bug - after upgrading to bazzite 3.5, some LGO users have reported booting into a black screen
- potential workarounds:
- first, open a tty + login via pressing
Ctrl + alt + f2 on a physical keyboard
- then, delete old/stale env variables from $HOME/.config/environment.d
- command for removing all env variables: rm $HOME/.config/environment.d/*
- also, run sudo systemctl daemon-reload
- reboot
- if potential workarounds don't work, you'll probably need to consider a bazzite rollback to an older versionwhat was the env variable
I don't know, the bugfix was submitted by a user
who just deleted everything
would be good to know, this environment variable would need to be removed
but it seems to have worked for others too
automatically
please if somebody has this issue keep a log of what was in the folder
my guess is that it's some sort of old override env var
since new bazzite installs don't have this issue
the bug was all from older bazzite installs
well, when updating bazzite should never break
if there is a variable that would need to be removed, it needs to be noted and deactivated, incl. how it ended up in there
anything in
$HOME/.config/environment.d was manually added by the user somehow
it's not something Bazzite shipsusers dont know what a directory is
so
theres some outdated documentation that is bricking installs
and that directory doesn't exist on a clean bazzite install
¯\_(ツ)_/¯