| 2016-08-17 18:37:02 |
Mike Robinson |
bug |
|
|
added bug |
| 2016-08-19 09:23:54 |
Launchpad Janitor |
apparmor (Ubuntu): status |
New |
Confirmed |
|
| 2016-08-19 09:24:05 |
Wise Melon |
bug task added |
|
apparmor |
|
| 2016-08-19 09:24:15 |
Wise Melon |
apparmor: status |
New |
Confirmed |
|
| 2016-08-19 09:24:27 |
Wise Melon |
bug task added |
|
ubuntu-gnome |
|
| 2016-08-19 09:24:37 |
Wise Melon |
ubuntu-gnome: status |
New |
Confirmed |
|
| 2016-08-19 09:25:36 |
Wise Melon |
tags |
amd64 apport-bug xenial |
amd64 apport-bug xenial yakkety |
|
| 2016-08-19 09:26:52 |
Wise Melon |
bug |
|
|
added subscriber Nikita Yerenkov-Scott |
| 2016-08-26 12:17:52 |
Alberto Salvia Novella |
apparmor (Ubuntu): importance |
Undecided |
High |
|
| 2016-08-26 18:28:34 |
Tyler Hicks |
apparmor: status |
Confirmed |
Invalid |
|
| 2016-08-26 18:29:19 |
Tyler Hicks |
ubuntu-gnome: status |
Confirmed |
Invalid |
|
| 2016-08-26 18:29:31 |
Tyler Hicks |
apparmor (Ubuntu): status |
Confirmed |
In Progress |
|
| 2016-08-26 18:29:37 |
Tyler Hicks |
apparmor (Ubuntu): importance |
High |
Low |
|
| 2016-08-26 18:29:40 |
Tyler Hicks |
apparmor (Ubuntu): assignee |
|
Tyler Hicks (tyhicks) |
|
| 2016-08-26 23:11:19 |
Tyler Hicks |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-08-26 23:11:19 |
Tyler Hicks |
bug task added |
|
apparmor (Ubuntu Xenial) |
|
| 2016-08-26 23:11:19 |
Tyler Hicks |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-08-26 23:11:19 |
Tyler Hicks |
bug task added |
|
apparmor (Ubuntu Yakkety) |
|
| 2016-08-26 23:11:37 |
Tyler Hicks |
apparmor (Ubuntu Xenial): importance |
Undecided |
Low |
|
| 2016-08-26 23:11:37 |
Tyler Hicks |
apparmor (Ubuntu Xenial): status |
New |
In Progress |
|
| 2016-08-26 23:11:37 |
Tyler Hicks |
apparmor (Ubuntu Xenial): assignee |
|
Tyler Hicks (tyhicks) |
|
| 2016-08-26 23:16:22 |
Tyler Hicks |
description |
Upon applying the latest Ubuntu routine-update, I observed these messages:
Setting up apparmor (2.10.95-0ubuntu2.2) ...
Installing new version of config file /etc/apparmor.d/abstractions/dbus-session-strict ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Skipping profile in /etc/apparmor.d/disable: usr.sbin.apache2
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Files /var/lib/dpkg/info/apparmor.md5sums and /var/lib/apparmor/profiles/.apparmor.md5sums differ
"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
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
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-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/hostname--vg-root ro
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) |
[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/dpkg/info/apparmor.md5sums and /var/lib/apparmor/profiles/.apparmor.md5sums differ
[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-0ubuntu2.2) ...
Installing new version of config file /etc/apparmor.d/abstractions/dbus-session-strict ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Skipping profile in /etc/apparmor.d/disable: usr.sbin.apache2
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Files /var/lib/dpkg/info/apparmor.md5sums and /var/lib/apparmor/profiles/.apparmor.md5sums differ
"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
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
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-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic root=/dev/mapper/hostname--vg-root ro
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) |
|
| 2016-08-27 00:23:54 |
Launchpad Janitor |
branch linked |
|
lp:~apparmor-dev/apparmor/apparmor-ubuntu-citrain |
|
| 2016-08-28 19:22:49 |
Launchpad Janitor |
apparmor (Ubuntu Yakkety): status |
In Progress |
Fix Released |
|
| 2016-08-29 19:39:11 |
Chris J Arges |
apparmor (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-08-29 19:39:16 |
Chris J Arges |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-08-29 19:39:20 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2016-08-29 19:39:28 |
Chris J Arges |
tags |
amd64 apport-bug xenial yakkety |
amd64 apport-bug verification-needed xenial yakkety |
|
| 2016-10-27 03:28:53 |
Tyler Hicks |
tags |
amd64 apport-bug verification-needed xenial yakkety |
amd64 apport-bug verification-done xenial yakkety |
|
| 2016-10-27 15:26:50 |
Launchpad Janitor |
apparmor (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
