[Bug 867793] [NEW] apparmor doesn't allow telepathy-haze to mknod() after network reset

Chad Miller chad.miller at canonical.com
Tue Oct 4 19:04:02 UTC 2011


Public bug reported:

In dmesg, after network is stopped and started:

Oct  4 14:54:46 localhost kernel: [64344.425370] type=1400
audit(1317754486.728:33): apparmor="DENIED" operation="mknod" parent=1
profile="/usr/lib/telepathy/telepathy-*"
name="/home/cmiller/.config/indicators/messages/applications-blacklist
/pidgin-libnotify.YF2E2V" pid=21052 comm="telepathy-haze"
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

** Affects: telepathy-mission-control-5 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of
Telepathy, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/867793

Title:
  apparmor doesn't allow telepathy-haze to mknod() after network reset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/867793/+subscriptions




More information about the Ubuntu-telepathy mailing list