Page 1 of 1
LinuxMint to avoid snapd
Posted: Wed Jun 03, 2020 12:53 pm
by manyroads
Interesting comments regarding the need to avoid snapd from Clem (the lead) at Linux Mint.
https://blog.linuxmint.com/?p=3906
Re: LinuxMint to avoid snapd
Posted: Wed Jun 03, 2020 5:08 pm
by andyprough
Can't blame him, sounds pretty awful:
in the Ubuntu 20.04 package base, the Chromium package is indeed empty and acting, without your consent, as a backdoor by connecting your computer to the Ubuntu Store. Applications in this store cannot be patched, or pinned. You can’t audit them, hold them, modify them or even point snap to a different store. You’ve as much empowerment with this as if you were using proprietary software, i.e. none. This is in effect similar to a commercial proprietary solution, but with two major differences: It runs as root, and it installs itself without asking you.
Re: LinuxMint to avoid snapd
Posted: Wed Jun 03, 2020 9:07 pm
by woodsman
hmmmm... so what does how does chromium act in MX?
i used chromium and like it. tried firefox 2x and the last time was when they had a major glitch a year or two ago that took them days to fix; and most people were pissed. me incuding. so went back to chromium and using it since then. so what is it dong on my system? how can i stop stuff or fix stuff if needed. sorry for my denseness.
Re: LinuxMint to avoid snapd
Posted: Wed Jun 03, 2020 9:38 pm
by andyprough
woodsman wrote: Wed Jun 03, 2020 9:07 pm
hmmmm... so what does how does chromium act in MX?
i used chromium and like it. tried firefox 2x and the last time was when they had a major glitch a year or two ago that took them days to fix; and most people were pissed. me incuding. so went back to chromium and using it since then. so what is it dong on my system? how can i stop stuff or fix stuff if needed. sorry for my denseness.
MX does not use Snap packaging by default - this is a Ubuntu problem, not a problem with chromium outside of Ubuntu's repos. Mint is having to deal with it because their distro is based on Ubuntu. Your chromium on MX is fine.
Re: LinuxMint to avoid snapd
Posted: Wed Jun 03, 2020 9:40 pm
by woodsman
thanks - i kind of thought that but what do i know. I am glad i am here using MX! not a fan of ubuntu based stuff anyway. thank you.
Re: LinuxMint to avoid snapd
Posted: Mon Jun 08, 2020 10:31 am
by manyroads
Re: LinuxMint to avoid snapd
Posted: Mon Jun 08, 2020 2:51 pm
by KBD
Awhile back I thought I'd give Ubuntu with snap a shot. I set up a server using Ubuntu and the Plex snap package, I foolishly thought I'd have fewer issues with Plex as a snap package. It was buggy from the start, and within two months the Plex snap package on Ubuntu was broken beyond repair and I had had enough. So much for making thing easier. Clem is right to avoid that junk.
Re: LinuxMint to avoid snapd
Posted: Mon Jun 08, 2020 3:29 pm
by SwampRabbit
For all things Ubuntu has done to help Linux, sometimes I wonder if they are trying to provide choice and competition, or just doped up on smack.
Member when, Buntu...
- moved window buttons to the left
- came up with the idea of Unity
- had hidden dash search controversy
- tried to make a init system
- defaulted a opted-in system usage data collection
- decided to remove 32bit support
- tried to snap you with snaps
- blah, blah, blah
Ubuntu has done many good things, but they have also shot themselves in the foot a bunch.
Re: LinuxMint to avoid snapd
Posted: Mon Jun 08, 2020 4:01 pm
by dreamer
SwampRabbit wrote: Mon Jun 08, 2020 3:29 pm
- tried to make a init system
I never had a single problem with Upstart between 2008 and 2014. I never had a single problem with sysvinit either. systemd on the other hand... but it seems stable now. I think Upstart was default even in Debian for a release and is still default in Chrome OS. When Red Hat backed systemd and then Debian adopted it I think Canonical saw no reason to continue with Upstart. Basically they didn't want to do the work that antiX/MX Linux is doing.
Re: LinuxMint to avoid snapd
Posted: Mon Jun 08, 2020 4:20 pm
by SwampRabbit
dreamer wrote: Mon Jun 08, 2020 4:01 pm
I never had a single problem with Upstart between 2008 and 2014. I never had a single problem with sysvinit either. systemd on the other hand... but it seems stable now. I think Upstart was default even in Debian for a release and is still default in Chrome OS. When Red Hat backed systemd and then Debian adopted it I think Canonical saw no reason to continue with Upstart. Basically they didn't want to do the work that antiX/MX Linux is doing.
Wasn't saying there was an issue with Upstart, just that they spent the time and resources to create it, then abandoned it.
Ubuntu could have kept up with Upstart (or Unity), like you said "didn't want to", but they could have and still can back sysVinit.