GNOME Bugzilla – Bug 675324
Empathy does not login - Error contacting the Account Manager
Last modified: 2012-05-24 17:15:22 UTC
Originally reported at: https://bugs.launchpad.net/bugs/992619 As soon as I launch empathy, I get the following error message: --------------- Error contacting the Account Manager There was an error while trying to connect to the Telepathy Account Manager. The error was: Did not receive a reply. Possible causes include: the remote application did not terminal out put tom@blacknight:~$ empathy (empathy:19911): folks-WARNING **: Error preparing Backend 'telepathy': Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (empathy:19911): libebook-WARNING **: e_book_client_new: Cannot get book from factory: Invalid source (empathy:19911): folks-WARNING **: Error preparing persona store 'eds:1269739475.6653.5@blacknight': Couldn't open address book ‘1269739475.6653.5@blacknight’: Invalid source (empathy:19911): folks-WARNING **: postal-address-details.vala:283: Empty postal address passed to PostalAddressFieldDetails.
two different debug logs by 2 users http://pastebin.com/KZ44DCBH http://pastebin.com/Q7S2d9tR
Humm I suspect mission-control is crashing for some reason. Could you please: - Make sur empathy and mission-control-5 are not running - export MC_DEBUG=all - gdb /usr/lib/telepathy/mission-control-5 - r - Start Empathy and check what happens in mission control
- Made sure empathy and mission-control processes were killed - done Mission Control output: http://pastebin.com/e0mUv9z4 Empathy output: http://pastebin.com/MxkdgS1e Killing mission-control for this made empathy behave in a different manor, in that no error message came up and it sort of looks like it's signed in. I could at least go into Accounts and manually enable my IM accounts.
(process:1226): mcd-WARNING **: _storage_dup_value: cannot get property param-account, unknown type (null) looks weird. Could you please mail me (guillaume.desmottes@collabora.co.uk) your ~/.mission-control/accounts/accounts.cfg and ~/.local/share/telepathy/mission-control/cassidy@cass-x200s ?
Just confirming in here that the steps outlined in comment #2 resolved the issue for me; merely killing/restarting the mission-control5 process.
Thanks for your accounts.cfg; I don't see anything suspicious in it. Could you please: - killall -9 empathy - killall -9 mission-control-5 - export GDEBUG=fatal-warnings - Install telepathy-mission-control-5-dbg - gdb /usr/lib/telepathy/mission-control-5 - hit 'r' in gdb - hit 'c' when you hit the "mcd-WARNING **: Could not add client names match rule" error - hit 'bt full' when you hit the "mcd-WARNING **: _storage_dup_value: cannot get property param-account, unknown type (null)" - Attach the full backtrace here.
I'll update this thread with the require information the next time I receive the error. It hasn't reproduced itself for several days now. http://pastebin.com/WgmzZT5T The link above shows the output of when I tried following Guillaume's instructions.
Sorry, "killall -9 mission-control-5" should be "killall -9 /usr/lib/telepathy/mission-control-5"
Hi, Im running emapty on a ubuntu precise machine, dont know the apparmor setting in debian, but maybe this could be applied also for debian. found following lines in /var/log/syslog: May 19 11:21:37 kiilo-precise kernel: [45343.111207] type=1400 audit(1337440897.232:32): apparmor="DENIED" operation="open" parent=21468 profile="/usr/lib/telepathy/mission-control-5" name="/var/lib/dbus/machine-id" pid=21469 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 May 19 11:21:37 kiilo-precise kernel: [45343.111684] type=1400 audit(1337440897.232:33): apparmor="DENIED" operation="exec" parent=21469 profile="/usr/lib/telepathy/mission-control-5" name="/usr/bin/dbus-launch" pid=21470 comm="mission-control" requested_mask="x" denied_mask="x" fsuid=0 ouid=0 May 19 11:21:37 kiilo-precise kernel: [45343.111887] type=1400 audit(1337440897.232:34): apparmor="DENIED" operation="open" parent=21468 profile="/usr/lib/telepathy/mission-control-5" name="/var/lib/dbus/machine-id" pid=21469 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 May 19 11:21:37 kiilo-precise kernel: [45343.112310] type=1400 audit(1337440897.236:35): apparmor="DENIED" operation="exec" parent=21469 profile="/usr/lib/telepathy/mission-control-5" name="/usr/bin/dbus-launch" pid=21471 comm="mission-control" requested_mask="x" denied_mask="x" fsuid=0 ouid=0 crossed my fingers and added following lines to /etc/apparmor.d/usr.lib.telepathy in the section after: /usr/lib/telepathy/mission-control-5 { [...} /usr/lib/mission-control-plugins.*/ r, /usr/lib/mission-control-plugins.*/*.so mr, I aadded this three lines: /var/lib/dbus/* r, /usr/bin/dbus-launch x, /dev/tty* rw, [...] and the behaviour disapeared for now ~ still there is an issue for google talk its possible to define an account by telepathy or by system settings but this is maybe another story / bug / feature wish you well kiilo
Sounds like a bug in Ubuntu's apparmor configuration then. Please report to launchpad.
Also reported there - if you are on debian check there please too and i like to see at least one confirmation from others before close https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/992619 just checked its pointed to apparmor bugs thanks kiilo