Comment 2 for bug 857610

The following also seems to be related to this bug...

I am experiencing an issue on one of two systems that I log into. I'm not sure if the differences between the two systems are causing this, or if something else is going on.

My problem started by initially configuring Empathy for a sipe account. All was fine until I had to log out and back in again. This is when I noticed that my account information was missing. After poking around a bit, I discovered these in /var/log/syslog:

Nov 17 15:24:38 linux13 kernel: [26233.295858] type=1400 audit(1321561478.257:1276): apparmor="DENIED" operation="open" parent=11498 profile="/usr/lib/telepathy/mission-control-5" name="/nas/users02/daly/.mission-control/accounts/accounts.cfg" pid=11499 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1245 ouid=1245
Nov 17 15:24:38 linux13 kernel: [26233.301999] type=1400 audit(1321561478.265:1277): apparmor="DENIED" operation="open" parent=1 profile="/usr/lib/telepathy/mission-control-5" name="/nas/users02/daly/.cache/.mc_connections" pid=11499 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1245 ouid=1245
[..]

The first DENIED message indicates that apparmor is preventing Empathy from reading the file it keeps the account details in.

I modified the program "telepathy" such that it's in "complain" mode. I was then able to log out and back in again, having Empathy successfully re-read my existing account information.

I can provide further details if needed. Thanks.