this post was submitted on 29 Mar 2025
66 points (94.6% liked)

Linux

52817 readers
686 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
 

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.

top 50 comments
sorted by: hot top controversial new old
[–] Bogus007@lemm.ee 2 points 6 days ago (1 children)

Did you contact TUXEDO Support Centre?

[–] Alaknar@lemm.ee 1 points 5 days ago (1 children)

Haven't had the time yet, but it's on my to-do list. Just not sure if they will support this as I'm running it on my own hardware, not their laptop.

[–] Bogus007@lemm.ee 1 points 5 days ago

Give it a try. Perhaps they may give you at least a hint.

[–] ReakDuck@lemmy.ml 3 points 6 days ago (1 children)

Having the same issue on Intel + AMD GPU.

Arch Linux with newest KDE.

[–] Alaknar@lemm.ee 1 points 6 days ago

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.

[–] spacemanspiffy@lemmy.world 1 points 5 days ago (1 children)

What kernel version? I had similar issues on similar hardware. These have gone away in more recent kernels though.

[–] Alaknar@lemm.ee 1 points 5 days ago (1 children)

6.11.0-109019-tuxedo.

Not the latest, right? I guess I'll wait for an update.

[–] spacemanspiffy@lemmy.world 2 points 5 days ago

No, but I don't believe I saw the issue until the 6.13.x kernels either

[–] BoxOfFeet@lemmy.world 2 points 6 days ago (1 children)

That exact issue is why I stopped using KDE. I never did figure it out.

[–] zer0squar3d@lemmy.dbzer0.com 1 points 6 days ago (1 children)

Specs for computer havibg the issue ans how long ago did this happen? Seems like a bug that neexs to be reported and more data for devs the better.

[–] BoxOfFeet@lemmy.world 1 points 6 days ago* (last edited 5 days ago)

Tried it November of 2024, ended up switching to Mint with Cinnamon, zero issues since.

Dell XPS 8930

i7 9700 (no K)

32GB ram

NVidia RTX 2060

240gb ssd

2tb hdd

[–] original_reader@lemm.ee 23 points 1 week ago* (last edited 1 week ago) (5 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?

[–] flubba86@lemmy.world 3 points 6 days ago

Yep, not bricked. Just frozen.

There are two forms of bricked:

  1. hard bricked. This is when a software change (eg, installing a custom firmware) caused the system to fail to boot, and there is no possible way to ever get it to run again.
  2. soft bricked. Where a software change caused the failure to boot but there is a way (eg, reflashing using UART) to recover back to an older version that does boot.

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.

load more comments (4 replies)
[–] pogodem0n@lemmy.world 13 points 1 week ago (26 children)

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

load more comments (26 replies)
[–] Scholars_Mate@lemmy.world 10 points 1 week ago (4 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.

load more comments (4 replies)
load more comments
view more: next ›