Call for testing: chromium-browser deb to snap transition

Hi @oSoMoN

This is the current user agent string of the snap:

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/78.0.3904.97 Chrome/78.0.3904.97 Safari/537.36

This is the user agent string for the deb package:

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/78.0.3904.97 Chrome/78.0.3904.97 Safari/537.36

I can confirm that works if I change snap to Ubuntu in the user agent.

Is it possible to reconsider having a separate browser string for the snap? Given that a website as popular as doesn’t work, it probably won’t be the only one. I’ve had to contact so many websites because they incorrectly blocked Linux and Chromebooks, I’d hate to have to do this again for the snap now.

Moreover, having a distinction between the snap and deb user agent increases the browser fingerprint, making it easier for websites to track us without our permission.

Given that the Chromium snap is strictly confined, chromium is in fact running in Ubuntu as far as Chromium is concerned.

Ubuntu used to include the version number in the UA, but this hasn’t been the case for a while now. I suspect that was removed for similar reasons.


I have set snap set core experimental.refresh-app-awareness=true but I keep losing some data when snap updates.
I usually never restart chromium (30 days uptime on my laptor currently). And here what I think is happening:

  1. snap updates, copies .config/chromium
  2. I keep using old version of snap which is using old .config/chromium
  3. After couple of hours I open some url from another app (executes chromium https://...), running version of chromium crashes (maybe because newly executed chromium points to another .config/chromium).
  4. New version of snap executes, but missing a data from those couple of hours. And I can confirm this data in .config/chromium of old version of snap.

This will probably affect few people but I pretty much immediately discovered that the snapped Chromium could not access files in hidden directories. (I extensively use .local/opt, .local/src, .local/include, etc. – so I guess it was bound to happen sooner than for most people.)

GooPG uses native host messaging, which currently won’t work because of bug #1741074.

1 Like

Chromedriver is working here with the snap. You can have a look at the snap’s own basic tests, which are installed in /snap/chromium/current/tests/, for example the chromium-version test.

The most important bits are:

options.binary_location = "/snap/chromium/current/command-chromium.wrapper"
driver_path = "/snap/bin/chromium.chromedriver"

I haven’t had a chance to test this with more complex setups though. If this doesn’t work for you, please file a bug with details about your setup. Thanks!

This is very unfortunate. It’s 2019 and companies still produce web pages that enable/disable features based on UA sniffing. I’d suggest using an extension (e.g. User-Agent Switcher for Chrome) to work around the problem.

The “snap” token was added to the UA string initially to allow to identify unambiguously a system that knows how to handle snap:// links, to provide accurate installation instructions. This isn’t ideal, but it’s not something we can easily revert either.

Indeed. An extension to override the default UA string sounds like a good mitigation for privacy concerns.

That’s not quite correct. The app is running on whatever the host system is, but it has a very limited view of that system. The fact that the snap was built on Ubuntu is an implementation detail, even more so in the case of chromium which embeds and builds many of its dependencies at build time.

Indeed the home interface disallows access to .dot files and folders immediately under $HOME/.

With experimental.refresh-app-awareness=true the snap won’t be updated while it’s running.

I am however seeing something that might explain your issue. I also have experimental.refresh-app-awareness set to true, and I have chromium running pretty much all the time, so it doesn’t leave it a chance to update. When I reboot my machine, however, is when the snap gets updated if a new revision is available. The application won’t launch until the snap is updated, however copying the data in ~/snap/chromium/ from one revision to the next might not be complete by the time the app is started (the browser is usually the first app I launch, and the profile directory can grow quite large), so the browser will start with an incomplete profile. This is definitely an issue with snapd.

I have described it in more details there.

It doesn’t look like my case:

% ls -la ~/snap/chromium/current
lrwxrwxrwx 1 baz baz 3 Nov 22 13:11 /home/baz/snap/chromium/current -> 949

“currect” link was relinked at 13:11, while I was using old version of snap until 15:32:

% ls -la ~/snap/chromium/937/.config/chromium/Default/Login\ Data
-rw------- 1 baz baz 589824 Nov 22 15:32 '/home/baz/snap/chromium/937/.config/chromium/Default/Login Data'

And just in case:
% sudo snap get core experimental.refresh-app-awareness

So it looks like refresh-app-awareness is not working as intended for you.

May I suggest you comment to explain the problem on the snapcraft thread I linked to in my previous post?

Cool. I still don’t know if it’s how the container apps behave or something else. But I’m expecting a way for root and other places.

Till very recently, it was Pop!_OS theme available from their own PPA. But now it’s the Ubuntu bionic default theme: Ambiance. I guess there should be a way for this apps to copy system defaults or ask the user if one prefer override it or use what is already set.

Good to know, thanks.


It’s not quite true. You are just relying on the command line but:
$ du -hs /snap/chromium/958
574M /snap/chromium/958
$ snap info chromium | grep installed
installed: 78.0.3904.108 (958) 160MB -

Please notify me if I’m wrong. I’m just looking at the numbers.

I may doodled it around. But as I told not important. For what reason should I adjust 60GiB and not using it!

Also there is more!
I don’t know how should I report this bug. When I click on Home shortcut on the left side of “Select file” window, this happens. I guess it’s pretty straight forward and no need any comments.


…at the wrong ones though :slight_smile:

/snap/chromium/958 is a mountpoint, you are looking at the content of a compressed readonly filesystem file that happens to be loop mounted there … the actual size it occupies on disk can be found via:

$ mount | grep chromium\/958
/var/lib/snapd/snaps/chromium_958.snap on /snap/chromium/958 type squashfs (ro,nodev,relatime)

$ ls -lh /var/lib/snapd/snaps/chromium_958.snap
-rw------- 1 root root 154M Nov 26 09:28 /var/lib/snapd/snaps/chromium_958.snap

… indeed, that you have multiple revisions on disk makes it occupy more space in the end but not as significant as it looks like from looking at the mountpoint content :wink:

Also note that desktop snaps are only a fraction of what is in the snap store, on the “snapped-server/cloud-software” or “snapped-iot-software” side many snaps make actual use of the builtin auto-rollback features and self-testing that come for free with the snap package format … sadly you cant have (auto)roll-back features without having the former data and binaries around, so the above is a design requirement.

…and the same goes for home dirs … which is why snaps execute with a versioned home dir pointing to ~/snap/<packagename>/<version>. We allow you to disconnect the home interface at any point in time for any snap (and on some systems it does not get auto-connected at all). To still give an application a proper $HOME to work in even when there is no way to access the real users home they default to this setup. So the difference you see between deb and snap regarding home dirs is also by design…

Chromium snap is unresponsive or 5-10 seconds upon launch, and randomly while in use.

I never saw this issue before installing the snap.

This system is no slouch. 4 cores, 8 threads, 32G ram (16 free)… While I’m waiting for Chromium to respond to my command (click, typed input, whatever), I can run top in a console and there isn’t anything out of the ordinary.

1 Like

I understand the logic for using a sandboxed $HOME, but this means I cannot use Ctrl+L ~/src/someproject/my.patch in the file dialog when I’m trying to attach patches to bugs, which is annoying.

1 Like

Would you mind filing a bug with as many details as possible, so we can start the investigation there?

My feedback after using snap Chromium for ~6 weeks (Kubuntu 19.10):

:grinning: Neat. I almost forget I am using a snap.

Known issue: I encountered the “losing new profile changes (bookmarks in my case) if Chromium updates while it’s running” problem. Until this is fixed I would recommend the snap only to people aware of this risk.

Startup time is fine (old 2011 computer too).

Known issues in Launchpad: mouse cursor changes to odd hand cursor when hovering over links, mouse cursor is a black traditional cursor rather than my preferred white KDE-style cursor.

Fixed recently: brief white flash of GUI elements (e.g. right-click menus) before getting ‘filled in’ was mildly annoying. Presumably related to Nouveau graphics driver.


Thanks for the feedback!

For the issue with chromium being silently updated while it’s running, I recommend turning on the Refresh App Awareness experimental feature, which will prevent exactly that:

snap set core experimental.refresh-app-awareness=true

This should be fixed when this MR is merged:

It’s been sitting there for a while, waiting for someone from the desktop team to review it.


Since the Chromium 79 snap, this seems to no longer work.

I have the from Firefox in ~/snap/chromium/current/.local/lib/, which always worked fine before, but now EME videos all just show warnings and the plugin does not seem to be loaded.

Extracting the from a Chrome deb and putting it in the same place also does not help.