Empathy can't connect to a Jabber account.

[Mike Mestnik]

Hello,
  #361731 says to open a new bug. #576335 seams to have something working, however in my case even irc is not connecting.

http://pastebin.com/eijLQ7sm

http://pastebin.com/QhrUHTPi

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: telepathy-gabble 0.16.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-6.12-generic-pae 3.2.0-rc6
Uname: Linux 3.2.0-6-generic-pae i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Tue May 29 11:52:40 2012
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=C
 SHELL=/bin/bash
SourcePackage: telepathy-gabble
UpgradeStatus: Upgraded to precise on 2011-12-21 (159 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Aaron Roydhouse (aaron-roydhouse)]

After upgrade to 12.04 my Empathy and jabber accounts were working fine. After recent ubuntu updates (last few days) it is unstable and usually dies a little while after login. Empathy locks up for a while then say can't connect to Telepathy. Logging out/in and full restarts don't fix it, in that telepathy appears to lock up after time.

"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."

Manually killing and restarting all telepathy and empathy processes does fix the problem for a while, but when I look later I find jabber accounts no long working and telepathy shows errors like above if I try to connect.

When I restart mission-control-5 I get a warning, though may be nothing unusual?

(process:5511): mcd-WARNING **: Could not add client names match rule: Key 'arg0namespace' in match rule contains junk after argument number. Only 'path' is optionally valid ('arg0path' for example).

And while connecting get some of these warnings, labelled 'CRITICAL', permission problem?

(process:5511): mcd-CRITICAL **: _mcd_channel_set_status: assertion `channel->priv->status != MCD_CHANNEL_STATUS_FAILED' failed

[Bilal Shahid (s9iper1)]

please attach the mission control log file and with which account you are having this problem ?

[Mike Mestnik (cheako)]

Bilal Shahid,
  Looks like the logs are devoid of any useful information, this can't possibly be our fault.
http://pastebin.com/eijLQ7sm
http://pastebin.com/QhrUHTPi

If Aaron Roydhouse says the only messages he gets are these warning, then likely he has all the same DEBUG messages I do.

[Mike Mestnik (cheako)]

...You didn't read the report vary well, I'll not repeat myself.