PSA: Decky broke. Either revert to 2.0.14 or don't update to 2.0.16
PSA: Decky broke. Either revert to 2.0.14 or don't update to 2.0.16
BPastebin
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
BIs that likely the cause of my issue then?
Awhats your issue?
Asounds like probably not though. The issue is menu weirdness i think
Abut you should try disabling the plugin_loader service and see if it boots
BI'll give it a try, thanks
BNah, got a blank unresponsive terminal this time but that's not unusual. Still able to navigate behind that to get to desktop mode. Rollback seems not to have my prior deployment. Going to have to try rebase.
BMy .gamescope-stdout.log shows some definite errors
TI'm wondering if anyone has any ideas for what else to troubleshoot in my situation. For a long time off and on, I've been trying to figure out why total war: Warhammer 3 works perfectly in xorg but is stuttery when panning the camera in Wayland. I'm on an AMD GPU with VRR enabled (via the patched mutter). I don't really notice this difference in other games. I've messed with tons of variables at this point, I don't really see why it should be like this especially with AMD. I've got the GPU using the correct power profile, I've messed with CPU governors and AMD CPU drivers. I've messed with Vulcan present modes/vsync but some of those seemed bugged and stick to 60fps cap when my monitor is 120. I've tried tweaking dxvk. I tried plasma a while back but maybe should try it again to see if it's something weird with gnomes VRR implementation. It's just so weird to me that it's perfect in xorg (VRR enabled with no other tweaks) but stuttery in Wayland.
VBare metal, ventoy with secure boot
TAnd also this is the windows version run in proton
VI'll take a peek now
VLemme try disable secure boot until it;s installed
TAlthough I'm remembering the issue persists in a dedicated gamescope session so it must not be gnome-specific
DHoooldup
DOnly one of the SSDs was actually dead
DThe one time that the offline iso actually worked was when I booted it with ventoy...
V@Noel Ok, so it seems that not removing the ventoy drive properly will cause the install to fail
VYou need to eject it properly or it doesn't like it apparently
VSorry if that was common knowledge, not much of a ventoy user and not ejecting USBs is usually fine for me
FHey, did anyone figure out my issues booting the installer on Deck?
Ayou should always eject usb drives on linux
Alinux uses RAM caching so transfers will finish on the UI before they are written to disk
Asome times 10-15min before
VOh, that explains why it takes a sec to eject
AWindows has it disabled now so as long as there isnt a transfer it is safe on windows
VOk, next step, how do I make secure boot work on bazzite?
AI dont think theres a way to disable ram caching in linux tho
VI'm on the MOK manager right now
Athere should be a mok key floating somewhere but ive never done it sooo
FThere is via udev rule, but it makes writing process much slower besides classic RAM cache disabling
Fthere was a recent talk about this in general
VLooks like you need to disable it, enroll the keys and then re-enable
KISO should ask you to enroll it at the end
KOr you can do that
KEither is valid
VOh, I just force rebooted it
VI can try that
TI’m not convinced there’s not a different suspend issue with the latest version of Bazzite on the Legion Go. Since updating this morning I noticed once where the LED indicator was white but the screen was on and the steam performance overlay was there and just now the screen was off but the fans were still on.
TSomeone else mentioned a similar suspend problem in a help thread for the ally today too
AWas on or flashing?
TIt just happened again, it is purple and on. Flashing would be normal behavior. It’s like it doesn’t complete the suspend.
AOh
ASo black screen
AFans on, light on
TRight
TAnd unresponsive to being resumed on press
THave to hard shutdown
AClassic suspend issue
ASomeone fish the journalctl fpaste
