desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #15378
[Bug 848757] Re: Empathy fails connecting to jabber account - "No reason specified"
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.
--
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/848757
Title:
Empathy fails connecting to jabber account - "No reason specified"
Status in “empathy” package in Ubuntu:
New
Bug description:
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/848757/+subscriptions
References