after deb->snap transition, chromium no longer sees local password store

Can you check whether the password-manager-service interface is connected?

    snap connections chromium | grep password

I suspect it's not. This can be fixed by running "snap connect chromium:password-manager-service".

There appears to be a wrong assumption in the preinst script for chromium-browser that decides whether to request the connection.

On Mon, Oct 21, 2019 at 07:57:19PM -0000, Olivier Tilloy wrote:
> Can you check whether the password-manager-service interface is
> connected?

> snap connections chromium | grep password

Output is:

$ snap connections chromium | grep password
password-manager-service chromium:password-manager-service - -
$

So I think that means it is connected?

No, it's not connected. There have been similar reports, and I think I understand what's going on.
I will SRU a fix to the chromium-browser package. In the meantime, I suggest you run:

    snap connect chromium:password-manager-service

(please confirm whether this fixes the problem)

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

Fixed with https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-stable/revision/1522.

On Tue, Oct 22, 2019 at 01:50:07PM -0000, Olivier Tilloy wrote:
> No, it's not connected. There have been similar reports, and I think I understand what's going on.
> I will SRU a fix to the chromium-browser package. In the meantime, I suggest you run:

> snap connect chromium:password-manager-service

> (please confirm whether this fixes the problem)

Ok, sure enough, running this command and restarting fixes the problem.
Thanks!

(Sorry, I tried to run this command before, but there seemed to be a
whitespace issue in your comment #1 and it gave me an error instead.)

This bug was fixed in the package chromium-browser - 77.0.3865.120-0ubuntu2

---------------
chromium-browser (77.0.3865.120-0ubuntu2) focal; urgency=medium

  * debian/chromium-browser.preinst: revert a previous change which was causing
    upgrades from disco to eoan to install the snap but not connect the
    password-manager-service interface (LP: #1849160)
  * debian/control: update Vcs-Bzr URL to point to the branch for 20.04
    (codename the Focal Fossa)

 -- Olivier Tilloy <email address hidden> Tue, 22 Oct 2019 16:20:34 +0200

Hello Steve, or anyone else affected,

Accepted chromium-browser into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/chromium-browser/77.0.3865.120-0ubuntu1.19.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Tested and validated in a disco VM which had chromium-browser installed (but not the chromium snap). I dist-upgraded to eoan, and chromium-browser was upgraded to 77.0.3865.120-0ubuntu1~snap1. I verified that the chromium snap was correctly installed, but the password-manager-service wasn't connected. I then enabled eoan-proposed, updated chromium-browser to 77.0.3865.120-0ubuntu1.19.10.1, and verified that the password-manager-service was connected.

This bug was fixed in the package chromium-browser - 77.0.3865.120-0ubuntu1.19.10.1

---------------
chromium-browser (77.0.3865.120-0ubuntu1.19.10.1) eoan; urgency=medium

  * debian/chromium-browser.preinst: revert a previous change which was causing
    upgrades from disco to eoan to install the snap but not connect the
    password-manager-service interface (LP: #1849160)

 -- Olivier Tilloy <email address hidden> Tue, 22 Oct 2019 16:23:55 +0200

The verification of the Stable Release Update for chromium-browser has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Alter Ubuntu 19.04 => 19.10 upgrade

Chromium passwords are still not working

- password not imported
- password not synced with other systems
- password not saved

I've tried:

---

snap connect chromium:password-manager-service

the command:

snap connections chromium | grep password

returns

password-manager-service chromium:password-manager-service :password-manager-service manual

---

~ snap list chromium
Name Version Rev Tracking Publisher Notes
chromium 78.0.3904.70 920 stable canonical✓ -

~ apt policy chromium-browser
chromium-browser:
  Installed: 77.0.3865.120-0ubuntu1.19.10.1
  Candidate: 77.0.3865.120-0ubuntu1.19.10.1
  Version table:
 *** 77.0.3865.120-0ubuntu1.19.10.1 500
        500 http://it.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 Packages
        100 /var/lib/dpkg/status
     77.0.3865.120-0ubuntu1~snap1 500
        500 http://it.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages

---

reimporting old config

mv ~/snap/chromium/current/.config ~/snap/chromium/current/.config.000

chromium-browser

Importing existing chromium profile from /home/xxx/.config/chromium (version 76.0.3809.100)
Import done in 12.293 s

what i see here:

[8384:8766:1107/113136.480119:ERROR:token_service_table.cc(140)] Failed to decrypt token for service AccountId-101040866152128307883
[8384:8766:1107/113136.480171:ERROR:token_service_table.cc(140)] Failed to decrypt token for service AccountId-111604898276580333411
[8384:8766:1107/113136.480196:ERROR:token_service_table.cc(140)] Failed to decrypt token for service AccountId-117219250637178212384
[8384:8766:1107/113136.480221:ERROR:token_service_table.cc(140)] Failed to decrypt token for service AccountId-116924599772170384880
[8384:8766:1107/113136.480242:ERROR:token_service_table.cc(140)] Failed to decrypt token for service AccountId-106555677384077017077
[8384:8384:1107/113137.484604:ERROR:account_tracker.cc(241)] AccessTokenFetched error: Invalid credentials (credentials missing).
[8384:8384:1107/113137.484926:ERROR:account_info_fetcher.cc(60)] OnGetTokenFailure: Invalid credentials (credentials missing).
[8384:8384:1107/113139.303513:ERROR:data_type_manager_impl.cc(38)] Passwords cryptographer error was encountered:
...
[8384:8697:1107/113149.949701:ERROR:gcm_store_impl.cc(936)] Failed to restore security token.
...
[8384:8995:1107/113313.221960:ERROR:database.cc(1581)] Passwords sqlite error 2067, errno 0: UNIQUE constraint failed: logins.origin_url, logins.username_element, logins.username_value, logins.password_element, logins.signon_realm, sql: INSERT INTO logins (origin_url, action_url, username_element, username_value, password_element, password_value, submit_element, signon_realm, preferred, date_created, blacklisted_by_user, scheme, password_type, times_used, form_data, date_synced, display_name, icon_url, federation_url, skip_zero_click, generation_upload_status, possible_username_pairs, id, date_last_used) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
[8384:8384:1107/113315.265525:ERROR:gaia_auth_fetcher.cc(76)] Missing ID token on refresh token fetch response.
[8384:8770:1107/113315.689058:ERROR:password_syncable_s...

Giovanni, this looks like a different issue (corrupted passwords database maybe?).
Would you mind filing a new bug with this information, using `ubuntu-bug chromium-browser` ?

Thanks!

the same behavior on ubuntu 19.04 with snap chromium 78.0.3904.97

Darko, what is the output of "snap connections chromium | grep password" ?

I'm normally using Kubuntu (Plasma session) and had this problem. I've run "snap connect chromium:password-manager-service" and it helped.

However, if I log out, and choose the default Ubuntu (Gnome session) and try to use Chromium, it's again without passwords, and re-running "snap connect chromium:password-manager-service" does not help.

Please advise how to get the lost passwords back in that case.

# apt policy chromium-browser
chromium-browser:
  Installed: 77.0.3865.120-0ubuntu1.19.10.1
  Candidate: 77.0.3865.120-0ubuntu1.19.10.1
  Version table:
 *** 77.0.3865.120-0ubuntu1.19.10.1 500
        500 http://jp.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 Packages
        100 /var/lib/dpkg/status
     77.0.3865.120-0ubuntu1~snap1 500
        500 http://jp.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages

# snap connections chromium | grep password
password-manager-service chromium:password-manager-service :password-manager-service manual

Chromium uses different backends to store passwords based on the desktop environment, so passwords stored under a KDE session won't be visible under a GNOME session, and vice-versa. That's an upstream shortcoming though, nothing specific to the snap.

Just noting here that:

snap connect chromium:password-manager-service

Is still a valid way to fix this issue if you someone still bumps into it. I had this now on openSUSE Tumbleweed (using GNOME) where I installed the Chromium snap after some months of having it uninstalled. I'm not sure if it always had the problem since I use Firefox 99% of the time, but now I noticed it was not saving my password when I asked it to, and googled this bug report up.

Before doing the fix snap connections chromium had the "- -" ending line, after doing that the whole line is "password-manager-service chromium:password-manager-service :password-manager-service manual"