Error messages while updating snapd (2.59.1+23.04ubuntu1.1) over (2.59.1+23.04ubuntu1)

[Alexander Lazarević]

The update seems not to have worked properly

Unpacking snapd (2.59.1+23.04ubuntu1.1) over (2.59.1+23.04ubuntu1) ...
Setting up snapd (2.59.1+23.04ubuntu1.1) ...
snapd.failure.service is a disabled or a static unit not running, not starting it.
snapd.snap-repair.service is a disabled or a static unit not running, not starting 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 manual 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.

systemctl status snapd.mounts-pre.target
● snapd.mounts-pre.target - Mounting snaps
     Loaded: loaded (/lib/systemd/system/snapd.mounts-pre.target; static)
     Active: active since Wed 2023-05-31 06:33:46 CEST; 9min ago
      Until: Wed 2023-05-31 06:33:46 CEST; 9min ago

Notice: journal has been rotated since unit was started, output may be incomplete.

[Alexander Lazarević (e11bits)]

I tried to remove every snap unless core and reinstall it. But no snap would work any more. For example, firefox gives this when started from command line

sed: can't read /home/laza/.config/user-dirs.dirs: Permission denied
/snap/firefox/2710/snap/command-chain/desktop-launch: line 264: /home/laza/.config/user-dirs.dirs: Permission denied
cp: cannot open '/home/laza/.config/user-dirs.locale' for reading: Permission denied
/snap/firefox/2710/snap/command-chain/desktop-launch: line 269: /home/laza/.config/user-dirs.locale: Permission denied
Gtk-Message: 08:02:49.151: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.
Error: cannot open display: :0

Kind of the same with bitwarden, bw, spotify and others. They're just not working any more.

Now this might be the final straw for moving to another snapless distro ...

[Knickers Brown (metta-crawler)]

Bug reports should show how to reproduce the issue, what commands to run, etc. and that is a fact.

I don't think that any of the 'apt upgrade' output in your bug report indicates an error.

I got the same messages but all the packages are in the 'ii' or 'rc' state, see 'man dpkg' and other documentation on dpkg.

How I checked

$ dpkg -l | grep -Ev '^ii|^rc'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============================================-==========================================-============-================================================================================