Bug 141016 - Jabber accounts with passwords not remembered have a problem connecting
Summary: Jabber accounts with passwords not remembered have a problem connecting
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (other bugs)
Version First Reported In: 0.12.3
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-01 18:42 UTC by Michał ,,KNT'' Gorycki
Modified: 2008-01-07 03:23 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michał ,,KNT'' Gorycki 2007-02-01 18:42:44 UTC
Version:           0.12.3 (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages

I have four Jabber accounts (one ICQ, one GG, btw). Three of them have their passwords stored in KWallet. One not (lets name it "red").
If I choose "Available*" for my status all of the accounts will connect, but the "red" won't. It's lightbulb will continue to flash till hell frezes.
When I choose to connect "red" manually, and then I connect the rest manually (choosing "Available" dosen't work), every thing works fine.

*-Sorry if I'm miss-translating it back to english. I thing about the first online status available in Kopete.
Comment 1 Michał ,,KNT'' Gorycki 2007-02-02 17:37:46 UTC
In the first case, when trying to connect the "red" account will fail with a message "Connection error: Operation not supported".
Comment 2 firepol 2007-07-19 17:34:03 UTC
I don't know if this is the same bug or not, but if I add my google talk account in kopete, using jabber as explained in this guide http://www.google.com/support/talk/bin/answer.py?hl=en&answer=57557 I tick the option to Remember Password. But it's never saved. Each time I open kopete I have to enter the password again.
Comment 3 Matt Rogers 2008-01-07 03:21:27 UTC
SVN commit 758161 by mattr:

Fix bug 141016.

QString::isNull() does not behave the same in Qt 4 as it did with Qt 3, and so
the password string was never null but it was empty.

BUG: 141016



 M  +2 -2      kopetepassword.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=758161
Comment 4 Matt Rogers 2008-01-07 03:23:49 UTC
SVN commit 758163 by mattr:

Fix bug 141016 for KDE 4.0.1

Backport from trunk

CCBUG: 141016



 M  +2 -2      kopetepassword.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=758163