Can't do updates because of snapd crash

Bug #1782619 reported by cariboo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd (Ubuntu)
New
Undecided
Unassigned

Bug Description

I get the following output when running systemctl status snapd.apparmor.service:

snapd.apparmor.service - Load AppArmor profiles managed internally by snapd
   Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2018-07-19 10:41:49 PDT; 22s ago
  Process: 3817 ExecStart=/usr/lib/snapd/snapd-apparmor start (code=exited, status=203/EXEC)
 Main PID: 3817 (code=exited, status=203/EXEC)

Jul 19 10:41:49 skynet systemd[1]: Starting Load AppArmor profiles managed internally by snapd...
Jul 19 10:41:49 skynet systemd[3817]: snapd.apparmor.service: Failed to execute command: No such file or directory
Jul 19 10:41:49 skynet systemd[3817]: snapd.apparmor.service: Failed at step EXEC spawning /usr/lib/snapd/snapd-apparmor: No such file or
Jul 19 10:41:49 skynet systemd[1]: snapd.apparmor.service: Main process exited, code=exited, status=203/EXEC
Jul 19 10:41:49 skynet systemd[1]: snapd.apparmor.service: Failed with result 'exit-code'.
Jul 19 10:41:49 skynet systemd[1]: Failed to start Load AppArmor profiles managed internally by snapd.

This is the second time I've run into this problem on a new Ubuntu 18.10 install

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: snapd 2.34+18.10
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 19 10:40:52 2018
InstallationDate: Installed on 2018-07-12 (7 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
cariboo (cariboo) wrote :
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.