This bug was fixed in the package snapd - 2.54.3+20.04.1ubuntu0.3
---
snapd (2.54.3+20.04.1ubuntu0.3) focal; urgency=medium
* Cherry-pick https://github.com/snapcore/snapd/pull/11680 and
https://github.com/snapcore/snapd/pull/11287:
- This fixes a bad interaction between
I also tested a distribution upgrade from Focal to Jammy with the
canonical-livepatch snap installed and did not notice a 10 minute pause
during the process.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received
I followed the test case as detailed in the bug description and did not
observe a 10 minute wait during the dbus package upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969162
Title:
bad
Fwiw, I tested this also for focal->jammy on my laptop (real machien)
and it worked fine there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969162
Title:
bad interaction between snapd and
Hello Steve, or anyone else affected,
Accepted snapd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/snapd/2.54.3+20.04.1ubuntu0.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
@mrconorae: I've just checked that the upgrade is enabled:
---
$ sudo do-release-upgrade -c
Checking for a new Ubuntu release
New release '22.04 LTS' available.
Run 'do-release-upgrade' to upgrade to it.
--
You received this bug notification because you are a member of
Now that a fix has been released for both affected versions, what's left before
upgrades are enabled for 21.10→22.04?
(new to Ubuntu and Launchpad, so feel free to point out the seemingly obvious)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This bug was fixed in the package snapd - 2.54.3+21.10.1ubuntu0.3
---
snapd (2.54.3+21.10.1ubuntu0.3) impish; urgency=medium
* Cherry-pick https://github.com/snapcore/snapd/pull/11680 and
https://github.com/snapcore/snapd/pull/11287:
- This fixes a bad interaction between
This bug was fixed in the package snapd - 2.55.3+22.04ubuntu1
---
snapd (2.55.3+22.04ubuntu1) jammy; urgency=medium
* Cherry-pick https://github.com/snapcore/snapd/pull/11680
- This fixes a bad interaction between snapd and update-notifier
during a release upgrade (LP:
I ran the spread test in the snapd PR
https://github.com/snapcore/snapd/pull/11702 against this change in
21.10 and 22.04 and the restart behavior is correct: if snapd is
upgraded from a version that does not yet use "dh_systemd --restart-
after-upgrade" still keep running.
** Tags removed:
** Changed in: snapd (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969162
Title:
bad interaction between snapd and update-notifier when snapd
ah whoops-please undo
** Changed in: snapd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969162
Title:
bad interaction between snapd and
It seems the above is not an issue on 21.10 at least.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969162
Title:
bad interaction between snapd and update-notifier when snapd package
is being
There is one thing I noticed - when transitioning from
"dh_systemd_start" to "dh_systemd_start --restart-after-upgrade" at
least on 16.04 snapd.service is stopped in the old prerm but when the
new postinst runs it calls "systemctl restart snapd" but that only
restarts a service if it was not
** Description changed:
+ [Impact]
+
+ On a release upgrade from impish to jammy, dbus postinst hangs for 10
+ minutes.
+
+ [Test Case]
+
+ Testing the fix itself:
+
+ On a minimal impish system (created with autopkgtest-buildvm), install the
snapd from -proposed and run:
+ $ sudo snap
** Changed in: snapd (Ubuntu Impish)
Importance: Undecided => High
** Changed in: update-notifier (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969162
Hello Steve, or anyone else affected,
Accepted snapd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/snapd/2.54.3+21.10.1ubuntu0.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Accepting the jammy version into -proposed for a 0-day SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969162
Title:
bad interaction between snapd and update-notifier when snapd package
is
I uploaded a version of snapd with the changes from
https://github.com/snapcore/snapd/pull/11680 and
https://github.com/snapcore/snapd/pull/11287 to the my ppa:mvo/tmp for impish
too.
On a minimal impish system (created with autopkgtest-buildvm) I ran:
$ sudo apt-add-repository ppa:mvo/tmp
$
On a minimal impish system (created with autopkgtest-buildvm) I ran:
$ sudo apt install --no-install--recommends snapd update-notifier
$ sudo snap install canonical-livepatch
$ sudo apt-add-repository ppa:mvo/tmp
$ sudo sed -i 's/impish/jammy/' /etc/apt/sources.list
$ sudo sed -i 's/impish/jammy/'
On a minimal impish system (created with autopkgtest-buildvm) I ran:
$ sudo apt install --no-install--recommends snapd update-notifier
$ sudo snap install canonical-livepatch
$ sudo sed -i 's/impish/jammy/' /etc/apt/sources.list
$ sudo apt update
$ sudo apt full-upgrade -y
and with that I can
I uploaded a cherry pick of Albertos branch with the current jammy snapd
plus the fix to https://launchpad.net/~mvo/+archive/ubuntu/tmp/+packages
and will test once it's build in there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: update-notifier (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/1969162
Here's the PR: https://github.com/snapcore/snapd/pull/11680
And please forget what I wrote about our prerm script: that script is
not stopping snapd, but only all the systemd service installed *by snap
packages*, so it should be fine.
--
You received this bug notification because you are a
Hi Steve, thanks for reporting this, and for the hint on how to fix it.
We currently have a shell script in our prerm script, which manually
stops all our systemd units:
https://github.com/snapcore/snapd/blob/master/packaging/ubuntu-16.04/snapd.prerm
Do I correctly understand that your
25 matches
Mail list logo
