The Fedora software app has been promoting flatpaks over native packages, even not displaying that native packages are available even if they are, requiring the command line tool to access some native packages. So I don’t see how this is fundamentally different.
I hate that they also SEO’d the hell out of major search engines to show snap setup and installation instructions when anyone searches for installing a package. E.g. “arch install firefox” leads to snapcraft.io/install/firefox/arch which is downright dishonest marketing.
There as absolutely no reason for anyone in Arch to use snap to install something mainstream like Firefox. Same goes for other OS’s like Fedora etc. (which are all mined in similar way, just change it to /fedora for instance).
The page presents itself as if it’s the only choice, and can easily scam someone who’s just getting into Linux into installing snap. I think it’s designed for that purpose. Arch links to the package, but not step by step guide (which is on Arch), but this can easily lure people into installing snap and being none the wiser the it’s not the default package manager for their distro.
It’s 4th for Firefox, but I’ve seen it as the top result for some other packages. Probably Google caught up, or probably for packages not mainstream as Firefox it still shows snap as number one result.
The big difference is that Snap is partially proprietary. For those who like Linux for its free and open-source nature and all the benefits that confers, this is an unfortunate evolution that has a negative impact on the Linux ecosystem.
I’ve had no problems, as long as I’ve updated the keyring first sudo pacman-key —refresh-keys. I’ve probably gone a few times not upgrading my system for a while and I had minimal problems.
Ubuntu is getting on my last nerve. At this point I’m going Debian on everything except Thinkpad, but only because it’s Nvidia based and Pop!_OS just works on it.
All the servers I’ve spun up in the past few years have been Debian instead of my usual Ubuntu.
The last straw was kinda when I learned that installing docker via the install menu gives you the snap version instead of the normal one, with no indication that this is the case.
I’ve got an Arch server that I update monthly (and have been for 2+ years now), and a desktop that I update maybe 2-3 times a week. I’ve not had any issues, so long as I update the keyring first. Good luck!!
Good question. I have the same problem with flatpak (I have both 525 and 515 version installed at the moment) but I use the deb version of steam, not the flatpak one. I should try to remove them.
BUT, if I recall correctly, I still have something relayed to Nvidia 515 installed via apt (for example, when the kernel updates, I see that apt compiles the modules related to 515 together with the ones for 525).
I use VSCodium in Distrobox daily on Alpine Linux, and it works flawlessly. I don’t experience the problem you encounter but I use KDE Plasma which I suppose handles it differently.
I am however looking into slowly moving over to KDE’s Kate for development, my laptop really doesn’t like opening multiple chrome instances for the various instances of VSCodium and then also an Android emulator on top of that.
I can remember flatpak apps working each one with their own libraries, meaning app1 installed nvidia-drivers-535, app2 uses nvidia-430, app3…
U get my point, this is just a reference point tough since this comes from a vague memory about exactly this being controversial for all the redundancy it could cause.
I checked a few and all of them are bound to steam, nothing else, apart from the last one that’s also being used by Blender. At this point i think I’ll try uninstalling the oldest and check if steam still works. After that I’ll work my way forward. Thanks
Right now I’ve only removed the oldest driver, and steam opened fine. No complaints in it’s terminal output. For now I’m going to test a few games and once I remove a few more versions I’ll edit the post.
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.