Closed Bug 1844279 Opened 2 years ago Closed 2 years ago

Firefox Snap can not import data from google-chrome

Categories

(Firefox Build System :: Third Party Packaging, defect)

Firefox 115
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1818237

People

(Reporter: thomasbechtold, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36

Steps to reproduce:

I want to switch from google-chrome (115.0.5790.98, installed via a .deb package) to firefox (snap)

I installed the Firefox snap (from the latest/stable channel) on Ubuntu 23.04 :

$ snap info firefox|grep installed
installed: 115.0.2-1 (2908) 256MB -

Then I started Firefox and followed https://support.mozilla.org/en-US/kb/import-data-another-browser but when I click the "Import Data" button, I get an error which says :

Firefox couldn’t find any programs that contain bookmark, history or password data.

I think that's due to the snap confinement but I wonder if the firefox snap should have access to ~/.config/google-chrome/ (that's the directory where the google-chrome data is) to be able to import data

Actual results:

The data can not be imported from google-chrome

Expected results:

the data import from google-chrome works so I can start using firefox

The Bugbug bot thinks this bug should belong to the 'Firefox Build System::Third Party Packaging' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Third Party Packaging
Product: Firefox → Firefox Build System

The severity field is not set for this bug.
:gerard-majax, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(lissyx+mozillians)
Flags: needinfo?(mstriemer)
Flags: needinfo?(mconley)
Flags: needinfo?(lissyx+mozillians)
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1818237
Flags: needinfo?(mstriemer)
Flags: needinfo?(mconley)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.