Bug 203609 - Kopete: It seems we have been directed to a different server
Summary: Kopete: It seems we have been directed to a different server
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-12 21:22 UTC by Jeffrey
Modified: 2018-11-17 04:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey 2009-08-12 21:22:52 UTC 
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.
Comment 1 Andrew Crouthamel 2018-11-02 23:06:40 UTC 
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!
Comment 2 Andrew Crouthamel 2018-11-16 05:26:10 UTC 
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!
Comment 3 Jeffrey 2018-11-16 15:34:56 UTC 
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.
Comment 4 Andrew Crouthamel 2018-11-17 04:44:40 UTC 
Thanks for the update!