[snap] No access to user config directory for separate app IDs

Bug #1848126 reported by hackel
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After the forced upgrade to the snap version of Chromium, all of my Chrome app shortcuts stopped working.

I have several apps which I launch like this:
chromium-browser --user-data-dir=/home/hackel/.config/appname --profile-directory=Default --app-id=abcdjdachboclehgmhnocadmlnkmehhi

They are now all broken.

So I can move my user-data-dir into ~/snap/chromium/current/.config and that works fine, but what do I do about the custom icons? These were created in e.g.
~/.local/share/icons/hicolor/*/apps/chrome-abcdjdachboclehgmhnocadmlnkmehhi-Default.png
for all 5 different icon sizes. But the corresponding snap icon directories are all broken symlinks to /snap/chromium/881/data-dir/icons/hicolor/64x64. (There actual directory structure ends with an empty icons directory.) A snap running as a user wouldn't be able to write to those directories anyway, right? Or does snapd have some mechanism to allow that?

If I try to use the Create Shortcut function in Chromium, I get this error 14 times:
LaunchProcess: failed to execvp:
xdg-desktop-menu

It doesn't actually create any .desktop or icons that I can find anywhere on the filesystem.

Is there time to restore the old deb package? This snap is just *not* ready for prime time!

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.