You are not logged in.

Dear visitor, welcome to If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.


Friday, February 2nd 2007, 11:33pm

(kopete 0.12.4) fail to connect to msn


i can't connect to msn messenger via kopete for the last few days. i can't say precisely when this began. i upgraded kde to 3.5.6 few days ago, so maybe it started then. i just made a test and installed gaim - no problems with connection to msn!

any help anybody?



Monday, February 5th 2007, 3:40pm

it's not 0.12.4! i downgraded to 0.12.3 and result was the same. no error message, it just doesn't connect.
any help for the helpless?


This post has been edited 1 times, last edit by "toxic-hero" (Feb 5th 2007, 3:40pm)


Monday, February 5th 2007, 3:46pm

konsole says:
kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (remote host closed connection)


Tuesday, February 6th 2007, 1:28pm

i found out (somehow) that installing torK and privoxy caused this. now i uninstalled both but the problem gets even bigger.
msn bird icon now gives up after a two seconds, not after a minute or two like before. and KOrganizer now can not connect to Google calendar anymore. "Could not connect to host Proxy localhost at port 8118"

any help before i kill myself? ;(



Tuesday, February 6th 2007, 7:06pm

you should remove the proxy configuration too ;)
Help mee om KDE 3.5.5 in het Nederlands te vertalen


Tuesday, February 6th 2007, 7:20pm

hmm.. i share your opinion but i don't know how to do it. i did never change any configuration on kopete or KOrganizer regarding proxy. maybe torK or privoxy did it automatic. i looked around and couldn't find such settings on kopete or kontact. i'd be very grateful if someone helped me with that.

thanks for your answer,



Tuesday, February 6th 2007, 7:40pm

problem solved! the system settings were changed. on kubuntu:
system settings/network settings/proxy/connect to internet directly


This post has been edited 1 times, last edit by "toxic-hero" (Feb 6th 2007, 7:41pm)