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.
Hot take: PPAs suck and snaps/flatpaks are better.
With PPAs, inevitably some repo that hasn’t been updated since 2015 causes dependency conflicts and you have to sit there and troubleshoot, or pick between the software you need and actually having an OS that’s not EOL. With snaps, you can keep your decade old dependencies all bundled up and still upgrade your system even if the package maintainer has abandoned it.
The issue people have with snaps isn’t the containerization or the bundles, but the proprietary backend. There is no way to point the snaps at a different store other than the one canonical controls. Canonicals forcing snaps on people pisses a lot of people off because it’s a blatant power grab, an attempt to get people dependent on something they have control over in a microsoft-esque move. Flatpaks and docker don’t have that issue.
Hot take: it doesn’t feel nice to have a change forced.
It should be the personal preference of the user to decide whether to use native or snap/flatpak. If native package manager decide to not support the package any longer it would be better to make user aware and stop maintaining app, than to install a snap package. This is a user’s decision.
Also this can have far reaching consequences. Imagine you cannot use/install snaps on your machine due some reason, what now?
I tried so hard to embrace snaps and flatpak. I really did. But the snap service kept bogging down. Installs specifically of Firefox were ponderously slow to start up. And ultimately I ended up with regular installs, PPAs, snaps, and flatpaks all together with their own daemons, update paths, and quirks sucking up my system bandwidth and emotional resources. System was constantly slow. Felt like I was running Windows.
I flipped over to endeavours, really enjoying it. Feels like Ubuntu did in the earlier years. Great support community, lots of choice, but a straightforward path to just using your system if that’s what you’re there for. And the same computer runs a good 25% faster.
Valid opinion and immutable distros like silverblue might be where the future is headed.
It’s not the point though, I’m not going with a distro that tries to force their proprietary solution on me.
Not a fan of immutable distros like Silverblue because you’re giving a lot of control to the upstream, unless you have the ability and time to maintain those system images yourself. And if you’re doing that, except for within an organization, there’s not a huge reason to not just use a traditional distro.
If you don’t want that control, they’re great.
In NixOS you can do an overlay and just make your own package. If the package works, you can submit it to the NUR. If it’s good, you can maintain it in the official channel. I’m doing both, the crappy fork of some GUI is in the NUR, the underlying service is maintained by me in nixpkgs
Nix had a huge learning curve for most folks, but it doesn’t suffer most of my complaints about control.
Ironically a full Ubuntu modular system made up of a bunch of snaps wouldn’t necessarily either. One of the cool things about snaps is that they can hold the kernel and other lower level things so you could build a “snap”-together immutable system out of various components.
Silverblue and its variants are a monolithic system image though.
Or how about… they each have their advantages and disadvantages, and therefore are each better suited to different uses and it doesn’t have to be a competition?
So your saying a Snap based Firefox use case is limited to downloading a different browser… so it’s effectively IE6? I agree, if that’s what you are saying.
PPAs suck, no doubt. But the thing is, if snap is so superior, just switch your whole distribution over to it and be done with it. Don’t do this underhanded switcheroo with individual packages spread over so many years.
The crux here is ultimately that snap just doesn’t look to be up to the task of replacing
.deb, otherwise they’d have already done it. But they still want their proprietary appstore, so they have to make snap relevant by force.I can agree with that only if they solved the problems with extensions and a few other features that were not working with the snap version. If they did not, then they are assholes.
I use keepass to fill login forms, and that does not work with the snap version.
Just curious if you know why? I thought snap was just a package format, not a siloed container.
In my case, KeePass and ExpressVPN could not function. For KeepassXC, this was the reason:
It appears they found some work-around with an extra script after installation as of 2 years ago. Basically, snaps are sandboxed, which is a feature. That wreaks havoc with certain tools, though. ExpressVPN’s browser plugin was having similar problems, and on Linux, that’s you’re only GUI interface for ExpressVPN.
I just checked, and I was updated to the Snap version, and I had no problems with either extension, so they did solve the problems. Therefore, I’m not outraged. Ubuntu has the right to standardize their deployments on a system that makes their work easier or less chaotic - as long as it does not screw over their customers.
Edit: i was mistaken. I still use the Mozilla PPA, so the problems migjt remain.
I haven’t had any problems with using Snap. I am currently switching from Chrome to Firefox. Firefox has ran great with Snaps so far.
But I also have an Nvidia RTX 3080. The Linux community hates both Snap and Nvidia. But they are working fine for me.
I tried PopOS but they didn’t have the current drivers for my Nvidia card, so I switched back to Ubuntu. This was about a year or so ago
I’m on ARM, arm64 to be more specific. There’s no native Widevine package for the browsers. There is a way to rip it from the new chromeOS for arm64, and to then plug it into chromium and firefox… but not with snap firefox. And to top it off, flatpak doesn’t even have firefox or thunderbird for arm64.
The NVIDIA driver in Pop!_OS is currently 535.98. I’ve been using a RTX 3080 with Pop!_OS since the pandemic lockdown.
I am at work and can’t check the driver version but they sound like the current one.
How is Steam’s new big picture mode running for you under Pop!OS? I used to run Wayland with Steam’s old big picture mode but had to go back to x because it wouldn’t work.
Agreed. I’d rather install manually than use a third-party PPA. I’ve had way too many problems, especially when it comes time for an OS upgrade.
I see this as a false dichotomy. The point of a distro is to have a wide array of stuff tested and available in official repositories. If the official repositories only contain half-assed snap ports, what’s the point? I either suffer with a shitty Firefox or jump through more hoops than ever before to install it from external sources? Ugh.
I’m on Ubuntu again, and I’ve had it up to my eyeballs with snaps. When the time comes to upgrade again, I’m either going back upstream to Debian, or downstream to a de-snapped Ubuntu derivative.
Yes, that is the acceptable use case. Aging, I maintained software in a usable form. Not “we’re showing off our container engine so everyone has to use it now”.