Does the system also freeze on lock screen without the sleep? superkey(winkey)+L

No, lock screen works fine.

Cheers for the links, I’ll look into that!

That’s interesting! Might be KDE bug then.

Could you try going to System Settings → Screen Locking and de-select “Lock after waking from sleep”? I wonder if you’ll get the same result as I’m getting.

Before I updated the BIOS to the latest version, once I woke it up, I’d see the desktop exactly frozen as it was the moment I pressed the “Sleep” button.

Now, after the update, that freeze happens BEFORE the PC goes to sleep - the monitors stay on.

So, I did a BIOS update, as advised here, and got some interesting results!

The freeze still happens - but it now freezes BEFORE the PC shuts down.

As in: I click the Sleep button, all devices get disconnected (audio, network, BT, input - all of it goes), the OS freezes, but the screens stay on. I cannot switch to a different VT at this point as everything is disconnected.

Oh, yeah, that’s true! Didn’t know that’s a thing here, good to know!

No, the keyboard is unresponsive. I also tried Ctrl+Alt+F1…F7, and got absolutely nothing.

I did a BIOS update, as advised here, and the behaviour changed! Now the freeze happens BEFORE the PC goes to sleep. As in: it gets to the frozen state the moment I click the button and the screens remain on.

I did some more digging and in System Settings → Screen Locking found an option called “Lock after waking from sleep”. Since the OS was freezing on the lock screen, I disabled that to see what happens.

The OS freezes completely just before the shutdown to sleep - I can see ALL devices get booted out - network, BT, audio, mouse, keyboard - everything gets disconnected and then freeze happens.

I have updated the BIOS to the latest version and since then the freeze happens BEFORE the OS goes to sleep. As in: I click the Sleep button, everything freezes, that’s it, the screens never turn off.

So it doesn’t seem like it’s something that’s happening in BIOS during wake-up/reboot, right?

Don’t need to check, I built the PC myself - it’s currently running on the iGPU from the 7800x3d.

(K)Ubuntu is configured to apply updates at reboot to minimize any breakages

That’s the problem - it never did apply the updates. I even tested that by manually telling it to download them all and then rebooting once they were all ready to install. I had to re-download them all after logging back in.

I also noticed that one account was always getting app updates while OS updates were ONLY showing up for the primary account,

I get how this may be “by design”, but it’s an infuriating design. :D

Did the toolbar just disappear from all apps?

Correct. It was just not there. I was able to add the Global Toolbar widget and get a “Mac-like” experience, or add it as a hamburger button on the titlebar, but that’s it.

Automatic mounting of drives is done easiest through editing the /etc/fstab file in Linux. I am not aware any other methods that are more user-friendly

Which is also extremely bad design, if you ask me. For removable drives - sure, why not. But if it’s a bloody NVMe sitting on the motherboard? Also: there just should be a prompt going “do you want to auto-mount this” the moment the user mounts it through Dolphin for the first time.

Unless you have a specific reason for using Tuxedo OS, I would highly recommend Fedora with KDE Plasma desktop environment

As of right now, I’m having a great time with Tuxedo OS - other than the Sleep function not working, everything else is smooth sailing. I don’t want to use Fedora, because I’m more familiar (if still barely) with the Debian Linux family.

It also ships with the latest versions of the kernel, so you’ll have less driver issues.

Is there an easy way to check the kernel version I’m running vs the latest available?

Well, I updated the BIOS - no change so far. I guess I’m stuck without Sleep. :/

OK, that was journey… I’m on the latest BIOS version now! Of course I forgot to check ALL the settings before I installed it, so I ended up in a boot loop. All good now, hopefully.

There IS a behaviour change on the Sleep front - it now never actually goes to sleep, the screen freezes like before, I can see ALL devices getting kicked out, and then nothing more happens.

Before doing the update I removed the "mem_sleep_default=deep" bit from grub, tested, added it back in, tested again. No change noted.

Everything worked fine on Windows - wouldn’t BIOS misconfiguration also cause problems there?

There’s no Windows, I nuked the drive before installing Tuxedo OS.

Nvidia?

I currently have no dedicated GPU, just a Ryzen CPU.

I go CTRL + ALT + F6, wait for the login to show up

Tried that just now - doesn’t work. It seems like all devices are disconnected so I can’t use the keyboard to change the VT.

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.

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.