Closed Bug 1467094 Opened 5 years ago Closed 7 months ago
Import from the Chromium Snap profile doesn't work (Firefox can't detect Chromium being installed)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build ID: 20180517114003 Steps to reproduce: I've tried tried import bookmarks from Chromium browser on Ubuntu 18.04 Actual results: Firefox can't detect Chromium browser Expected results: Chromium browser detection
Hello, we are supposed to support Chromium imports on Linux but it's possible Ubuntu installs it in a different place. Can you open chrome://version/ while in Chromium and share the "Profile Path" directory?  https://dxr.mozilla.org/mozilla-central/rev/cec4a3cecc29ff97860198969b6fdff24b9e93bb/browser/components/migration/ChromeMigrationUtils.jsm#221,238-239
On Ubuntu 16.04 my profile path for Chromium is: /home/sfoster/.config/chromium/Default Import of Chromium bookmarks into a new nightly profile worked for me. It would seem odd (though I guess possible) that the profile paths would change in 18.04?
> Profile Path /home/ubuntu/snap/chromium/353/.config/chromium/Default Hmm… looks like the Snap uses a different profile path… I think https://git.launchpad.net/~chromium-team/chromium-browser/+git/snappy-packaging/tree/snap may be the code for the snap but I'm not sure since there are a few and I don't see $CHROME_USER_DATA_DIR or --user-data-dir= getting set there I'm wondering what the significance of "353" is in the profile path? I'm guessing we can't hard-code that in our search. We need to figure out how to find this profile path in a reliable way.  https://chromium.googlesource.com/chromium/src/+/master/docs/user_data_dir.md
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Summary: Bookmark Import from Chromium → Import from the Chromium Snap profile doesn't work
(In reply to Matthew N. [:MattN] (PM if requests are blocking you) from comment #4) > > Profile Path /home/ubuntu/snap/chromium/353/.config/chromium/Default > > … > I'm wondering what the significance of "353" is in the profile path? I'm > guessing we can't hard-code that in our search. We need to figure out how to > find this profile path in a reliable way. jlorenzo, any suggestions for how we could reliably find this directory from Firefox? I guess we would need to do the same for the other channels of chromium too if they use different paths.
That's a very good question! I'm not sure we can access the config of another snap. I didn't find the right permission to give. Moreover, we ship with the "strict" confinement, which restricts the access to the list given at . Ken, Olivier, is there a way to add new whitelisted paths to the confinment, without setting the level to something lower than strict?  https://docs.snapcraft.io/reference/interfaces  https://searchfox.org/mozilla-central/rev/c621276fbdd9591f52009042d959b9e19b66d49f/taskcluster/docker/firefox-snap/snapcraft.yaml.in#5  https://docs.snapcraft.io/reference/confinement
Component: Migration → Release Automation: Snap
Product: Firefox → Release Engineering
QA Contact: jlorenzo
Version: 60 Branch → unspecified
(In reply to Johan Lorenzo [:jlorenzo] from comment #6) > That's a very good question! I'm not sure we can access the config of > another snap. I didn't find the right permission to give. Moreover, we ship > with the "strict" confinement, which restricts the access to the list > given at . > > Ken, Olivier, is there a way to add new whitelisted paths to the confinment, > without setting the level to something lower than strict? > >  https://docs.snapcraft.io/reference/interfaces >  > https://searchfox.org/mozilla-central/rev/ > c621276fbdd9591f52009042d959b9e19b66d49f/taskcluster/docker/firefox-snap/ > snapcraft.yaml.in#5 >  https://docs.snapcraft.io/reference/confinement I know importing from another browser is an existing feature, however we consider a snap knowing about other snaps that are installed an information leak. This is a powerful feature of snap confinement.
I don't know much about Snaps but suppose a non-Snap Firefox build wants to import from a Chromium Snap, is that possible and how should we find the profile path?
A symlink to the current revision of the chromium snap's local data: $HOME/snap/chromium/current
Component: Release Automation: Snap → Migration
Product: Release Engineering → Firefox
QA Contact: jlorenzo
Summary: Import from the Chromium Snap profile doesn't work → Import from the Chromium Snap profile doesn't work (Firefox can't detect Chromium being installed)
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/45df0c21ab31 Import from Chromium Snap Profile r=mconley
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.