Bug 253184 - kopete doesn't realise it's been disconnected and therefore won't reconnect
Summary: kopete doesn't realise it's been disconnected and therefore won't reconnect
Status: RESOLVED DUPLICATE of bug 210793
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-04 01:32 UTC by Alessandro Ghersi
Modified: 2011-03-20 04:28 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alessandro Ghersi 2010-10-04 01:32:17 UTC
Version:           unspecified (using KDE 4.3.2) 
OS:                Linux

Bug reported here:
https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/557849
Kopete doesn't realise it has been disconnected, at least when connected to XMPP servers, and therefore doesn't automatically reconnect. Therefore it always has to be manually disconnected and reconnected after, say, every sleep-wake cycle.

Steps to reproduce:
1. Configure Kopete to connect to XMPP servers. Mine is connected to Facebook chat and Google Chat.
2. Set Kopete running. Check that some contacts show up as being online.
3. Put your machine to sleep and wake it up again.
4. Look at your contacts. They are all marked offline.
5. Change status to online. This will not work.
4. Change status to offline and then to online. Now your contacts will appear to come online again.

ProblemType: Bug
Architecture: amd64
Date: Thu Apr 8 01:08:58 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: kopete 4:4.3.2-0ubuntu4
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: kdenetwork
Uname: Linux 2.6.31.6-rt19 x86_64


Reproducible: Didn't try
Comment 1 Lamarque V. Souza 2011-03-20 04:28:52 UTC

*** This bug has been marked as a duplicate of bug 210793 ***