Hi all!
I recently installed Tuxedo OS with KDE and Wayland. I’m fairly new to Linux and, so far, the distro is great. With one caveat.
As far as power options go, everything works fine EXCEPT for Sleep. I can put the PC to sleep, but when I wake it up, I land on the login screen wallpaper with the login/password fields barely visible, as if frozen around the second frame of a fade-in animation.
Nothing works. The mouse cursor doesn’t move, the keyboard doesn’t do anything. The only way out of this state is to hold the power button until the PC shuts down and then turn it back on again.
I did some digging, but couldn’t find a solution. Some threads mentioned modifying something in systemd, but those were from years ago, so I didn’t want to risk that.
One fairly recent thread had a proposed solution of adding "mem_sleep_default=deep"
to GRUB_CMDLINE_LINUX_DEFAULT
in /etc/default/grub
.
That didn’t work for me, though.
I’d love to fix this, but I’m out of ideas. Any help welcome!
EDIT
Forgot it might be a driver issue, people were complaining about Nvidia gear!
I currently don’t have a dedicated GPU. I only have Ryzen 7 7800X3D running on MSI B650 Gaming Plus WIFI ATX AM5 MoBo.
Not really related to the issue. If I understand correctly, your device isn’t bricked, but freezes. A bricked device doesn’t boot anymore, a frozen device is unresponsive. Or am I misunderstanding this?
Yep, not bricked. Just frozen.
There are two forms of bricked:
Both are terms from the Phone modding community (ie, a phone has become as useful as a brick after this update) it’s quite hard to actually brick a modern PC.
Came here to say the same thing. Using the term “bricking” in the title had me very confused. It would be catastrophic if this was actually bricking computers.
Yeah, had a brain fart. It’s a freeze.
you could edit your post title
Oh, yeah, that’s true! Didn’t know that’s a thing here, good to know!