[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2021-02-17 Thread Timo Jyrinki
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

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-12-09 Thread Olivier Tilloy
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. -- You received this bug notification because

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-12-09 Thread TomaszChmielewski
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

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-12-09 Thread TomaszChmielewski
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

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-11-19 Thread Olivier Tilloy
Darko, what is the output of "snap connections chromium | grep password" ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849160 Title: after deb->snap transition, chromium no longer sees local

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-11-19 Thread Darko Veberic
the same behavior on ubuntu 19.04 with snap chromium 78.0.3904.97 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849160 Title: after deb->snap transition, chromium no longer sees local password

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-11-08 Thread Olivier Tilloy
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! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-11-07 Thread Giovanni Pelosi
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

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-11-04 Thread Launchpad Bug Tracker
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

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-10-28 Thread Olivier Tilloy
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

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-10-28 Thread Łukasz Zemczak
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

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-10-22 Thread Launchpad Bug Tracker
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

Re: [Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-10-22 Thread Steve Langasek
On Tue, Oct 22, 2019 at 01:50:07PM -, 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

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-10-22 Thread Olivier Tilloy
** Description changed: + [Impact] + After upgrading to eoan and accepting the deb->snap transition for chromium, the passwords saved in my browser are no longer available to the app, despite ~/snap/chromium/current/.config/chromium/Default/Login - Data being present and fully-populated.

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-10-22 Thread Launchpad Bug Tracker
** Branch linked: lp:~chromium-team/chromium-browser/eoan-stable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849160 Title: after deb->snap transition, chromium no longer sees local password

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-10-22 Thread Olivier Tilloy
Fixed with https://bazaar.launchpad.net/~chromium-team/chromium-browser /eoan-stable/revision/1522. ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Committed -- You received

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-10-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849160

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-10-22 Thread Olivier Tilloy
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) -- You

Re: [Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-10-21 Thread Steve Langasek
On Mon, Oct 21, 2019 at 07:57:19PM -, 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

[Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store

2019-10-21 Thread Olivier Tilloy
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