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

https://lemmy.world/comment/8762394

since i3 dies not work on Wayland.

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

MiB and MB are not the same thing. Just that many CLI tools in linux use MiB instead so I just got used to typing MiB lol.

Because it is not exactly 10MiB. Should have used about instead of like though.

https://github.com/swaywm/sway/issues/8002

https://github.com/swaywm/sway/issues/8001

https://github.com/swaywm/sway/issues/8000

Also this issue which affects xfce apps in wayland:

https://gitlab.xfce.org/xfce/thunar/-/issues/1304

I also need to find a way to do “window devour” in sway.

I also tried Hyprland and it was a total nope for me, I wasted my time reading the wiki pinning workspaces to certain monitors only for hyprland to tell me that shit was deprecated. I also found that I can’t move a floating window between displays in hyprland, as the move left/right commands move the floating window to the left or right of the display and don’t actually move it left or right, that means the window gets stuck in the left or right side of the display when trying to move it into the next.

edit: And my polybar is a long config for multiple displays as well that has several features I worked on and I really don’t wanna bother migrating to another bar:

https://imgur.com/2GXp2L6.png

I have indicators of cpu usage (which when click change the cpu scheduler), mem, gpu, etc, It also prints the names of the windows in the scratchpad which is the Xfce4-terminal Mate-calc in this case, the current workspace, the window class name and instance of the window with focus, the currently playing music track with playerctl, the volume in decibels, the current network speed, etc.

doas uses like 10MIB less of mem than sudo.

?

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.

In this case the issue was that a change between kde5 and kde6 let to the variable being defined as somepath / (notice the space).

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

They are already doing that, and plenty of commits as well.

The main question now is if it will be further developed once they get the automatic builds up again. The good news is that Yuzu doesn’t need much improvement now, just a few days before the lawsuit they did some very needed vram usage fixes so now development only has to focus on getting future titles to launch.

edit: Of course I’m talking about the pc builds, Getting android to work was a nightmare even for the original devs

You don’t have steam-runtime instead of steam-native on nix?

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.

Oh, sorry I thought you were talking about the I/O plate.

TIme to use an open frame case then lol.

Brave has configurable keybinds, you can set any key you want to do anything.

However I still need to use the vimium extension to have proper keyboard only web navigation, because with the exception of qutebrowser none of the “popular” web browsers have the select link mode with the f key.

I’m pretty sure the second one will work on any case, just that you might be missing the I/O plate.

I have had several used dell / hp motherboards, the only thing proprietary was that some were 12V only and needed a 6 usd adapter to work with regular atx psus.

And also the power button connector, you have to figure out which pins are the ones that turn the PC on.

Is that a PWA? Firefox used to support it.

Oh I can tell you that zram will not result in an OOM that zswap would prevent:

I once ran into a bug when using foobar2000 with wine to convert my music library that resulted in an insanely high ram usage, like my 16 GIB ram was filled and then my 32 GIB zram was also filled and the PC froze.

I just went and edited my zram config to make my zram 48GIB and ran foobar again, it ended the conversion without issue kek. No idea wtf happened but whatever data was being written in memory was being compressed good by zRAM, like very few people would even use a swap partition or file that is more than 32 GIB to begin with.

I also tested running Zelda tears of the kingdom in yuzu using 4GiB of ram with a big zram and it worked, that game in yuzu is a ramhog and on windows people need 16 GiB of ram and they still max out their swapfile.

There is also a vid on yt titled zram vs windows pagefile where a user running endevour demostrates how zram can take a bunch of Minecraft mods while windows with the help its of pagefile cant

Edit: Here is the vid: https://www.youtube.com/watch?v=nMYTBsjeoTc