Red Hat Bugzilla – Bug 158214
MSN login in kopete fails with bad password error
Last modified: 2007-11-30 17:11:06 EST
Description of problem:
When kopete attempts to login to MSN servers login fails with bad password
error. While the password is indeed correct.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create msn account in kopete
2. attempt to login
login fails. with bad password error.
has additional info including info on patch applied to svn tree
Created attachment 114685 [details]
Patch to fix Kopete MSN login for kdenetwork-3.3.1
Due to my impatience I've back-ported the Kopete MSN login fix to FC3. The
patch was created against kdenetwork-3.3.1 and then added to the
kdenetwork-3.3.1-3 FC3 package. After building kdenetwork with the patch I
successfully logged into MSN with Kopete.
Are there any plans to fix this bug for FC3? Although I've managed to build a
patched version of kdenetwork-3.3.1-3 others may not be capable of doing this.
It's approaching a fortnight since this bug was reported here. Unfortunately
this is also the type of response I've seen from another distribution as well.
Gaim appears to be updated frequency and Kopete not at all.
I'd really appreciate this fix, Kopete's a nicer IM client for KDE users.
This bug's still not fixed in Stentz.
(I wonder why FC4 comes with KDE 3.4.0 instead of 3.4.1 ?!)
This fix is included in new kde-3.4.1. I'm still packaging kde-3.4.1 for FC4 and
probably for FC3 . I hope it will be done this week. Many thanks for your report.
*** Bug 160424 has been marked as a duplicate of this bug. ***
(In reply to comment #5)
> This fix is included in new kde-3.4.1. I'm still packaging kde-3.4.1 for FC4
> probably for FC3 . I hope it will be done this week. Many thanks for your
While I have since upgraded to FC4 I can't help but notice that kdenetwork
still hasn't been patched for FC3. It has
been 8 weeks since I posted an example of a patch in a previous comment at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=158214#c1 that I used in
the new kdenetworl-3.3.1 including this fix will be pushed this week ;-)
Sorry for the delay