Empathy fails connecting to jabber account - "No reason specified"

[Łukasz Zemczak]

I have seen some other people reporting a similar bug (e.g. #753820) with similar issues, but not sure if the causes are the same. Might be a duplicate in the end.

Situation: I was using Empathy with this jabber account for some time now, everything worked fine. Until one day it simply stopped working - that day no updates have been made or system changes. Empathy simply can't connect to the account, giving an error "No reason specified". Other clients connect correctly. I have attached mission-control and gabble (jabber) logs for convenience.

I did some research and experiments regarding this bug, as I am able to temporarily remove it. It seems the problem might be related to mission-control-5. After removal of the .mission-control directory, killing the mission-control-5 process, and inputting account data anew, Empathy connects with no problems. Disconnecting and connecting works correctly. The problem re-appears whenever Empathy is restarted.
No changes seem to happen in .mission-control/ between the working and not working versions (diff -urN returns nothing).
Reinstall of empathy by itself doesn't help.

Ubuntu version: 11.04
Packages version: empathy (2.34.0-0ubuntu3.1), telepathy-mission-control-5 (1:5.7.7-1)

[Łukasz Zemczak (sil2100)]

I'll try looking into it some more later.

[Łukasz Zemczak (sil2100)]

I found out the problem, but still I would need to find the very root cause of this issue. It seems that a Jabber MUC I had set as auto-join suddenly started killing the whole connection for yet unknown to me reasons. I missed this lead because I wrongly assumed that settings such as favorite channels are being held alongside account data in .mission-control/. But as they are not, even after reconfiguring the account, auto-join was still enabled and crashed the connection.

It seems trying to join that given MUC kills the connection, which I think still should not happen. But at least I found a work-around my problem. Will try some more regarding this issue.

[Bilal Shahid (s9iper1)]

attach the auth client log file with it?

[Łukasz Zemczak (sil2100)]

The MUC that was causing problems no longer exists, so providing an auth client log file from a session where the problem occurred is impossible. Sadly. So let's leave it as Incomplete.

[Launchpad Janitor (janitor)]

[Expired for empathy (Ubuntu) because there has been no activity for 60 days.]