Summary: | Empathy connect and disconnects immediatly when I trying to access an olark (jabber) account | ||
---|---|---|---|
Product: | Telepathy | Reporter: | crashbit <crashbit> |
Component: | gabble | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED NOTOURBUG | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | 0.9 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
URL: | http://crashbit.homelinux.com | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
log file of reconnect
log of frequent reconnect with gabble 0.9.5 |
Description
crashbit
2010-02-12 10:54:46 UTC
If Gabble's crashing, could you get a backtrace as per http://telepathy.freedesktop.org/wiki/Debugging ? Created attachment 33586 [details]
log file of reconnect
Created attachment 33587 [details]
log of frequent reconnect with gabble 0.9.5
As per request I attached a log of the frequent disconnect/reconnect from telepathy-gabble 0.9.5
Regards,
Sebastian
From both logs (Gabble 0.8 and 0.9) it looks like the server just disconnects us. Usually this is because either the servers keepalive is lower then the keepalives gabble sends or the server not understnading whitespace and/or TCP keepalives. Given that you're using ejabberd i'm quite surprised this happens, has the admin configured its timeouts very low or? This comment was posted on http://www.olark.com/forum/viewtopic.php?id=648 Hmm. I actually have some theories now, we are working on a new backend that might solve this problem. We'll definitely test gabble once the backend is deployed. -ben http://www.olark.com/forum/viewtopic.php?id=648 suggests that this wasn't our bug. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.