Both servers were running musl libc instead of glibc for a while. This gave me a couple of random issues, but eventually I got tired and switched back to glibc.

musl in a nutshell

since i3 dies not work on Wayland.

Might wanna drink a bit more coffee btw (sorry I couldn’t hold it lol).

?

I said: “I will daily drive wayland once sway fixes their compatibility bugs with i3” That is I am not using wayland at the moment and I’m using i3 (x11) due to bugs in sway.

Sway is the wayland window manager that is a “drop in” replacement of i3. I can’t use it right now because it has several bugs that prevent me from using it.

I will daily drive wayland once sway fixes all their compatibility bugs with i3 and once polybar works on wayland as well.

It is a bug, and not only that, it is KDE6 related lmao. It’s the steam bug again!

Flatpak usually ships very outdated drivers.

I’ve been in the support channel for yuzu linux, and you would not believe all the issues people have with games freezing, etc that are instantly fixed by using the appimage instead of the flatpak.

Also flatpaks are non-xdg compliant, since it creates the useless ~/.var directory. And they have said over and over that they won’t fix that. So fuck them.

Not to mention all the issues people have with their theming and integration into the system.

Appimages are just simpler and better, the other day I was thinking how many issues would be fixed if Steam shipped as an appimage.

• It would allow for shipping a patch glibc with EAC
• It would allow for moving all the nonsense that steam puts in the home user dir, since appimages support a portable home.
• It would allow for shipping the 32bit libraries instead of having to install them system wide.

And depending on how you go about, appimages will even take less disk space than flatpaks or native packages even though you don’t get shared libraries with those, because they are compressed which reduces their size significantly.

Like for example the LibreWolf appimage is 110MiB while a the native package for librewolf 300MiB. Same with LibreOffice, the appimage is 300MiB while the native package is 600 MiB.

It also makes it easier to downgrade if you run into an issue, like I had to had an older appimage of ferdium because the latest version is affected by an electron bug that broke its zoom functionality.

My time with nvidia on linux was 0 issues in performance or usability.

The only sort of issue that I had was that the GTX 1060 drew 20W at idle when using the 3 displays, this was a bug that nvidia fixed for the RTX 20 series and newer cards but never fixed for pascal lol.

But even on BeamNG, there was a period were the native linux version didn’t work on mesa while it worked for nvidia, now to be fair with amd this was because the vulkan implementation of beamng is horrible and right now it does not work on either lol.

I have a similar story with an RX580, I replaced my GTX 1060 3GB for a 8GB RX 580 mostly because the 3GB of vram were an issue for BeamNG.

Now I can’t record my 3 displays with the RX 580, it just fails when trying to do so, and 2 displays results in constant encoder overloads, something that the 1060 had issues at all, also my colors are off when recording and I have no idea why, it even happens when recording with the CPU:

https://bbs.archlinux.org/viewtopic.php?id=292196

Also kernel 6.6 broke the power reporting on all polaris GPUs, thankfully that was fixed recently in kernel 6.7.2, but holy shit it took like 6 months to fix that.

I don’t distro hop, but I keep my most commonly used programs as appimages in my home, as well as some locally compiled programs that I install in ~/.local/bin and ~/.local/lib.

Those include essentials like:

• i3wm
• polybar
• rofi
• handlr (regex one)

And for the programs, those include:

• brave
• ferdium
• freetube
• gimp
• librewolf
• libreoffice

That way I can drop my home onto any distro and everything will work at once. No need to manually install programs.

I also have wrapper scripts on my PATH that force applications that don’t comply with the xdg base dir spec to use a fakehome in ~/.local, like steam and the web browsers.

Been using Btrfs for a year, I once had an issue that my filesystem was read only, I went to the Btrfs reddit and after some troubleshooting it turned out that my ssd was dying, I couldn’t believe it at first because my SMART report was perfectly clean and the SSD was only 2 years old, then a few hours later SMART began reporting thousands of dead sectors.

The bloody thing was better than smart at detecting a dying ssd lol.