Alaknar

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.

11:48 - Sleep

11:50 - Wake

11:52 - Reboot

Password to the file:

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.

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

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

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.

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

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

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

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).

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?

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

Is “sleep” hibernate or suspend?

How can I tell the difference? The button says "Sleep". I don't see anything like "Power Settings" in System Settings.

Also, is this triggered by manually putting to sleep or by for example closing a laptop lid?

It's a PC, not a laptop. I click the "Sleep" button in the Application Launcher.