[snap] chromium won't start after logging in to google account
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Fix Released
|
High
|
Olivier Tilloy |
Bug Description
(issue initially reported on the forum: https:/
$ snap info core chromium | egrep "name|installed"
name: core
installed: 16-2.32.3 (4407) 90MB core
name: chromium
installed: 65.0.3325.181 (274) 144MB -
Steps to reproduce:
1) Install the chromium snap: snap install chromium
2) Launch it: /snap/bin/chromium
3) Click the account button on the right side of the tabs bar, and log into a google account
4) Close the browser window
5) Launch chromium again
Expected result: chromium launches, a window is shown and the user is logged into their google account
Current result: the executable seemingly hangs, no window is shown
Changed in chromium-browser (Ubuntu): | |
status: | Confirmed → In Progress |
The following verbose log suggests that libsecret is missing from the snap:
[8021:8236: 0413/194753. 217679: VERBOSE1: key_storage_ util_linux. cc(53)] Password storage detected desktop environment: GNOME 0413/194753. 218064: VERBOSE1: libsecret_ util_linux. cc(101) ] Could not load libsecret-1.so.0: libsecret-1.so.0: cannot open shared object file: No such file or directory
[8021:8236:
I tested rebuilding the snap with libsecret-1-0 in the stage packages, and the message went away but still no window. manager- service interface, the issue seemed to be resolved:
However after connecting the password-
snap connect chromium: password- manager- service