Call for testing: chromium-browser deb to snap transition

snap
33

This is tracked by bug #1732482.

34

Thanks for raising this issue here. I commented on the upstream bug.

35

chromium.launcher keep spawning sleep 60

36

It’s not possible to share files through /tmp. The snap chromium doesn’t have access to /tmp and maps /tmp to /tmp/snap.chromium/tmp. The regular users needs super user permissions to access /tmp/snap.chromium/tmp. This is a really sad thing.

37

This was an undesirable side-effect of the initial implementation of bug #1864901, but it should now be fixed with the latest update.

38

This is being discussed in a separate thread: Sharing files via /tmp.

39

$ snap info chromium
name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: Canonical✓
store-url: https://snapcraft.io/chromium
contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license: unset
description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
commands:

  • chromium.chromedriver
  • chromium
    snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
    tracking: latest/stable
    refresh-date: 3 days ago, at 21:41 +03
    channels:
    latest/stable: 81.0.4044.129 2020-04-29 (1135) 161MB -
    latest/candidate: 81.0.4044.129 2020-04-28 (1135) 161MB -
    latest/beta: 83.0.4103.23 2020-04-25 (1125) 163MB -
    latest/edge: 84.0.4128.3 2020-04-29 (1136) 164MB -
    installed: 81.0.4044.129 (1135) 161MB -

i can see a process right now. launcher

40

The fact that there’s one process running right now is perfectly normal, the problem was when multiple instances of it were kept running after exiting chromium.

41

Spawning a sleep 60 every minute is not normal why does it needs that?

42

Where can i find the answer of this question?

43

It’s explained in the bug that @oSoMoN linked to https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901). The process looks for a change in the chromium snap current symlink and then alerts users when the snap has been refreshed while running.

44

so there is no solution to this and the guys chose “this is not a bug, this is a feature” approach.

45

no, its a UX tradeoff for security and they are obviously looking for fixes/workaround in that thread (making all apps properly share files through the Downloads folder etc)… you make it sound like the problem has been completely ignored …

46

Almost three years passed, but nothing came up. Why there is just no interface for using file system there you can explicit set which places snap can look in? User themes and icons are broken for same reasons too. So I have to pack my icons and theme as a snap package and manually connect it for all of snaps. Really? May be this is the wrong place, but I am really fucked up about it since canonical dropped chromium deb packaging.

47

well, there was an internal developer sprint last week where there was another session around shared /tmp … but since there is a properly usable workaround to share files through ~/Downloads it is simply not high prio … so it will be worked on once someone has time and the more pressing and more serious issues are off the plate … the issue is known and typically we dont “just forget” about such stuff …

if you want to speed it up, propose something … make a PR, etc … the snapd source is at:

please tame your tone, we try to keep this forum family friendly …

48

Just noticed the following with Chromium Snap shipping on Ubuntu 20.04 - when creating WebApps (via menu -> More tools -> Create shortcut), the .desktop file generated links to the specific Chromium Snap version used. Therefor, as soon as a new Chromium Snap version is released and the old one is purged from the system, all WebApps break. A workaround is to edit all .desktop files and replace the explicit version with current, but the user has to repeat this for every .desktop file. Ideally, Chromium Snap should by default create .desktop files which link to current automagically. See https://askubuntu.com/questions/1236993/chromium-snap-webapps-stop-working-after-chromium-update-fix/1236994#1236994 for more info.

4 Likes
49

There are 2 “open a new window” menu entries in dock on right click on ubuntu 20.04.

VirtualBox_2004_02_05_2020_22_23_03

50

I can confirm, but this is not a regression in 20.04. The chromium-browser package in 18.04 shows the same. This is because the first entry is automatically added by the dock for all pinned apps, whereas the next 3 entries are defined in the desktop file for chromium.

I have tested adding a NotShowIn=GNOME stanza for that specific entry in the desktop file, but it doesn’t seem to have any effect.

1 Like
51

Is it possible that this is a snap thing? Due to lack of chromium browser in repositories, I just compared 20.04 ubuntu deb and snap versions of firefox. The same problems - snap has a redundant menu entry for new window.
firefox_deb_snap

52

Hi, out of snap apps could not start any more. Spotify or Zoom have client apps and xdg-open can not start them any more. Is there a workaround please ? An ability to facilitate migration.

May 18 10:10:00 hostname chromium_chromium.desktop[1293869]: user-open error: Supplied URL scheme “spotify” is not allowed

It seems the same problem exist with Firefox : https://bugzilla.mozilla.org/show_bug.cgi?id=1463091