Bug 132536 - kopete does not connect on session restore
Summary: kopete does not connect on session restore
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kopete
Classification: Applications
Component: Main Application (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-17 11:20 UTC by madman
Modified: 2010-01-17 11:59 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description madman 2006-08-17 11:20:44 UTC
Version:           0.12.1 (using KDE 3.5.4, Gentoo)
Compiler:          gcc version 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)
OS:                Linux (i686) release 2.6.17-ck1

Sometimes kopete does not connect to IM networks on session restore (logging out of KDE and then logging back in). It doesn't even connect when manually forced to do so.
Quitting kopete and starting it again helps.

Observed behaviour: kopete sometimes does not connect to IM servers on session restore and fails to connect even on manual forcing

Expected behaviour: kopete should connect to IM networks on KDE session restore
Comment 1 Olivier Goffart 2006-09-17 12:46:15 UTC
I cannot reproduce the problem here,  can you give more information.
Is there any meainignfull debug output ?
Maybe a problem with KWallet ?
Comment 2 madman 2006-09-17 13:49:27 UTC
Happens only with kopete bundled with KDE 3.5.3/4

Kopete 0.12.2 downloaded separately (net-im/kopete gentoo package) works correctly.
Comment 3 Matt Rogers 2006-12-06 23:16:06 UTC
kopete 0.12.2 reported working. Closing this bug.
Comment 4 Hobbsee 2007-07-20 16:53:06 UTC
Still getting reports at https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/91507 that this isnt fixed.

Please reopen this bug, and look into this.
Comment 5 Matt Rogers 2007-07-20 21:59:58 UTC
logging in on session restore never worked, unless you had some mechanism in place that connected you automatically when kopete started
Comment 6 Stef Louwers 2008-07-07 04:53:01 UTC
on kde4 (kopete 0.50.1):
with auto-connect disabled it does not reconnect on restore, but also no problems doing that manually;
with auto-connect enabled it reconnects just fine.
Comment 7 Viktor Engelmann 2008-08-12 01:20:58 UTC
I still have this bug in 0.12.7
i have auto-connect on startup, but it usually doesn't connect on session restore.

IRC connects, which doesn't need a password, so this might be an error with wallets - i have no password for the wallet and kopete is always allowed to access it - but i also have seen kopete connect, although kwalletmanager didn't run...
Comment 8 Pal Körössy 2008-08-28 00:39:51 UTC
This bug occurs here on OpenSUSE 11.0 in 0.12.7. When it doesn't reconnect, I can't even close the application sometimes. It's been configured not to use KWallet.
Comment 9 Don Cahoon 2008-10-03 19:23:50 UTC
I have seen this bug on OpenSuSE 11.0 running KDE 4.1.2 (release 44.2) and Kopete 0.60.2.  Additional observations:
- KDE 4 version of Kopete can connect once on a particular Yahoo account, but will not connect a second time if the connection is broken.  This only happens on 1 Yahoo account.  I have no problems with a second Yahoo account.
- KDE 4 version of Kopete connects (forces logout of Yahoo on another machine), but does not hold the connection.  After what appears to be about 3 attempts it stops trying.
- KDE 3 version of Kopete on the same machine works fine. Reconnections are not a problem.
- Removing/renaming the ~/.kde/share/apps/kopete/contactlist.xml resolved the issue with KDE 4 Kopete.  Once this file is recreated by logging back in with KDE 3 Kopete or renaming it to his original name then the issue reappears.
Comment 10 Roman Jarosz 2010-01-17 11:59:35 UTC
Closing this bug as this bug report contains mostly bugs reported against KDE 3 and we don't have manpower to support Kopete in KDE 3.

If you still see some of this bugs in KDE 4.2 or later please create new bug report for each bug. Thanks.