Fix: https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-
stable/revision/1514
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Committed
** Summary changed:
- [deb2snap] Upgrade fails when snap is already installed
+ [snap] failure to connect
** 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/1838821
Title:
[snap] failure to connect password-manager-service during package
Although I'm still unable to reproduce the problem, this bug was
reported independently (duplicate bug #1839720).
Failing to connect the password-manager-service shouldn't make the
package installation fail, as the application should still work (if the
core snap itself isn't broken, but that
** Tags added: snap
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838821
Title:
[deb2snap] Upgrade fails when snap is already installed
To manage notifications about this bug
I cannot reproduce this error when testing the upgrade scenario in a
clean eoan VM where the snap was already installed (tested both with the
password-manager-service interface previously connected, and not).
That snapd error looks suspicious, it's as if the core snap wasn't
available on your
