Is this a 'disable secure boot, update, re-enable' situation, or a 'things will die horrible if you
Is this a 'disable secure boot, update, re-enable' situation, or a 'things will die horrible if you do this' situation?
KYep, do that
KCan't die horribly, as long as you turn off secure boot it will always boot
KAnd are you on testing or stable?
ZThe app isn't really maintend anymore from what I seen . they just make sure it installs on the latest plasma and thats it. bug reports mostly get ignored. I'm guessing what happening on my end is that I am using the suffle wallpaper feature. and thats causing issues. I think most pepole just set a wallpaer and leave it at that
KBazzite stable
KWell disabling secure boot worked, BIOS is updating
K
Zi thought since wallpaper engine is included by default on bazzite you guys were supporting it or something. normaly I don't use wallpaper-engine on my kde systems. to many bugs and crashes
KWe don't maintain it, just install it and make sure it works at a base level
KThe QT6 branch got an update a month ago, it's definitely still maintained
KBut they are slow on new features
Zthey just do very minor updates to it latley and its useally by other pepole the main dev as moved on
K@Kyle Gospo latest lenovo BIOS update auto-enables Secure Boot. Then this happens on boot. Disabling secure boot again results in a booting system. I'd recommend having Legion Go users not use secure boot, or the shim location thing be changed?
K
KDid you enroll the key?
Zagain maybe my issue is that I use the shuffle feature and most don't but wallpaper engine def does not work on a base level
KBios update wipes out your enrolled keys
KOh this I did not know
Kso I need to re-enroll with Mokutil?
KYep
Zall my wallpapers do work indvidually so it dosn't seem to be a case of a unsporrted wallpaper
KI haven't seen that issue so definitely open one, might get some attention
KOk. Well I have successfuly updated to the July 19 Legion Go BIOS from LInux. https://pcsupport.lenovo.com/us/en/downloads/ds565491
KUse the ujust
Canybody else having issues playing No Man's Sky? Other games work find but this one keeps crashing at the menu
KHave you checked ProtonDB?
KI haven't played that one since the update but it was fine prior
Zi have https://github.com/catsout/wallpaper-engine-kde-plugin/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen+author%3Azany130 several times on several diffrent plasma versions
GitHub
A kde wallpaper plugin integrating wallpaper engine - Issues · catsout/wallpaper-engine-kde-plugin
CI hadn't until you mentioned it (just checked and it's gold) but it works perfectly on deck so I assumed it would on bazzite
Zmainly this one as the others may have been plasma version specfic https://github.com/catsout/wallpaper-engine-kde-plugin/issues/284
GitHub
Describe the bug causes kernel lockups ( system completely frozen can't ssh, use sysrq keys etc) System Information Operating System: Garuda Linux KDE Plasma Version: 5.27.3 KDE Frameworks Vers...
KThat's a very safe assumption
KTry validating your game files
Cdid that, full reinstall too, and manually deleting prefixes & shader cache but no dice
Calso tried
ENABLE_GAMESCOPE_WSI=1 gamescope -W 1920 -H 1080 -f -r 60 %command%@Kyle Gospo Worked perfectly. So yeah, newest Legion Go BIOS update went fine. Disable Secure Boot, use fwupdtool, reboot, wait for update to finish, disable secure boot, boot bazzite, re-enroll key, reboot, enable secure boot again, bob's your uncle.
Mif you enroll the MOK and use third-party UEFI keys it should work
Thonestly ill just layer it, automatically adds a desktop entry too
Ti remember there being a tutorial for layering vs code so it works seemlessly i think
KActually just installed it today, works great
KI wanted to try the new update
KI mean, nothing stops you. Distrobox is just cleaner and doesn't slow down updates further. But it's your system, so do what makes you happy 
KRe: BIOS updates - I also still hate whoever at Lenovo thought that having a black screen doing nothing with no output as a standard part of a BIOS update was somehow a good idea.
Csame!
Cseems like mangohud was causing issues. Weird because I have it active for other games too
KHuh. Well, glad I updated my BIOS then. I wonder what defines 'a long time'.
EDid the boot loader on the ROG Ally ever get fixed to allow the controller to work? Or still gotta boot into the BIOS?
Anot yet
Aneed an ally owner to do a simple command for me
Aor a native touch screen person
Awin mini etc
