[snap] chromium-browser ignores system password store

[Russ Dill]

The new chromium 75 snap package intentionally ignores the system password store:

https://chromium.googlesource.com/chromium/src.git/+/master/docs/linux_password_storage.md

Normally, chromium auto-detects what type of password store to use, previously this has resulted in chromium connecting to the gnome password store. The new snap release passes the command line argument:

'--password-store=basic'

Which bypasses the gnome password storage.

[Russ Dill (russ-dill)]

Verified that manually starting with:

'/snap/chromium/750/usr/lib/chromium-browser/chrome --no-default-browser-check --no-first-run --ppapi-flash-path'

fixes the issue.

[Olivier Tilloy (osomon)]

Thanks for the report Russ.
Can you please share the output of the following command?

    snap connections chromium | grep password-manager-service

I suspect the password-manager-service interface is not connected, which would explain why it's using the basic, unencrypted password store. In that case you can connect it like this:

    snap connect chromium:password-manager-service

Please note that this is not a regression as far as the snap is concerned, the password-manager-service interface has never been auto-connected.

[Russ Dill (russ-dill)]

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

[Olivier Tilloy (osomon)]

So the interface is connected indeed.

What makes you say that the new snap release passes the --password-store=basic command line argument?

[Olivier Tilloy (osomon)]

@Russ, can you answer the question above?

  > What makes you say that the new snap release passes
  > the --password-store=basic command line argument?

[Launchpad Janitor (janitor)]

[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]