Bug 133271

Summary:	Kopete: MSN slow login with proxy
Product:	[Unmaintained] kopete	Reporter:	David Naylor <naylor.b.david>
Component:	MSN Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	kde.bugs
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	FreeBSD
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description David Naylor 2006-08-30 14:11:12 UTC

Version:           unknown (using KDE 3.4.2, compiled sources)
Compiler:          gcc version 3.4.4 [FreeBSD] 20050518
OS:                FreeBSD (i386) release 6.0-RELEASE

I have seen other reports saying Kopete doesn't support proxy settings, HTTP or SOCKS.  As far as I can see, it doesn't, nor does it need to.  In the Konqueror settings for Proxy (which is the global settings for KDE!!!) there is a tab for SOCKS.  If you have a correctly installed socks lib (Dante and tsocks didn't work for me, but socks5(NEC Socks) does) then whenever Kopete tries to connect it will use socks.  I'm not sure if Kopete works with plain HTTP proxies, if it uses the same mechanisms (socket libraries) then it should.  I have also got Kopete to work with: runsocks kopete

My problem: Kopete takes over 2 minutes to connect to MSN.  I have run: while true; do netstat -p tcp; sleep 1; clear; done.  For the most part of the two minutes there doesn't seem to be any connections, attempted or connected and only closer to the end does something happen.  This corresponds to the messages Kopete prints on the consol.  Only after a long time does it show that is trying to connect and sending messages to MSN.  

I have had a similar experience with IRC, the long delay before connection.  The only reason I can see for this is Kopete just waits a few minutes before trying to connect.  

I am behind a firewall and the only way out is through proxies, HTTP and SOCKS.  

Thanks for your help
David

Comment 1 Tim Weber 2007-10-04 21:13:25 UTC

I can confirm that something like this still happens with 3.5.7 when running "tsocks kopete --nofork". tsocks is configured to use a "ssh -D" proxy. Without --nofork the connection does not get tunneled at all.

My MSN plugin is set to auto-connect on startup, it blinks a bit when starting, then turns grey. If I set it offline, then online again, it connects in "normal" time (about 10 seconds). Don't know if it's related to this bug, but it sounds pretty similar.

Can I supply you with more information to help you solve this issue?

Comment 2 Matt Rogers 2008-11-15 06:08:53 UTC

We've completely replaced the current MSN implementation with a new MSN implementation which  If you continue to experience this bug after testing the new implementation (which can be gotten from our subversion repository or with the KDE 4.2 Beta 1 release), PLEASE, open a new bug rather than reopening this bug. Thank you for your time and efforting in helping us find and fix problems in Kopete.