Linux

53682 readers

588 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 6 years ago

MODERATORS

[email protected]

Tuxedo OS (Ubuntu-based) with KDE/Wayland - waking from Sleep freezes the computer. Help? (lemm.ee)

submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]

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

you are viewing a single comment's thread
view the rest of the comments

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

I have been using Steam and Heroic as flatpaks for a long time, and never had any issues.

I have two NVMe drives - 1TB and 2TB. I keep the OS and "regular apps" on the first one, games go on the second one. Moving the libraries was DIFFICULT on Flatpak. Had to use external software (Flatsomething, can't remember right now) to give permissions and even then, for some reason, sometimes installation would just fail with a "drive error". Oh, and I had to search online to provide the appropriate Steam path for Heroic because, by default, it doesn't see Flatpak Steam.

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

Flatpak applications run in a sandboxed environment with limited permissions. Steam, being a proprietary app, was never made with flatpak sandboxing in mind, so you need to poke holes in it's sandbox for it if you want it to see your files. Most people do not store their games in a separate location, so the default is pretty constrained.

Applications can have sandbox holes by default. Just checked Heroic's permissions and it can see flatpak Steam's directories. I don't know what might have went wrong for you.

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

Well, to be fair, there was A LOT of weird stuff happening. Steam wouldn't open at all (unless called from the terminal), or would open with just a black screen (GPU acceleration issue). At some point, I'm pretty sure, I had three instances of Steam installed. It was chaos.