touch-packages team mailing list archive

[Jamie Strandboge <jamie@xxxxxxxxxx>]

Thank you for using Ubuntu and filing a bug.

$ aa-decode 2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E6C6F63616C2F73686172652F74656C6570617468792F6D697373696F6E2D636F6E74726F6C2F6163636F756E74732E636667
Decoded: /media/Storage/Profile/Ubuntu 14.04/loostro/.local/share/telepathy/mission-control/accounts.cfg

Piotr, it looks like you have your HOME set to something non-standard.
Please see https://wiki.ubuntu.com/DebuggingApparmor#Adjusting_Tunables
for how to adjust your system to work with this.

** Changed in: telepathy-mission-control-5 (Ubuntu)
       Status: New => Invalid

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

Title:
  telepathy-mission-control is trying to open weird files on startup

Status in “telepathy-mission-control-5” package in Ubuntu:
  Invalid

Bug description:
  Upon startup I'm getting a notice that an error occured. When I check
  the syslog I see errors like:

  Sep  6 19:57:22 Earth kernel: [   86.045357] type=1400 audit(1410026242.433:76): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462 pid=3007 comm="mission-control" requested_mask="rw" denied_mask="rw" fsuid=1000 ouid=1000
  Sep  6 19:57:22 Earth kernel: [   86.045707] type=1400 audit(1410026242.433:77): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462 pid=3007 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Sep  6 19:57:22 Earth kernel: [   86.050493] type=1400 audit(1410026242.437:78): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F64636F6E662F75736572 pid=3007 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Sep  6 19:57:22 Earth kernel: [   86.108894] type=1400 audit(1410026242.497:79): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E6C6F63616C2F73686172652F74656C6570617468792F6D697373696F6E2D636F6E74726F6C2F6163636F756E74732E636667 pid=3007 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

  According to http://askubuntu.com/questions/410808/what-is-reason-for-
  apparmor-denied-operation-open, telepathy-mission-control-5 is trying
  to open a file it has no access to.

  However, the "name" part is completely rubbish. How can check what
  file telepathy is actually trying to open? How do I fix that?

  I am on Ubuntu 14.04 LTS.

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