What use to be the PPA that allowed Ubuntu users to use native .deb packages for Firefox has recently changed to the same meta package that forces installation of Snap and the Firefox snap package.
I am having to remove the meta package, then re-uninstall the snap firefox, then re-uninstall Snap, then install pin the latest build I could get (firefox_116.0.3+build2-0ubuntu0.22.04.1~mt1_arm64.deb) to keep the native firefox build.
I’m so done with Ubuntu.
I get that people don’t like being forced, but otherwise I couldn’t care less about Firefox snap vs deb. All problems I once had have been ironed out. On the contrary, I like sticking to the “recommended” path with more developer focus and hopefully higher stability. For my usecases I have zero problems with snap.
For one, the snap version is 115 instead of 116, so it’s reverting me to an older version, which makes firefox want to wipe my profile. Not ok. Two, I was purposely using the Mozillateam PPA to get non snap installations, and they up and changed that on us with no warning. Then there is the matter that firefox as a snap is slower. And finally, I can’t add the Widevine for arm64 plugin to the snap.
Snap for browsers is a terrible idea.
If it works for you, fine. I still have this bug to deal with which makes snaps completely unusable in our environment.
Maybe I should try petitioning for us to at least use Linux Mint.
Same for our student PCs - As soon as the setup includes network homes snap becomes completely unusable. Applications just crash on startup because snap doesn’t allow them to access the user’s home directory
I also hate that anyone would side for snap based browser installation, and that any of you are upvoting it is horribly icky.
I like my apps to be contained somehow. I don’t like all the choices canonical made with snap, but I like containment.
Your responses here tho, yeah. Icky.
I like some things as flatpak or appimage. But not my browsers, I use a hacked in widevine plugin.
