Ubuntu
dbus package

  1. Bug #1264148
  2. Comment #2

Comment 2 for bug 1264148

Revision history for this message
Seth Arnold (seth-arnold) wrote :

Just for confirmation -- the ubuntu-bug attached files here are from Saucy, but the bug happened under Raring, correct?

The dbus version listed in the Dependencies.txt file would certainly have the ability to block specific dbus-messages via AppArmor configuration; the version in Raring should not have had that ability, unless you were playing around with pre-release AppArmor packages. Of course there's some policy mechanisms in pre-Saucy Dbus as well, but I'm much less familiar with that...

For information on the Saucy AppArmor Dbus integration, check out http://penguindroppings.wordpress.com/2013/10/18/application-isolation-with-apparmor-part-iii/

Since you've still got your Raring install around, it'd be nice to know the version of the dbus, apparmor, and linux-image* packages installed, and logging from the /var/log/syslog at the time of a failed login attempt. That'll help us figure out where to place the blame.

Thanks