this post was submitted on 29 Mar 2025
67 points (94.7% liked)

Linux

52837 readers
451 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
67
Tuxedo OS (Ubuntu-based) with KDE/Wayland - waking from Sleep freezes the computer. Help? (lemm.ee)
submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]
89 comments fedilink hide all child comments
 

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.

(page 2) 40 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 1 week ago (5 children)

First, update your computer's BIOS/firmware. If that doesn't fix it, then try Arch, or Fedora beta. If the problem exists there too, then it's a kernel issue in general, and it might get fixed in the future. OR, if the computer BIOS is buggy, Linus has been clear that they won't do workarounds for buggy firmwares. In which case, you'd need a new computer that's actually compatible with Linux.

Most of the computers out there have buggy firmwares that go around for Windows, but Linus has been adamant that he wouldn't do workarounds because they bloat the kernel.

load more comments (5 replies)
[–] [email protected] 23 points 1 week ago* (last edited 1 week ago) (3 children)

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?

[–] [email protected] 3 points 1 week ago (2 children)

Yeah, had a brain fart. It's a freeze.

load more comments (2 replies)
[–] [email protected] 7 points 1 week ago

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.

load more comments (1 replies)
[–] [email protected] 5 points 1 week ago (1 children)

I'm pretty sure tuxedo support should be able to cover this for you. Its one of the bonuses of buying a Linux laptop.

[–] [email protected] 2 points 1 week ago

I'm running it on a desktop PC, so not sure if they'd cover it. But I might poke them about it, good idea.

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago) (1 children)

Is your root partition encrypted?

Give the output of lsblk if you could.

[–] [email protected] 1 points 1 week ago (1 children) 
alaknar@HostName:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0     4K  1 loop /snap/bare/5
loop1         7:1    0 104,2M  1 loop /snap/core/17200
loop2         7:2    0  55,4M  1 loop /snap/core18/2855
loop3         7:3    0  63,7M  1 loop /snap/core20/2496
loop4         7:4    0  73,9M  1 loop /snap/core22/1802
loop5         7:5    0 164,8M  1 loop /snap/gnome-3-28-1804/198
loop6         7:6    0   516M  1 loop /snap/gnome-42-2204/202
loop7         7:7    0  91,7M  1 loop /snap/gtk-common-themes/1535
loop8         7:8    0  10,8M  1 loop /snap/snap-store/1248
loop9         7:9    0  44,4M  1 loop /snap/snapd/23771
nvme1n1     259:0    0 931,5G  0 disk 
├─nvme1n1p1 259:1    0   300M  0 part /boot/efi
└─nvme1n1p2 259:2    0 931,2G  0 part /
nvme0n1     259:3    0   1,8T  0 disk 
└─nvme0n1p1 259:4    0   1,8T  0 part /media/alaknar/BigStorage
[–] [email protected] 0 points 1 week ago (2 children)

I'm not seeing any swap space, so that could be it. Check this post out.

It could also be that your BIOS settings for suspend/resume aren't set to something compatible with your existing config as well though, if the above doesn't work, or you're not comfortable with that level of interaction, check your BIOS first, then try the above maybe.

load more comments (2 replies)
[–] [email protected] 1 points 1 week ago (1 children)

You could try a tool like LACT and setting your gpu power profile to always highest. Another thing you could check is your BIOS settings, https://www.tomshardware.com/reviews/bios-beginners,1126-8.html or checking if the latest bios is installed https://red.artemislena.eu/r/gigabyte/comments/1b3bffy/gigabye_b650_aorus_elite_ax_rev_10_sleeppower/

[–] [email protected] 1 points 1 week ago (2 children)

Hmm... Wouldn't I also have sleep problems on Windows if this was a BIOS issue?

[–] [email protected] 1 points 1 week ago (5 children)

I don't know enough to rule out that windows could overwrite bios.

load more comments (5 replies)
load more comments (1 replies)
[–] [email protected] 1 points 1 week ago

This is not a solution at all and just what I usually resort to, I always disable sleep on every OS and computer I use. I've always had strange issues after waking up from sleep that persist until reboot and I can't even remember what they are now because it's been so long since I've used it.

[–] [email protected] 5 points 1 week ago (1 children)

I would try:

  • see if you can get logs of the resume process
  • suspend from a text VT and see if that changes the behaviour
  • boot into single user mode and try suspend from there
  • boot an older LTS or a newer test kernel and see if it has the same problem
[–] [email protected] 4 points 1 week ago (4 children)

Sorry, mate, I'm a Linux noob.

I have no clue where to find the logs for this.

No idea what a VT is.

Don't know how to boot into single user mode....

[–] [email protected] 2 points 1 week ago (2 children)

Fair enough, most of that isn't something a user should have to worry about.

VT is just Virtual Terminals. You always have one of them active, and in most distros you can switch to others by Ctrl-Alt-F1 through F12. In some distos it's just Alt-F1.

So if you press Ctrl-Alt-F2 you should be brought to a text login. For crazy historical reasons you may have to either press Ctrl-Alt-F1 or Ctrl-Alt-F7 to get back to your usual graphical session.

Arch docs for example: https://wiki.archlinux.org/title/Linux_console

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago)

OK, I tried that. Ctrl+Alt+F2 gives me a black screen.

Ctrl+Alt+F1 brings me back to my desktop.

Ctrl+Alt+F3-F6 all have a text login screen. F7+ don't do anything.

I was able to grab the journalctl logs. You can find them (and an extra bit about the computer state I was able to get) HERE.

[–] [email protected] 1 points 1 week ago (1 children)

What are the crazy historical reasons? As far as I know, running six ttys and one graphical session, in that order, has been standard.

The really crazy historical way to test for crashes is num/scroll/caps lock. That's handled by a very low-level kernel driver. If those are responsive, it's probably just your display (gpu, X, wayland, or something) that's locked up. If they're unresponsive, your kernel is locked up. (If you're lucky, it's just gotten real busy and might catch up in a minute, but I've only seen that happen once.)

[–] [email protected] 0 points 1 week ago (2 children)

I was able to make some progress in troubleshooting.

I went to the Screen Locking options and disabled "Lock after waking from sleep". Now I get to see the screen when I wake the computer back up, frozen as it was when I issued the sleep command.

All devices are disconnected - no network, no Bluetooth, no audio, all the “tray” icons are greyed out and/or showing errors, time is stopped at the moment I clicked the "Sleep" button.

Not sure if that helps at all.

load more comments (2 replies)
load more comments (3 replies)
[–] [email protected] 10 points 1 week ago (1 children)

It might be due to https://github.com/systemd/systemd/issues/33083.

Try disabling user session freezing when sleeping:

sudo systemctl edit systemd-suspend.service

Add the following to the file:

[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"

Reload systemd:

sudo systemctl daemon-reload

After that, try sleeping and waking again.

[–] [email protected] 1 points 1 week ago (1 children)

Just tried it now. Does it need a reboot first? As in: should I try again?

[–] [email protected] 2 points 1 week ago (1 children)

As long as you ran systemctl daemon-reload, you should be able to try sleeping without needing to reboot.

[–] [email protected] 1 points 1 week ago (1 children)

Would this part potentially get in the way of the method you suggested?

One fairly recent thread had a proposed solution of adding "mem_sleep_default=deep" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.

Should I remove that?

[–] [email protected] 3 points 1 week ago

You can leave it.

[–] [email protected] 13 points 1 week ago (1 children)

What's your hardware? And did you regenerate grub's config after editing the file you mentioned?

[–] [email protected] 4 points 1 week ago* (last edited 1 week ago) (2 children)

Sorry, forgot to mention hardware! Added in an edit now!

I have a Ryzen 7 7800X3D and no dedicated GPU (yet).

I ran sudo update-grub after making the changes. That and rebooting a bunch of times since.

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago) (1 children)

I don't see a list of hardware in your edit.

[–] [email protected] 1 points 1 week ago (1 children)

What else do you need? CPU+GPU is there. MoBo? It's an MSI B650 Gaming Plus WIFI ATX AM5.

[–] [email protected] 3 points 1 week ago

Anything that might interfere with sleep. Literally any attached device might have a buggy driver.

[–] [email protected] 4 points 1 week ago (2 children)

Did you try any other distro or Windows on this system to narrow down the issue to Tuxedo OS itself? It could be an issue with your motherboard.

[–] [email protected] 2 points 1 week ago (1 children)

Windows worked flawlessly.

Kubuntu had massive issues with other things, but I didn't test Sleep (due to those other issues I only had it for a day or two).

[–] [email protected] 1 points 1 week ago (1 children)

Did you nuke your Tuxedo OS install? It would have been better to, at least, have a look at system logs to see if there's anything there.

What problems exactly did you have with Kubuntu?

[–] [email protected] 2 points 1 week ago (12 children)

Did you nuke your Tuxedo OS install?

No, I'm still running it. Other than Sleep, everything else works mostly fine. Just the regular "linuxiness" here and there that's either easy to sort out, or easy to ignore.

What problems exactly did you have with Kubuntu?

Wow, that's a whole list... :D

On my laptop, I had zero touchpad gestures. Once I switched from X11 to Wayland I managed to get Firefox to handle pinch-to-zoom and forward/back, but nothing else and in no other application.

Bluetooth drivers were crap, made my $300 headphones sound like $10 headphones.

I accidentally set the wrong keyboard language during installation, changed it without any issues after signing in... But to this day that previous layout pops up on the login screen. The only advice I found online required quite heavy Terminal "hacking"... and didn't work anyway.

Updates are all over the place. They're coming in constantly, practically every day, often requiring a reboot. It also doesn't install any updates on its own, so even if there are smaller, security updates that don't require a reboot, you have to manually click through the notification and apply them. There was supposed to be another "hack" that makes it apply updates automatically, but it doesn't work.

I recently connected my Linux laptop to an external screen. All good, but... The login screen was displayed on both monitors. I clicked the login field on the external screen, started typing and nothing happened. Fiddled with that for a bit before, just out of curiosity, trying again, but this time fully on the laptop screen. Worked like a charm, zero issues.

That was the laptop. Then on my PC, I suddenly realised that I have not application menu (the one with "File", "View", "Edit", etc.). Just gone. Wasn't able to restore it.

Also, my secondary SSD would not stay mounted. Any time I rebooted, it was just gone - and that was a problem for me because I had my Steam library there and wanted to have Steam auto-starting on logon. That I was able to fix by editing fstab, but was still super annoying.

The move to Tuxedo OS was very smooth. Almost everything worked out of the box (still had to do the fstab bit), the Bluetoot driver is MUCH better, updates are more controlled. It's just this bloody Sleep feature that doesn't work. :D

load more comments (12 replies)
[–] [email protected] 0 points 1 week ago (1 children)

I moved to Tuxedo from Kubuntu after having MASSIVE problems there, but I honestly can't remember if I was using the Sleep feature.

[–] [email protected] 6 points 1 week ago (1 children)

I assume your issue is reproducible every time, right? If yes, do so and reboot. Use the following command to obtain logs from the previous boot, where you had the problem:

$ journalctl -r -b -1

Before resuming from sleep, wait for about a minute or so to check for that time gap in the logs to easily find the logs of the resuming process.

You can append >> file_name.log to the command above to output logs to a file, in case that makes copy and pasting easier for you.

[–] [email protected] 3 points 1 week ago* (last edited 1 week ago) (3 children)

11:48 - Sleep

11:50 - Wake

11:52 - Reboot

Password to the file:

spoilerhelpm.ee.lemm.ee

Log file (on Filen.io).

I noticed something that might be helpful, not sure.

I was fiddling with settings to see if I can do anything about this on my own. Found the "Screen Locking" settings and disabled "Lock after waking from sleep". Got some interesting results!

Nothing changes when I put the device to sleep, but now, when I wake it up, I can see the desktop, as it was when I issued the sleep command. Everything is frozen and all devices are disconnected - no network, no Bluetooth, no audio, all the "tray" icons are greyed out and/or showing errors.

load more comments (3 replies)
[–] [email protected] 3 points 1 week ago (1 children)

Do you have a Nvidia GPU?

[–] [email protected] 1 points 1 week ago (2 children)

Sorry, forgot to mention hardware in the OP. I have a Ryzen 7 7800X3D and no dedicated GPU (yet).

load more comments (2 replies)
load more comments
view more: ‹ prev next ›