Version: (using KDE KDE 3.5.7) Installed from: Ubuntu Packages OS: Linux Can't connect to msn account. Jabber is working. Message: "unhandled msn error code 403, please fill an error report with konsole output if possible." So here's the konsole output, which doesn't seem too informative: (the last bit is danish, it says sumthin like "connection closed by remote host") QGDict::hashKeyString: Invalid null key kopete: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file jabberchatui.rc kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (ekstern vært lukkede for forbindelsen)
*** Bug 151025 has been marked as a duplicate of this bug. ***
*** Bug 151055 has been marked as a duplicate of this bug. ***
Does this still happen in recent versions? I can't reproduce in kopete 0.5.80
No, I haven't seen it for a very long time. I say, just close this bug report.
Thanks for your feedback. Please reopen if this bug comes back.
I see this bug since today. openSuSE-11.0 package. No console output, sorry. Please reopen this bug.
Rolf, kde 3.5.9, 4.0.x or 4.1 ?
Sorry! 3.5.9
Note: I use Kubuntu Hardy at work (KDE 3.5.9, too). And here, it works. Maybe it was just a temporary problem yesterday. I will re-check, when I am at home again.
I installed kopete from 3.5.9 in Opensuse 11.0 and I can't reproduce. I guess it seems dependent on some server message.
Today it works again on opensuse. Strange. Seems to be have been a temporary problem yesterday. Sorry!
You don't have to apologize, as far as I know, if it says " unhandled msn error code 403, please fill an error report with konsole output if possible. " then the bug is still there but only appears from time to time. The question is if it only happens in 3.5.x .
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.