Version: 1.0.0 (using KDE 4.4.0) OS: Linux Installed from: openSUSE RPMs There was a problem with live msn network a while ago, rejecting logins and kopete was asking for a password, though a valid one was provided. This is fine - not a kopete problem. The problematic part is that account value PasswordIsWrong is not properly reset when a password is accepted as good, this will occasionally reprompt user for a valid password, though a valid one exists in wallet manager. Manually resetting PasswordIsWrong=true to false is a workaround if kopete is asking to reenter password even when a correct one already exists.
I'm facing the same problem. Bug 229645 and bug 254152 are possible duplicates.
*** Bug 254152 has been marked as a duplicate of this bug. ***
I can see the same problem in Fedora 14 with KDE 4.5.3 and Kopete 1.0.80. I don't use msn like reporter of this bug, but I guess the problem is the same - once a while server responds the password is wrong (or maybe there is different failure) and kopete marks password as wrong even if it's still correct. I use following workaround: Because PATH on my system contains /usr/local/bin before /usr/bin (can be checked with echo $PATH ). I've created file /usr/local/bin/kopete with content: sed -i 's|^\(PasswordIsWrong=\).*$|\1false|' ~/.kde/share/config/kopeterc exec /usr/bin/kopete $@ and made it executable. Matej: Yes, you're right. It was duplicate, so I (being a reporter of duplicate bug) closed it as duplicate of this one.
I think kopete should work this way: 1) use password from kwallet 2) if authentication fails with wrong password reason, mark password as wrong 3) ask user for new password with input fields (pre)filled with old stored password 4) if password succeeds, store current password to kwallet and mark password as correct in kopeterc if kopete starts and finds password being marked as wrong, start with step 3)
*** Bug 229645 has been marked as a duplicate of this bug. ***
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!