| Summary: | Kopete: It seems we have been directed to a different server | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Jeffrey <eljefedelito> |
| Component: | Jabber Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | andrew.crouthamel, eljefedelito |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone! This report is over 9 years old. If t wasn't interesting then, and can't be reproduced now, I don't think this is worth our time to dig deeper. Please consider closing this report. Thanks for KDE. Thanks for the update! |
Version: 0.70.90 (using 4.3.00 (KDE 4.3.0), Debian packages) Compiler: cc OS: Linux (i686) release 2.6.30-1-686 Not sure about other protocols or networks but on talk.google.com: Occasionally talk.google.com will, for whatever reason, tell Kopete or whatever chat client to change servers. Kopete will pop up a message that reads something like, "It seems we have been directed to another server. I do not know how to handle this. talk.google.com." My suggestion is that Kopete automatically reconnects, maybe after a 2 second delay or something. I've never had a manual reconnect fail, and if Kopete is smart enough to know why we've been disconnected ("directed to another server...") then why not try to fix itself? If auto-reconnecting does fail after, say, 3 tries, than give a popup.