Ubuntu
apparmor package

package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1

  1. Focal (20.04)
  2. Bug #2032851
Bug #2032851 reported by Ravi
142
This bug affects 28 people
Affects Status Importance Assigned to Milestone
apparmor (Ubuntu)
Fix Released
Critical
Georgia Garcia
Focal
In Progress
Critical
Georgia Garcia

Bug Description

[ Impact ]

 * During an apparmor package upgrade, the cache files were
   deleted, but there could also be directories under
   /etc/apparmor.d/cache/ which the pre installation scripts did
   not account for. The upgrade would then fail with the
   following error message because it would not be able to remove
   the directories:

 package:apparmor:2.12-4ubuntu5.3
 Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ...
 rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory
 dpkg: error processing archive /tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack):
  new apparmor package pre-installation script subprocess returned error exit status 1
ErrorMessage: new apparmor package pre-installation script subprocess returned error exit status 1

[ Test Plan ]

 * On a bionic machine, create a directory under
/etc/apparmor.d/cache

sudo mkdir /etc/apparmor.d/cache/test

 * To simulate a system upgrade to focal, you can run the following steps

1. Add the focal archive

sudo bash -c "cat <<EOF >/etc/apt/sources.list.d/apparmor-focal.list
deb http://archive.ubuntu.com/ubuntu/ focal restricted main multiverse universe
EOF"

2. Set up preferences so not all packages are upgraded from focal

sudo bash -c "cat <<EOF >/etc/apt/preferences.d/apparmor-focal
Package: *
Pin: release a=focal
Pin-Priority: 400
EOF"

3. Install only apparmor from focal

sudo apt-get install apparmor/focal

4. Notice that the error occurs:

The following packages will be upgraded:
  apparmor
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/494 kB of archives.
After this operation, 99.3 kB of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 220084 files and directories currently installed.)
Preparing to unpack .../apparmor_2.13.3-7ubuntu5_amd64.deb ...
rm: cannot remove '/etc/apparmor.d/cache/test': Is a directory
dpkg: error processing archive /var/cache/apt/archives/apparmor_2.13.3-7ubuntu5_amd64.deb (--unpack):
 new apparmor package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/apparmor_2.13.3-7ubuntu5_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[ Where problems could occur ]

 * Since the cache files are being removed, they will have to be
   recreated next time apparmor runs.

-----------------------------------------------------
Original bug description
-----------------------------------------------------

package install error

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: apparmor 2.12-4ubuntu5.3
ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18
Uname: Linux 4.15.0-213-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Aug 24 02:35:35 2023
DuplicateSignature:
 package:apparmor:2.12-4ubuntu5.3
 Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ...
 rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory
 dpkg: error processing archive /tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack):
  new apparmor package pre-installation script subprocess returned error exit status 1
ErrorMessage: new apparmor package pre-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-08-22 (1 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic root=UUID=c5495aa8-cf2c-4042-a2ea-4533e9343808 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt 2.0.9
SourcePackage: apparmor
Syslog:
 Aug 24 02:04:25 adminn-Lenovo-V110-15ISK dbus-daemon[4678]: [session uid=1000 pid=4678] AppArmor D-Bus mediation is enabled
 Aug 24 02:05:26 adminn-Lenovo-V110-15ISK dbus-daemon[856]: [system] AppArmor D-Bus mediation is enabled
 Aug 24 02:05:31 adminn-Lenovo-V110-15ISK dbus-daemon[1021]: [session uid=124 pid=1021] AppArmor D-Bus mediation is enabled
 Aug 24 02:06:04 adminn-Lenovo-V110-15ISK dbus-daemon[1506]: [session uid=1000 pid=1506] AppArmor D-Bus mediation is enabled
 Aug 24 03:39:11 adminn-Lenovo-V110-15ISK dbus-daemon[9963]: [session uid=0 pid=9956] AppArmor D-Bus mediation is enabled
Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

See original description
Revision history for this message
Ravi (zeno1209) wrote :
Leonidas S. Barbosa (leosilvab)
information type: Private Security → Public
Apport retracing service (apport)
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in apparmor (Ubuntu):
status: New → Confirmed
Revision history for this message
Trevor Dearham (fydon) wrote (last edit ):

This occurs when updating from Ubuntu 18.04 to 20.04. I have a few instances that I'm trying to update to Ubuntu 22.04, but this issue is preventing them from updating. I was able to perform the update a few times earlier this week and over the past few weeks. I successfully performed test updates on multiple clones and then successfully on the actual instances prior to this week.

Revision history for this message
G (gkzf) wrote (last edit ):

Had this when updating from ubuntu (with unity) 18.4 to 20.04 Yesterday (27 Aug)

Possible Work around?
Moved bf9d6da9.0 to desktop (Moved, just in case was not a solution as had tried re-namaing, with no effect)
sudo apt-get install -f, then ran ok.

afterwards noted that etc/../cache/ & desktop/bf9d6da9.0 no longer present on the system

NB - to do this had to use back version of Ubuntu, as new version did not load.

Revision history for this message
Trevor Dearham (fydon) wrote (last edit ):

I'm not sure if G is saying something similar above, but I found that deleting all the subfolders in cache when still on Ubuntu 18.04 allows for do-release-upgrade to complete successfully:

sudo find /etc/apparmor.d/cache/* -type d -exec rm -r {} \;

There were other files in the cache folder, but I assume that rm can handle those. I wasn't sure if it was safe to delete the cache folder, but it didn't appear to be present after do-release-upgrade completed.

Revision history for this message
G (gkzf) wrote (last edit ):

In essences Trevor - yes.
I moved the directory, as i would have moved it back if the update had not been succeeded. (Being cautions)

To clarify, the move and running the fix install was after I had rebooted using previous 18.04 kernel set up, as the 20.04 was not complete/bootable.
So effectively running incomplete 20.04, under 18.04, (and therefore Libra Office and other applications did not run).
I hope that make sense.

Revision history for this message
Principal (dandu-01) wrote :

This bug is trying to boot my system late

Revision history for this message
No (thanks7) wrote :

I seem to be having the same trouble as the rest of you. Similar issues and messages were popping up during the attempted install. I am a fairly new user and have no idea how to fix this. If given instructions and a simple line of code I DO know how to open a terminal window and type in commands LOL.
Will someone email me when a solution is found?
Thanks a ton!

Revision history for this message
Georgia Garcia (georgiag) wrote :

I'm attaching the debdiff that fixes this issue on the apparmor pre-install script.

description: updated
Changed in apparmor (Ubuntu):
assignee: nobody → Georgia Garcia (georgiag)
Georgia Garcia (georgiag)
Changed in apparmor (Ubuntu):
status: Confirmed → In Progress
Georgia Garcia (georgiag)
Changed in apparmor (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Lukas Märdian (slyon) wrote :

Targetted to the Focal series and removed the ~ubuntu-sponsors team, as the debdiff got already sponsored into Focal and does not affect the newer series (Jammy+): https://launchpad.net/ubuntu/focal/+queue?queue_state=1&queue_text=apparmor

Changed in apparmor (Ubuntu Focal):
assignee: nobody → Georgia Garcia (georgiag)
status: New → In Progress
Changed in apparmor (Ubuntu):
status: In Progress → Fix Released
Changed in apparmor (Ubuntu Focal):
importance: Undecided → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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