Upgrade to snapd_2.63+24.04_amd64.deb fails on snap-update-ns.dpkg-new

Bug #2073215 reported by localhost
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
snapd (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

release: Ubuntu 24.04 LTS
apt-cache policy snapd
snapd:
  Installed: 2.62+24.04build1
  Candidate: 2.63+24.04
  Version table:
     2.63+24.04 500
        500 http://nl.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
 *** 2.62+24.04build1 500
        500 http://nl.archive.ubuntu.com/ubuntu noble/main amd64 Packages
        100 /var/lib/dpkg/status

The upgrade to snapd_2.63+24.04_amd64.deb fails with the following error:

Preparing to unpack .../snapd_2.63+24.04_amd64.deb ...
Unpacking snapd (2.63+24.04) over (2.62+24.04build1) ...
dpkg: error processing archive /var/cache/apt/archives/snapd_2.63+24.04_amd64.deb (--unpack):
 error setting timestamps of '/usr/lib/snapd/snap-update-ns.dpkg-new': No such file or directory
No apport report written because the error message indicates an issue on the local system
                                                                                         dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
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 148.
Errors were encountered while processing:
 /var/cache/apt/archives/snapd_2.63+24.04_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in snapd (Ubuntu):
status: New → Confirmed
Revision history for this message
localhost (localhost-gmail) wrote (last edit ):

On my machine, company device, I have ESET Protect running. I think that is actually the cause of the issue. So I think it is safe to mark this report as invalid. As fas as I can see, I don't have the rights to do so.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.