You are free to have your opinion but this discourse is not a forum, it’s a work and collaboration place so please find another platform to post such messages.
Can we get this post withdrawed or deleted, it’s off topic and derailing the technical discussion happening.
as someone who worked on the initial snap implementation back then (still python based when we started snaps in 2014) i can tell you that we did neither look at nor know about “klik” at that time
but all your other historical statements are 100% correct …
flatpak came to existence in 2016 (or rather the idling xdg-app development got picked up under new name), about a week after we announced desktop support for snaps (cli, daemon and server snap packages for IoT had existed for about two years at that time already)
I have just upgraded my raspberry pi 4 on arm64 from 19.04 to 19.10.
The latest chromium-browser worked on 19.04
After the upgrade the snap chromium gives a title but black window
I have purged both chromium-browser and snapd then installed again.
from the command line I have
Failed to load module “canberra-gtk-module”
Draw call returned invalid argument. Expect corruption.
I installed libcanberra-gtk-module but no change
As my VSCODE relies on it, I am a bit stuck
What can I try to help diagnose further?
Has anyone had any problems with printing? Chromium from the snap won’t let me select the right printer. Firefox (no snap) works fine.
Details: I’ve like five or six printers in my system (because autodiscovery is a thing and coworkers’ laptops tend to advertise their home printers for some reason), but most of them are stopped to avoid being a distraction. There are two printers that are relevant to me:
the office printer
my home printer
I was trying to print a PDF from Google Drive at work today, and Chromium gave me only one option: my home printer (plus save to disk/google drive, but let’s ignore those). Actually, it’s even more interesting: Ctrl+Shift+P gave me the GTK print dialog with only that option, but a regular Ctrl+P gave me this native-looking Chromium dropdown that showed my office printer as an option but wouldn’t let me select it, automatically switching back to the home printer.
In case it matters, the home printer was selected as default in the system printers dialog. But nothing changed after I set the work printer as default and reloaded the Chromium tab.
I truly get it, but i don’t think creating an update script that detects deprecated debs and reinstalls them as snaps is that hard to do. It’s still intrusive but it turns out to be much more coherent in a long term.
You’ve just described what the apt package is doing.
Hi, I just upgrade for Ubuntu 19.10 and Chromium via snap.
Well, I lose all passwords that was saved in my Chromium browser.
Is there a way to restore those password ?
I am very interested in how you managed to access other partitions than $HOME. I think it is very limiting and unnecessary to introduce the restriction to $HOME and no other partitions and I don’t see how that really affects security.
If you connect the removable-media plug, you should be able to access files and directories mounted under /mnt and /media. That won’t resolve your issue with NFS shares seamlessly, but maybe you can mount them there?
Looking at that bug report I ran
snap connect chromium:removable-media
then I reported that drag&drop worked like it did before switch to snap.
I didn’t change my mounts as I didn’t want to, but I added an extra mount entry in /etc/fstab to load a my share in /mnt/ for the directories (NFS for me) that I wanted to be able to access in chromium. After that I had no issues (as this was 13-June-2019 my memory is a little faded… but what I did works for me equally well on my now Ubuntu 20.04).
Printing works for me today. I’m not sure what changed – snap autorefreshed the chromium snap yesterday in the background (causing another lost browsing session for me today, this is annoying, please fix that).
This move from deb to snap has broken a number of things that I would normally do with Chromium. I frequently use Chromium to navigate my system’s file hierarchy when doing web development, etc., and that’s no longer possible for files outside of $HOME, or inside dotted folders inside $HOME.
In addition, Jupyter relies on the browser being able to open a file in $HOME/.local/share/jupyter to open a session nicely in a browser.
This is enough of a problem for me to take the time to switch to Debian as my primary development environment, which is a shame, because Ubuntu has made some nice advances recently - this isn’t one of them.
It seems stable version of chromium deb available from here. Also Saikrishna Arcot maintain debs of dev-builds (“dev” only by name basically stable). So anyone who wants them can easily download and install them.
ppa:chromium-team/stable is largely unmaintained these days (we use a different PPA for staging stable updates, and it targets only xenial, bionic and disco).
The PPA by Saikrishna Arcot contains indeed packages for the dev version of chromium, and contrary to what you state it is not stable, there’s no guarantee that it won’t break or corrupt your data, so use at your own risk, and please don’t recommend it to normal users.
I haven’t verified whether CVE-2019-13720 actually affects the snap, but regardless, the snap is currently being updated to version 78.0.3904.87, you can expect an update in the stable channel in the next hours.
Glad to know that printing works again. I’m not sure why it wasn’t in the first place. Note that this is being controlled by the cups-control interface (auto-connected by default).
You might want to try app refresh awareness to address the problem with the app updating while it’s running.