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.)
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.)