Bug 66919

Summary: account gone configuration (missing password)
Product: [Unmaintained] kopete Reporter: Blindauer Emmanuel <bugs.kde.org>
Component: Main ApplicationAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Blindauer Emmanuel 2003-10-30 18:18:39 UTC 
Version:            (using KDE KDE 3.1.4)
Installed from:    Compiled From Sources
OS:          Linux

Upgrading from 0.7.2 to 0.8beta, the configuration of an account give me no account configured. but in main windows of kopete, I see my three accounts, inactive. trying to connect them I'm prompted for each password, a give them.
After that, going into configuration of account, I can see my three account.
Comment 1 Olivier Goffart 2003-11-12 18:16:01 UTC 
I guess you mean your account was not in mainwindow the statusbar... this is a know bug and has been fixed.

Are you using KWallet?
If no, that's maybe why your password are not correctly remembered.
Comment 2 Will Stephenson 2003-11-17 16:28:55 UTC 
I think he means that immediately after upgrading, the accounts were not visible in the accounts page of the Configure Kopete dialog.  He could just see them offline in the status bar.  When he connected them he was prompted for a password, and after that they were visible in the accounts page of Configure Kopete.

Manu (if that's your name), is this what you meant?  I expect that because you were upgrading from 0.7.x you will not be able to check to see if this bug is still present.
Comment 3 Blindauer Emmanuel 2003-11-21 18:19:42 UTC 
yes, the accounts were not visible in the account page of the configure dialog, right after upgrading, but present in the status bar.
Comment 4 Olivier Goffart 2003-12-04 21:53:30 UTC 
There is ineed a password problem.
Anyway, the fact that not accounts show up at first start should be fixed.

*** This bug has been marked as a duplicate of 69239 ***