| Summary: | Kopete forgets WLM passwords if password prompt is cancelled | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Christopher January <chris> |
| Component: | WLM Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kedgedev |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 4.6.2 | |
| Sentry Crash Report: | |||
| Attachments: | Patch to not call setWrong if the password prompt was cancelled by the user. | ||
|
Description
Christopher January
2010-03-10 10:46:12 UTC
I've not heard anything re: this bug, but I now know the cause.
WlmAccount::connectWithPassword does this:
if (pass.isEmpty ())
{
password ().setWrong (true);
return;
}
but pass may be empty if the password prompt dialog was cancelled. In that case KopetePasswordGetRequestPrompt::slotCancelPressed emits finished with QString::null as the password.
So calling setWrong is, err, wrong. Other protocols either call disconnect (e.g. JabberAccount::connectWithPassword ) or set the status to offline (YahooAccount::connectWithPassword).
Created attachment 43263 [details]
Patch to not call setWrong if the password prompt was cancelled by the user.
Related to bug 226270 but I didn't dup this one as it has a protocol specific patch. SVN commit 1223106 by lvsouza: Do not call setWrong if the password prompt has been cancelled by the user. Thanks Christopher January for the patch. BUG: 230181 M +1 -1 wlmaccount.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1223106 SVN commit 1223107 by lvsouza: Backport r1223106 by lvsouza from trunk to the 4.6 branch: Do not call setWrong if the password prompt has been cancelled by the user. Thanks Christopher January for the patch. CCBUG: 230181 M +1 -1 wlmaccount.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1223107 |