When upgrading to Mantic, it fails to install snap firmware-updater

[Giuseppe Petralia]

[Impact]

While upgrading to Mantic the following message is reported:

installing snap firmware-updater
error: cannot perform the following tasks:
- Automatically connect eligible plugs and slots of snap "firmware-updater" (internal error: auto-connect of &{"firmware-updater:desktop-legacy" "snapd:desktop-legacy"} failed: snap "snapd" has no slot named "desktop-legacy")

[Test case]

Confirming the failure:

$ lxc launch ubuntu:lunar lp-2039268
Creating lp-2039268
Starting lp-2039268
$ lxc exec lp-2039268 bash
# sed -i -e's/lunar/mantic/' /etc/apt/sources.list && apt update && apt install -y systemd
# ls -l /run/systemd/generator/snap.mount
-rw-r--r-- 1 root root 274 Oct 18 05:49 /run/systemd/generator/snap.mount
# ^D
$ lxc delete --force lp-2039268

Confirming the fix:

$ lxc launch ubuntu:lunar lp-2039268
Creating lp-2039268
Starting lp-2039268
$ lxc exec lp-2039268 bash
# sed -i -e's/lunar/mantic/' /etc/apt/sources.list && apt update && apt install -y systemd
# ls -l /run/systemd/generator/snap.mount
ls: cannot access '/run/systemd/generator/snap.mount': No such file or directory
# ^D
$ lxc delete --force lp-2039268

[Where problems could occur]
This fix changes how snapd detects at boot time whether a bind remount of /snap with different mount options is necessary. In unusual circumstances where the rootfs mount options are not what we expect by default in Ubuntu, AND the systemd generator is blocked by a custom security policy from reading /proc/1/mounts, it would get the wrong answer, fail to generate the mount unit under necessary circumstances, and regress the behavior of snapd.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Brian Murray (brian-murray)]

I tested an upgrade from Ubuntu 23.04 to Ubuntu 23.10 and was able to recreate this failure. After the upgrade was completed the `firmware-updater` snap was *not* installed and trying to install it again failed. However, after rebooting the upgraded system I was able to install the `firmware-updater` snap.

[Brian Murray (brian-murray)]

I also tested an upgrade from Ubuntu 23.04 to Ubuntu 23.10 where I installed the latest version of snapd (something do-release-upgrade does not require) and rebooted the Ubuntu 23.04 system. I then ran `do-release-upgrade -d` and the `firmware-updater` snap was not installed during the upgrade process.

[Steve Langasek (vorlon)]

On my up-to-date lunar system, I was able to 'snap install firmware-updater' without issue.

I was also able to install it in a lunar lxd container.

$ lxc launch ubuntu:lunar -- lp-2039268
Creating lp-2039268
Starting lp-2039268
$ lxc exec lp-2039268 -- bash
# snap info snapd | grep installed
  Start with 'snap list' to see installed snaps.
installed: 2.60.3 (20092) 42MB snapd
# snap install firmware-updater
[...]
# snap connections|grep :desktop-legacy
desktop-legacy firmware-updater:desktop-legacy :desktop-legacy -
#

[Steve Langasek (vorlon)]

On a live system booted with the lunar ISO, I also see no failures installing firmware-updater.

snapd snap in the image is at version 2.59.1.

the plug shows as connected after install.

[Steve Langasek (vorlon)]

And on a real installed system, I executed the release upgrade via update-manager -d and was unable to reproduce this issue.

[Brian Murray (brian-murray)]

I've tried multiple ways to stop this from happening:

1) upgrading the snapd snap to version 2.60.4 before starting the upgrade
2) modifying the upgrader so that firmware-updater is installed after gtk-common-themes

Neither of those resolved the issue and in my experience the error message changes occassionally.

Below is one message I've seen:

Automatically connect eligible plugs and slots of snap "firmware-updater" (internal error: auto-connect of &{"firmware-updater:icon-themes" "gtk-common-themes:icon-themes"} failed: snap "gtk-common-themes" has no slot named "icon-themes")

Another:

- Automatically connect eligible plugs and slots of snap "firmware-updater" (internal error: auto-connect of &{"firmware-updater:gnome-42-2204" "gnome-42-2204:gnome-42-2204"} failed: snap "gnome-42-2204" has no slot named "gnome-42-2204")

Also running `snap info snapd` I noticed that snapd is broken before rebooting after the upgrade.

[Steve Langasek (vorlon)]

opening a task on snapd for this

[Steve Langasek (vorlon)]

I have managed to reproduce this in a fresh lunar VM. Applied updates with update-manager, rebooted, ran the upgrade with update-manager -d.

Rerunning 'snap install firmware-updater' from the commandline also fails, though not always with the same slot failing.

Output of 'snap changes':

ID Status Spawn Ready Summary
1 Done 2023-04-18 today at 16:54 PDT Initialize system state
2 Done today at 16:53 PDT today at 16:53 PDT Initialize device
3 Done today at 17:46 PDT today at 17:46 PDT Switch "core22" snap to channel "stable"
4 Error today at 17:46 PDT today at 17:46 PDT Install "firmware-updater" snap from "stable/ubuntu-23.10" channel
5 Done today at 17:46 PDT today at 17:46 PDT Switch "gnome-42-2204" snap to channel "stable/ubuntu-23.10"
6 Done today at 17:46 PDT today at 17:46 PDT Switch "gtk-common-themes" snap to channel "stable/ubuntu-23.10"
7 Done today at 17:46 PDT today at 17:46 PDT Switch "snap-store" snap to channel "stable/ubuntu-23.10"
8 Done today at 17:46 PDT today at 17:46 PDT Switch "snapd-desktop-integration" snap to channel "stable/ubuntu-23.10"
9 Done today at 17:46 PDT today at 17:46 PDT Switch "firefox" snap to channel "stable/ubuntu-23.10"
10 Error today at 17:51 PDT today at 17:51 PDT Install "firmware-updater" snap
11 Error today at 17:51 PDT today at 17:51 PDT Install "firmware-updater" snap

output of 'snap tasks 4':

Status Spawn Ready Summary
Done today at 17:46 PDT today at 17:46 PDT Ensure prerequisites for "firmware-updater" are available
Undone today at 17:46 PDT today at 17:46 PDT Download snap "firmware-updater" (109) from channel "stable/ubuntu-23.10"
Done today at 17:46 PDT today at 17:46 PDT Fetch and check assertions for snap "firmware-updater" (109)
Undone today at 17:46 PDT today at 17:46 PDT Mount snap "firmware-updater" (109)
Undone today at 17:46 PDT today at 17:46 PDT Copy snap "firmware-updater" data
Undone today at 17:46 PDT today at 17:46 PDT Setup snap "firmware-updater" (109) security profiles
Undone today at 17:46 PDT today at 17:46 PDT Make snap "firmware-updater" (109) available to the system
Error today at 17:46 PDT today at 17:46 PDT Automatically connect eligible plugs and slots of snap "firmware-updater"
Hold today at 17:46 PDT today at 17:46 PDT Set automatic aliases for snap "firmware-updater"
Hold today at 17:46 PDT today at 17:46 PDT Setup snap "firmware-updater" aliases
Hold today at 17:46 PDT today at 17:46 PDT Run install hook of "firmware-updater" snap if present
Hold today at 17:46 PDT today at 17:46 PDT Run default-configure hook of "firmware-updater" snap if present
Hold today at 17:46 PDT today at 17:46 PDT Start snap "firmware-updater" (109) services
Hold today at 17:46 PDT today at 17:46 PDT Run configure hook of "firmware-updater" snap if present
Hold today at 17:46 PDT today at 17:46 PDT Run health check of "firmware-updater" snap

......................................................................
Automatically connect eligible plugs and slots of snap "fi...

[Steve Langasek (vorlon)]

mount showed /dev/vda2 mounted on /snap. 'sudo umount /snap' revealed the contents of /snap/snapd/18933.

Also for reference, the desktop system I upgraded where I could not reproduce this is ancient, continuously upgraded, and apparently does not have the snapd snap installed at all?

[Steve Langasek (vorlon)]

Before the upgrade I have a normal set of mount units for mount points under /snap.

After the upgrade, I get an additional 'snap.mount' unit that shows up and mounts on /snap.

# Ensure that snap mount directory is mounted "shared" so snaps can be refreshed correctly (LP: #1668759).
[Unit]
Description=Ensure that the snap directory shares mount events.
[Mount]
What=/snap
Where=/snap
Type=none
Options=bind,shared
[Install]
WantedBy=local-fs.target

[Steve Langasek (vorlon)]

The bug number in the comment appears to be incorrect.

[Steve Langasek (vorlon)]

This comes from the snapd mount generator.

The code to generate this mount unit is not new, it dates back to snapd 2.31.2.

But that unit was not there at boot.

Its generation gets triggered as part of the ubuntu-release-upgrade after the apt upgrade has finished, as part of the Quirks.manticPostUpgrade based on the timing in the log vs the timestamp of the mount unit file.

It does happen after the logging line 'DEBUG switch of snap core22 succeeded' (I guess because before upgrade it was incorrectly following the ubuntu-23.04 channel but should be following stable?)

I have confirmed that on a lunar system with snapd 2.59.1+23.04ubuntu1.1, the snap.mount does not exist and /snap is not bind-mounted.

The code of the generator says it's not supposed to be needed as a workaround if the root filesystem is already mounted as shared:, which is the case at the start of the upgrade.

[Steve Langasek (vorlon)]

After upgrade, the / line in /proc/self/mountinfo still shows:

28 1 252:2 / / rw,relatime shared:1 - ext4 /dev/vda2 rw

so I don't know why this mount unit winds up being output.

[Steve Langasek (vorlon)]

This is sufficient to reproduce the issue on a lunar desktop:

sudo sed -i -e's/lunar/mantic/' /etc/apt/sources.list && sudo apt update && sudo apt install systemd

[Steve Langasek (vorlon)]

$ lxc launch ubuntu:lunar lp-2039268
Creating lp-2039268
Starting lp-2039268
$ lxc exec lp-2039268 bash
# sed -i -e's/lunar/mantic/' /etc/apt/sources.list && apt update && apt install systemd
# ls -l /run/systemd/generator/snap.mount
-rw-r--r-- 1 root root 274 Oct 18 05:49 /run/systemd/generator/snap.mount
#

in a container the mount unit appears not to actually activate, but this is enough to reproduce the generation of the unit.

[Steve Langasek (vorlon)]

moving the generator aside and replacing it with the following script:

cd /lib/systemd
mv system-generators/snapd-generator .
cat > system-generators/snapd-generator <<EOF
#!/bin/sh

exec > /tmp/lp.2039268 2>&1
cat /proc/self/mountinfo

exec strace -ff -s256 -o /tmp/trace-2039268 /lib/systemd/snapd-generator "\$@"
EOF
chmod a+x system-generators/snapd-generator

It looks like this unit isn't actually generated by the snapd generator in the snapd deb, but maybe by the copy in the snapd snap? which could explain why /proc/self/mountinfo is different, but I don't understand how or why this would be executed.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Miguel Pires (miguelpires1)]

I believe this has been fixed with this PR https://github.com/snapcore/snapd/pull/13129 which is in 2.61 (currently in beta) . I've tested the snapd-generator containing the fix and it makes the issue not reproduce anymore.

[Samuele Pedroni (pedronis)]

> It looks like this unit isn't actually generated by the snapd generator in the snapd deb, but maybe by the copy in the snapd snap? which could explain why /proc/self/mountinfo is different, but I don't understand how or why this would be executed.

I'm confused by this part of the report, as I said elsewhere I don't know of a mechanism that would involve on classic the generator in the snap.

Indeed if I try bluntly to remove the one outside and leave only the buggy one from the snap in reproducer I don't get the unit:

$ lxc launch ubuntu:lunar lp-2039268
Creating lp-2039268
Starting lp-2039268
$ lxc exec lp-2039268 bash
root@lp-2039268:~# rm /usr/lib/systemd/system-generators/snapd-generator
root@lp-2039268:~# find / -name "snapd-generator"
... errors
/snap/snapd/20092/lib/systemd/system-generators/snapd-generator
... errors

root@lp-2039268:~# snap version
snap 2.60.3
snapd 2.60.3
series 16
ubuntu 23.04
kernel 6.2.0-35-generic
root@lp-2039268:~# sed -i -e's/lunar/mantic/' /etc/apt/sources.list && apt update && apt install systemd
...
root@lp-2039268:~# ls /usr/lib/systemd/system-generators/snapd*
ls: cannot access '/usr/lib/systemd/system-generators/snapd*': No such file or directory
root@lp-2039268:~# ls -l /run/systemd/generator/snap.mount
ls: cannot access '/run/systemd/generator/snap.mount': No such file or directory

the snap.mount was not created

Also to clarify another aspect many things in snapd support reexec from the deb into the snap, but the generator is not one of them as can be seen inspecting its code

[Benjamin Drung (bdrung)]

The bug number referenced in the snap.mount was changed by this rewording commit: https://github.com/snapcore/snapd/commit/0782a466d87449064b4ce69fd04f71f1b5c4b395 - so the referenced bug should be bug #1668659 instead.

[Benjamin Drung (bdrung)]

The lxc container has / mounted shared:

$ lxc launch ubuntu:lunar lp-2039268
$ lxc exec lp-2039268 bash
root@lp-2039268:~# findmnt -o TARGET,PROPAGATION /
TARGET PROPAGATION
/ shared,slave

So /run/systemd/generator/snap.mount should not be generated.

[Benjamin Drung (bdrung)]

Excluded any snap as culprit by removing all snaps before the upgrade:

$ lxc launch ubuntu:lunar lp-2039268
$ lxc exec lp-2039268 bash
root@lp-2039268:~# snap remove lxd && snap remove core22 && snap remove snapd
root@lp-2039268:~# sed -i -e's/lunar/mantic/' /etc/apt/sources.list && apt update && apt install -y systemd
root@lp-2039268:~# ls -l /run/systemd/generator/snap.mount
-rw-r--r-- 1 root root 274 Oct 26 11:29 /run/systemd/generator/snap.mount
root@lp-2039268:~# snap list
No snaps are installed yet. Try 'snap install hello-world'.

Replacing the snapd-generator as mentioned in comment #17 and adding `ls -l /run/systemd/generator/snap.mount` to the ends of the replacement script shows that /run/systemd/generator/snap.mount is not present at that point of time. Something later creates this file.

[Samuele Pedroni (pedronis)]

I built a deb locally with https://github.com/snapcore/snapd/pull/13335 which contains a cherry-pick of the fix on top of 2.60.4, and I could *not* reproduce the issue!

even with a snapd snap installed with a generator with the bug (which afaik should not matter)

$ lxc launch ubuntu:lunar lp-2039268
$ lxc file push snapd_2.60.4fix1_amd64.deb lp-2039268/root/
$ lxc exec lp-2039268 bash
root@lp-2039268:~# snap version
snap 2.60.3
snapd 2.60.3
series 16
ubuntu 23.04
kernel 6.2.0-35-generic
root@lp-2039268:~# dpkg -i snapd_2.60.4fix1_amd64.deb
...
root@lp-2039268:~# ls -l /run/systemd/generator/snap.mount
ls: cannot access '/run/systemd/generator/snap.mount': No such file or directory
root@lp-2039268:~# sed -i -e's/lunar/mantic/' /etc/apt/sources.list && apt update && apt install systemd

...
root@lp-2039268:~# ls -l /run/systemd/generator/snap.mount
ls: cannot access '/run/systemd/generator/snap.mount': No such file or directory

[Benjamin Drung (bdrung)]

Successfully verified with the attached patch:

$ lxc launch ubuntu:lunar lp-2039268
$ lxc file push snapd_2.60.2+23.04.1_amd64.deb lp-2039268/root/
$ lxc exec lp-2039268 bash
root@lp-2039268:~# apt install ./snapd_2.60.2+23.04.1_amd64.deb
root@lp-2039268:~# ls -l /run/systemd/generator/snap.mount
ls: cannot access '/run/systemd/generator/snap.mount': No such file or directory
root@lp-2039268:~# sed -i -e's/lunar/mantic/' /etc/apt/sources.list && apt update && apt install -y systemd
root@lp-2039268:~# ls -l /run/systemd/generator/snap.mount
ls: cannot access '/run/systemd/generator/snap.mount': No such file or directory

[Michael Hudson-Doyle (mwhudson)]

Oh so this is probably fallout from https://github.com/systemd/systemd/commit/ca6ce62d2a437432082b5c6e5d4275d56055510f ("manager: execute generators in a mount namespace "sandbox"") then? Slightly surprised it only causes issues on upgrades though...

[Steve Langasek (vorlon)]

It occurs to me belatedly that the reason we're not seeing evidence of the generator creating this unit in the debug output is because the debug output itself is happening in a different mount namespace and therefore we're failing to capture it in the expected /tmp directory....

So if we're empirically seeing that this patch fixes it, we should be good to cherry pick this.

[Steve Langasek (vorlon)]

An upload of snapd to lunar-proposed has been rejected from the upload queue for the following reason: "diff cruft".

[Brian Murray (brian-murray)]

Hello Giuseppe, or anyone else affected,

Accepted snapd into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/snapd/2.60.4+23.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Brian Murray (brian-murray)]

Hello Giuseppe, or anyone else affected,

Accepted snapd into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/snapd/2.59.1+23.04ubuntu1.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Steve Langasek (vorlon)]

$ lxc launch ubuntu:lunar lp-2039268
Creating lp-2039268
Starting lp-2039268
$ lxc exec lp-2039268 bash
root@lp-2039268:~# echo -e 'deb http://archive.ubuntu.com/ubuntu lunar-proposed main' >> /etc/apt/sources.list
root@lp-2039268:~# apt update
[...]
root@lp-2039268:~# apt install snapd/lunar-proposed
[...]
root@lp-2039268:~# sed -i -e's/lunar/mantic/' /etc/apt/sources.list && apt update && apt install -y systemd
[...]
root@lp-2039268:~# ls -l /run/systemd/generator/snap.mount
ls: cannot access '/run/systemd/generator/snap.mount': No such file or directory
root@lp-2039268:~#

Confirmed for lunar.

[Steve Langasek (vorlon)]

Mantic, slightly different test case to install snapd from mantic-proposed onto lunar before installing snapd:

$ lxc launch ubuntu:lunar lp-2039268
Creating lp-2039268
Starting lp-2039268
$ lxc exec lp-2039268 bash
root@lp-2039268:~# echo -e 'deb http://archive.ubuntu.com/ubuntu lunar-proposed main' >> /etc/apt/sources.list
root@lp-2039268:~# sed -i -e's/lunar/mantic/' /etc/apt/sources.list
root@lp-2039268:~# apt update
[...]
root@lp-2039268:~# apt install -y snapd/mantic-proposed
[...]
root@lp-2039268:~# apt install -y systemd
[...]
root@lp-2039268:~# ls -l /run/systemd/generator/snap.mount
ls: cannot access '/run/systemd/generator/snap.mount': No such file or directory
root@lp-2039268:~#

Confirmed for mantic.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted snapd (2.59.1+23.04ubuntu1.2) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/252.5-2ubuntu3.2 (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/lunar/update_excuses.html#snapd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Brian Murray (brian-murray)]

I've queued a test with snapd 2.59.1+23.04ubuntu1.1 and systemd as that was never tested to determine if the test failure was a regrsession in the security update of snapd.

[Brian Murray (brian-murray)]

I tested an upgrade from Lunar w/ the version of snapd from -proposed installed and upgraded to Mantic and the firmware-updater snap was not installed after upgrade. I reported bug 2041697 which has new log files.

[Nick Rosbrook (enr0n)]

I ran an upgrade from lunar to mantic where I had snapd from lunar-proposed installed before the upgrade, and left mantic-proposed enabled so that snapd from mantic-proposed would be installed during the upgrade. In that test, firmware-updater was successfully installed.

nr@clean-lunar-amd64:~$ do-release-upgrade -d
Checking for a new Ubuntu release

= Welcome to Ubuntu 23.10 'Mantic Minotaur' =

The Ubuntu team is proud to announce Ubuntu 23.10 'Mantic Minotaur'.

To see what's new in this release, visit:
  https://wiki.ubuntu.com/ManticMinotaur/ReleaseNotes

Ubuntu is a Linux distribution for your desktop or server, with a fast
and easy install, regular releases, a tight selection of excellent
applications installed by default, and almost any other software you
can imagine available through the network.

We hope you enjoy Ubuntu.

== Feedback and Helping ==

If you would like to help shape Ubuntu, take a look at the list of
ways you can participate at

  http://www.ubuntu.com/community/participate/

Your comments, bug reports, patches and suggestions will help ensure
that our next release is the best release of Ubuntu ever. If you feel
that you have found a bug please read:

  http://help.ubuntu.com/community/ReportingBugs

Then report bugs using apport in Ubuntu. For example:

  ubuntu-bug linux

will open a bug report in Launchpad regarding the linux package.

If you have a question, or if you think you may have found a bug but
aren't sure, first try asking on the #ubuntu or #ubuntu-bugs IRC
channels on Libera.Chat, on the Ubuntu Users mailing list, or on the
Ubuntu forums:

  http://help.ubuntu.com/community/InternetRelayChat
  http://lists.ubuntu.com/mailman/listinfo/ubuntu-users
  http://www.ubuntuforums.org/

== More Information ==

You can find out more about Ubuntu on our website, IRC channel and wiki.
If you're new to Ubuntu, please visit:

  http://www.ubuntu.com/

To sign up for future Ubuntu announcements, please subscribe to Ubuntu's
very low volume announcement list at:

  http://lists.ubuntu.com/mailman/listinfo/ubuntu-announce

Continue [yN] y
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,271 kB]
Fetched 1,272 kB in 0s (0 B/s)
authenticate 'mantic.tar.gz' against 'mantic.tar.gz.gpg'
extracting 'mantic.tar.gz'
[sudo] password for nr:

Sorry, try again.
[sudo] password for nr:

Sorry, try again.
[sudo] password for nr:

sudo: 3 incorrect password attempts
nr@clean-lunar-amd64:~$
nr@clean-lunar-amd64:~$ cd /tmp/ubuntu-release-upgrader-8clgr67q/
nr@clean-lunar-amd64:/tmp/ubuntu-release-upgrader-8clgr67q$ sudo su
[sudo] password for nr:
root@clean-lunar-amd64:/tmp/ubuntu-release-upgrader-8clgr67q# cat <<EOF >/etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe
EOF
root@clean-lunar-amd64:/tmp/ubuntu-release-upgrader-8clgr67q# cat <<EOF >/etc/apt/preferences.d/proposed-updates
Package: *
Pin: release a=$(lsb_release -cs)-pr...

[Launchpad Janitor (janitor)]

This bug was fixed in the package snapd - 2.60.4+23.10.1

---------------
snapd (2.60.4+23.10.1) mantic; urgency=medium

  [ Valentin David ]
  * cmd/snapd-generator: read mountinfo for pid 1 (LP: #2039268)

 -- Steve Langasek <email address hidden> Thu, 26 Oct 2023 13:25:44 -0700

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for snapd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package snapd - 2.59.1+23.04ubuntu1.2

---------------
snapd (2.59.1+23.04ubuntu1.2) lunar; urgency=medium

  [ Valentin David ]
  * cmd/snapd-generator: read mountinfo for pid 1 (LP: #2039268)

 -- Steve Langasek <email address hidden> Thu, 26 Oct 2023 13:03:02 -0700

[Nick Rosbrook (enr0n)]

Since snapd has been released to {lunar,mantic}-updates, I tested an upgrade from lunar to mantic without any modifications, and all went well:

nr@clean-lunar-amd64:~$ sudo apt update && sudo apt install snapd -y
[sudo] password for nr:
Get:1 http://security.ubuntu.com/ubuntu lunar-security InRelease [109 kB]
Hit:2 http://archive.ubuntu.com/ubuntu lunar InRelease
Get:3 http://archive.ubuntu.com/ubuntu lunar-updates InRelease [109 kB]
Get:4 http://security.ubuntu.com/ubuntu lunar-security/main amd64 DEP-11 Metadata [7,412 B]
Get:5 http://security.ubuntu.com/ubuntu lunar-security/universe amd64 DEP-11 Metadata [32.0 kB]
Get:6 http://archive.ubuntu.com/ubuntu lunar-updates/main Sources [155 kB]
Get:7 http://archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages [503 kB]
Get:8 http://archive.ubuntu.com/ubuntu lunar-updates/main amd64 DEP-11 Metadata [81.1 kB]
Get:9 http://archive.ubuntu.com/ubuntu lunar-updates/universe i386 Packages [674 kB]
Get:10 http://archive.ubuntu.com/ubuntu lunar-updates/universe amd64 Packages [814 kB]
Get:11 http://archive.ubuntu.com/ubuntu lunar-updates/universe amd64 DEP-11 Metadata [71.5 kB]
Fetched 2,555 kB in 2s (1,477 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-6.2.0-26 linux-headers-6.2.0-26-generic
  linux-image-5.19.0-46-generic linux-image-6.2.0-26-generic
  linux-modules-5.19.0-46-generic linux-modules-6.2.0-26-generic
  linux-modules-extra-5.19.0-46-generic linux-modules-extra-6.2.0-26-generic
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
  snapd
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 26.2 MB of archives.
After this operation, 4,096 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu lunar-updates/main amd64 snapd amd64 2.59.1+23.04ubuntu1.2 [26.2 MB]
Fetched 26.2 MB in 2s (14.5 MB/s)
(Reading database ... 248469 files and directories currently installed.)
Preparing to unpack .../snapd_2.59.1+23.04ubuntu1.2_amd64.deb ...
Unpacking snapd (2.59.1+23.04ubuntu1.2) over (2.59.1+23.04ubuntu1.1) ...
Setting up snapd (2.59.1+23.04ubuntu1.2) ...
snapd.failure.service is a disabled or a static unit not running, not starting i
t.
snapd.snap-repair.service is a disabled or a static unit not running, not starti
ng it.
Failed to restart snapd.mounts-pre.target: Operation refused, unit snapd.mounts-
pre.target may be requested by dependency only (it is configured to refuse manua
l start/stop).
See system logs and 'systemctl status snapd.mounts-pre.target' for details.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for dbus (1.14.4-1ubuntu1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Pro...

[Brian Murray (brian-murray)]

I tested an upgrade from Mantic to Noble today and the firmware-updater snap was updated so I'm setting this to Fix Released.