Its even worse when you force Firefox to use wayland its icon doesn’t even show.
Edit: Oh since everyone now is confused; I only have the flatpak version of Firefox installed yet it doesn’t use the pinned icon and doesn’t even use the firefox icon under wayland at all.
@orcrist @lambda
There definitely is a problem that flatpak is trying to solve. That problem is dependency hell.
This most often (or rather most famously) occurs with python packaging. Sometimes you can have one package that requires a version that is incompatible with another version that another package requires. That’s why people use python venv these days (or just use pipx).
IMO a better way of solving this is with nix. With nix, it doesn’t require a container, it just builds in isolation.
Thing is, this will probably end up a VHS vs Beta Max.
I am very impressed by nix. I have tried nixOS and it was very nice. But, I might have to try the package manager as a standalone to see how I like that.
@lambda a lot of people do nix-env -ia nameOfPackage. I would recommend doing it properly with a file, and you just direct that command to the file (I would probably setup an alias). It gives you that declarative nature that nix is known for.
I’ll try that for sure. I need to lookup if nix packages work on Steam Deck…
@lambda they should if you use the single user command. The command that does it for the whole system requires root access, something you don’t have on the deck.
You can get root very easily. But, updates wipe out all but your home directory. So, I think you’d do the single user that you are referencing for that reason.
@lambda
Oh I didn’t know, I just remembered reading that it utilizes an immutable filesystem and thought that it also doesn’t give root access as well. That’s good to hear though.
Yeah, it’s immutable until you run the command
steamos-readonly disableIIRC.@lambda
Oh, good on valve for making that easy to undo, albeit until you update.