"md5sums differ" message seems to indicate an install problem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AppArmor |
Invalid
|
Undecided
|
Unassigned | ||
Ubuntu GNOME |
Invalid
|
Undecided
|
Unassigned | ||
apparmor (Ubuntu) |
Fix Released
|
Low
|
Tyler Hicks | ||
Xenial |
Fix Released
|
Low
|
Tyler Hicks | ||
Yakkety |
Fix Released
|
Low
|
Tyler Hicks |
Bug Description
[Impact]
Confusing output from a diff command executed during the apparmor update process leaves users concerned about the state of their system.
[Test Case]
1. Make sure that apparmor 2.10.95-0ubuntu2 from the -release pocket is installed
2. Update to the apparmor package in -proposed
3. Look at the output during the update process to verify that the following message is *not* printed:
Files /var/lib/
[Regression Potential]
Considered to be extremely low. The change is a one-liner that pipes the stdout of diff command to /dev/null (the -q option of diff is not sufficient).
[Original description]
Upon applying the latest Ubuntu routine-update, I observed these messages:
Setting up apparmor (2.10.95-
Installing new version of config file /etc/apparmor.
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Skipping profile in /etc/apparmor.
Skipping profile in /etc/apparmor.
Files /var/lib/
"The reason why I am filing a bug report" is the LAST line. I presume that if md5sums do not agree, something was probably done improperly in preparing this particular software-update blast.
However, in-passing, I would also point out line #3, about "start and stop actions no longer supported." That seems to me to be something (of much less importance, obviously) that might have been overlooked. (I've seen =that= message for some time now.)
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor 2.10.95-0ubuntu2.2
ProcVersionSign
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Aug 17 14:22:55 2016
InstallationDate: Installed on 2016-03-02 (168 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdline: BOOT_IMAGE=
SourcePackage: apparmor
Syslog:
Aug 10 10:36:07 IntersignVM dbus[1638]: [system] AppArmor D-Bus mediation is enabled
Aug 11 13:10:08 IntersignVM dbus[1655]: [system] AppArmor D-Bus mediation is enabled
Aug 16 08:40:24 IntersignVM dbus[1693]: [system] AppArmor D-Bus mediation is enabled
Aug 17 13:58:37 IntersignVM dbus[1657]: [system] AppArmor D-Bus mediation is enabled
UpgradeStatus: Upgraded to xenial on 2016-05-11 (98 days ago)
Related branches
Changed in apparmor (Ubuntu): | |
importance: | Undecided → High |
Changed in apparmor (Ubuntu Xenial): | |
assignee: | nobody → Tyler Hicks (tyhicks) |
importance: | Undecided → Low |
status: | New → In Progress |
description: | updated |
Agree with OP on both points, but also note that when I check the two supposedly different files afterwards they are in fact identical except for timestamp:
$ sudo diff /var/lib/ dpkg/info/ apparmor. md5sums /var/lib/ apparmor/ profiles/ .apparmor. md5sums; echo $?
0