juipeltje

Yeah, i’m realizing more and more how convenient those variables are. I recently started using gtklock for example, a screenlocker that also has separate modules for extra functionality, which are also in nixpkgs, but the problem is that you have to explicitly specify the path to those modules in the config. So i wrote the config inside of home manager, and pointed to the modules path with the pkgs.foo variables. Worked like a charm.

I use NixOS, it appealed to me because i got to a point where i liked minimal distros like arch and void and i could build them up exactly the way i like them to be, however i didn’t like how i would have to go through that whole process again if i wanted to do a reinstall. With NixOS i can still craft my OS the way i like it, with the benefit of it being saved as a config, and easy to restore. I did make my own post-install script for void but NixOS is a more solid solution compared to my own janky script. I’m hoping to finally settle down on this distro. I guess the upside to the huge learning curve with nix is that it’s a good motivator to not abandon it because it would feel like my efforts to learn it would go to waste lol.

Fair enough. I wasn’t aware you actually had that problem yourself, i thought you just looked it up to prove a point lol. I do think it’s a weird decision that niri doesn’t just have xwayland built-in. Even river has native xwayland support, which is much more focused on minimalism. I haven’t used niri all that much because so far haven’t really been able to get used to scrolling. I think i still prefer dynamic tilers with a layout system. I should probably try booting up a game in niri to see if i can replicate it.

I think it does work, but from my understanding when nested inside another wayland session, thing like vrr don’t work, which brings me back to the xorg problem, but my current workaround works for me, so now it’s just a matter of hoping it will improve and become less tedious.

Issue is already closed though and might have more to do with xwayland itself it seems. Also fwiw, i just tested steam on niri with xwayland-satellite a few weeks ago and it worked just fine.

Yeah it’s at the point where i’m wondering if i still even need xorg. I’m still keeping it around just in case for now, but i could very easily purge it from my system anytime since i’m using nixos and all my xorg related settings are in a specific file. The main pet peeve i have with wayland is gaming related, and should hopefully improve when wine and proton go native wayland. I have a dual monitor setup and games always choose the wrong monitor by default, which means i can only use the resolution and refreshrate of the secondary monitor. I have a keybind to set the primary xwayland monitor with xrandr, which solves the problem, but it is a bit hacky. I also need to toggle vrr on and off with a keybind because it causes flickering on my monitor. It’s a bit annoying but atleast it works, on xorg you can’t even use vrr with multi monitor to begin with.

What’s wrong about that statement? Try installing SteamOS on Nvidia hardware and tell me how it went ;) why do you think Bazzite exists in the first place? SteamOS in it’s current state is not meant to be installed on other hardware, it’s a recovery image for the deck. Sure, if you have compatible AMD hardware you COULD do it, but you can’t even choose which drive to install it on cause there is no proper installer. If you want the SteamOS experience on other devices just use Bazzite.

I wonder what distrotube is going to use from now on since he’s an arcolinux user. He recently made a video about turning dtos into an installscript bundled with a base arch iso, maybe he’ll use that?

I’m not sure if they still are, but yeah i think they were made by sapphire as well. My vega was specifically a nitro+ though, so not a reference design.

Yeah openrgb is your best bet, but like others already pointed out it can be hit or miss. For example i used to have a sapphire nitro+ vega 64 and that thing never worked with openrgb in linux. They used a weird implementation that someone would have to reverse engineer in order to get it working, which to my knowledge never ended up happening. At the moment i’m using a reference rx 6950xt and it just worked straight away.

Seems like a strange choice. If anything i would’ve expected them to just use a firefox fork or something.