I discovered some line in /var/log/syslog regarding:
May 18 18:21:36 kiilo-precise kernel: [31338.049940] type=1400
audit(1337379696.854:31): apparmor="DENIED" operation="open" parent=1
profile="/usr/lib/telepathy/mission-control-5" name="/dev/tty" pid=13079
comm="mission-control" requested_mask="rw" denied_mask="rw" fsuid=1000 ouid=0
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
/usr/lib/telepathy/mission-control-5 {
[...}
/usr/lib/mission-control-plugins.*/ r,
/usr/lib/mission-control-plugins.*/*.so mr,
this three lines added:
/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
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/992619
Title:
Empathy does not login - Error contacting the Account Manager
Status in Chat app, and Telepathy user interface:
Incomplete
Status in “empathy” package in Ubuntu:
Triaged
Bug description:
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 send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.
---------------
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: empathy 3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Tue May 1 15:49:25 2012
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
SourcePackage: empathy
UpgradeStatus: Upgraded to precise on 2012-04-27 (4 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/992619/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
