Ubuntu
telepathy-mission-control-5 package

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

Bug #867793 reported by Chad Miller
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

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

Tags: apparmor
Jamie Strandboge (jdstrand)
tags: added: apparmor
Changed in telepathy-mission-control-5 (Ubuntu):
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Mon, 02 Jan 2012 14:53:08 -0600

Changed in telepathy-mission-control-5 (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.