Manjaro: Lots of criticism from others, ironically ran 2 years without major issues. But I wanted to switch to btrfs and EOS was hyped up to be a better version of a simple Arch installation.
I had a similar story, in fact EOS has a problem that they use dracut by default and is set to overwrite the kernel parameters every time you update the system lol.
I’m very sorry you had to deal with some users from here btw, specially the nixos people.
Thank you for posting this @boredsquirrel@slrpnk.net
I will later see if I can convince the gearlever dev to add aisap support, since that app targets flatpak users.
Also during testing Ivan discovered something interesting in fedora, sometimes some of the xdg-user-dirs variable for some reason were being defined as $HOME/ with a trailing slash instead of $HOME/Scrivania (desktop) for example, even though they were clearly defined in the conf file of xdg-user-dirs.
am has a check in the sandbox script that unsets these variables and makes aisap use their default location when that happens to prevent giving full access to $HOME, I don’t know if flatpak has similar measures in place.
I find it funny that thumbnail with a “fail” I’m actually surprised that it got 48% right.
In the old days distros used to separate the location of binaries in several places like /bin /sbin /usr/bin and /usr/sbin there was this idea that system binaries would go in /sbin while the rest in /bin and the similar dirs in /usr were so that you could mount a separate drive to store more binaries. This is from a time where storage was an issue.
These days distros usually just symlink all those locations to /usr/bin with the exception of fedora, which still keeps some split.
However it seems they will finally merge the remaining dirs in fedora 41: https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin
(once Flatpak get that too, there is no valid reason for snaps to exist).
They said they will not fix it due to “security concerns”
Isnt fedora like the last distro that doesnt symlink /bin and /sbin to /usr/bin?
What kind of non argument is that lol
I also have the UR20.
I use my ksc75 daily with the headphone jack.
Try using yuzu-mainline-git from the aur and change your compile flags (edit makepkg.conf) to match=native mtune=native and O3. That gives a 15% boost in totk.
Also use zram instead of zswap as that that causes terrible stuttering on yuzu if you are short of ram. The usual recommendation is to use zstd compression but I can tell you that lz4 performs better on yuzu.
“sudo pacman -S zram generator” then “sudo nano /etc/systemd/zram-generator.conf” and paste this:
[zram0]
zram-size = ram
compression-algorithm = lz4
swap-priority = 100
Also make sure you are running gamemode with yuzu. Same with steam games.
I moved from a gtx 1060 to an RX580 and it has been terrible, recording in obs is horrible to the point that the cpu yields better results and now a recent kernel version broke the power meter on all the polaris gpus.
i3 is actually exporting the enviroment variables when I set them in its config file, however for some reason qt5ct and all the qt apps refuse to use it, running printenv confirms that it is there.
However I found the issue, it seems to be an issue with my zsh shell, because I just created ~/.zshenv and added my enviroment variables there instead of on ~/.profile and now it works like it should kek. I didn’t have to do this before when using lightdm so no idea what exactly changed though.
It is likely that the qt enviroment variable needs to be exported very early and that is why doing it from i3 doesn’t work but from the shell it does.
Alright, adding the variable directly to /etc/enviroment made it work.
I also tried exporting the variable from my i3config and that didn’t work.
Though why isn’t it working like it did before with lightdm? Feels a bit wrong editing enviroment directly idk.
PWA ffs