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.

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.

Since I REALLY wanted to just not be bothered with the issue of drivers (especially AMD drivers) I went for one of the "gaming" distros - Garuda Linux.

And I have to say, I'm very positively surprised. Judging by the images on their website, I was afraid it'll be one of those, you know, "pro gamer, full RBG rainbow" bullshit designs, but no - it's actually very pretty live, looks much better than on their website.

Runs on Arch (Zen?) and has a bunch of things that I like - for example an app called "Garuda Rani" which is basically: "you're a noob, here, press these buttons to make things work". It even includes installation shortcuts to some popular applications (Heroic Launcher, Steam, for gamers, but also Wine and Proton, AnyDesk, Discord, VLC, some emulators, a bunch of Linux games (they have SuperTux here!), etc.)

Overall, other than a slight issue with my favourite browser* and repositories**, everything so far seems to be smooth sailing.

* Created a profile, had it running, changed the hostname and it, apparently, screwed the browser over as it was looking for the profile on the old hostname. Weird stuff. Nuked the profile, recreated it, all is well.

** One of those "press these buttons to make things work" includes merging the mirrorlist. Since I knew nothing about it, I just merged one file to the other, didn't think a second about it, and then when I tried installing Steam, I got an error about a "missing repository for extras". Managed to fix it after finally reading what the # signs mean in the mirrorlist file (everything was commented out - every single server...).

I ended up switching to a different distro and now everything seems to be working fine. Tuxedo OS really didn't like my new graphics card.

I ended up switching to a different distro and now everything seems to be working fine. Tuxedo OS really didn't like my new graphics card.

I ended up switching to a different distro - Tuxedo OS didn't really like me putting in an AMD graphics card.

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.

6.11.0-109019-tuxedo.

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

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

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?

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.

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