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

[Launchpad Bug Tracker]

This bug was fixed in the package telepathy-mission-control-5 -
1:5.10.1-1ubuntu2

---------------
telepathy-mission-control-5 (1:5.10.1-1ubuntu2) precise; urgency=low

  * AppArmor updates to debian/apparmor-profile:
    - allow write for indicators on network restart for haze (LP: #867793)
    - allow reads for indicators for haze (LP: #871497)
    - allow launching of skype from haze (LP: #878839)
    - don't allow mmap of files owned by user
    - allow mission-control-5 writes to .{cache,config}/dconf/user and
      .local/share/telepathy/mission-control/*
 -- Jamie Strandboge <jamie at ubuntu.com>   Mon, 02 Jan 2012 14:53:08 -0600

** Changed in: telepathy-mission-control-5 (Ubuntu)
       Status: Triaged => Fix Released

-- 
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