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.

  • pogodem0n@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 day ago

    Garuda Linux was one of my first distros when I started three years ago. It is fine, but I generally prefer customizing my system to my liking, including installed applications. I switched to Arch Linux (which is what Garuda is based on) after a few days. After using it for two and a half years, I realized I was spending way too much time customizing it. Then I switched to Fedora and it was a really tame experience. Now I am using uBlue Aurora, which is a fork of Fedora Kinoite (Atomic variant of Fedora KDE Plasma spin). It updates everything automatically and in one go (similar to smartphones) and I download all my apps from Flathub. It is practically the opposite of what I was doing with Arch.

    • Alaknár@lemm.eeOP
      link
      fedilink
      arrow-up
      1
      ·
      1 day ago

      I’m pretty happy with the state of the OS and GUI as it is right now. Just moved a couple of things around, basically.

      I do have a problem with Flathub, though - in theory, it’s great. But I’m going to be playing games on this PC and Flathub causes MASSIVE problems for Steam and Heroic Launcher, their libraries and Proton compatibility. Love the idea, don’t like the execution.

      Garuda (or maybe it’s an Arch thing?) does a phenomenal thing with AppImage files - when I launched the first one it asked me if I want to add shortcuts to Application Laucher and tuck the AppImage away in a safe spot, so that it doesn’t sit in Downloads. LOVE that feature.

      • pogodem0n@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        24 hours ago

        What problems did you have? I have been using Steam and Heroic as flatpaks for a long time, and never had any issues.

        That must Gear Lever, pre-installed. Pretty neat program.

        • Alaknár@lemm.eeOP
          link
          fedilink
          arrow-up
          1
          ·
          21 hours ago

          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.

          • pogodem0n@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            21 hours ago

            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.

            • Alaknár@lemm.eeOP
              link
              fedilink
              arrow-up
              1
              ·
              11 hours 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.