Subject: Re: [Kopete-devel]  New: saving passwrd does not work

Do you have KWallet enabled or are you using unencrypted password in the 
Kopete config file instead?

In the former case, could you check using the KWallet GUI (it's in kdeutils) 
whether there are any passwords stored? In the latter case, please check 
~/.kde/share/config/kopeterc and see if your password is listed.

If Kopete doesn't shutdown properly it might never get saved. A workaround 
would be then to quit Kopete before logging out of KDE and restart it again. 
This should trigger saving all config settings.

Subject: Re:  saving passwrd does not work

>Do you have KWallet enabled or are you using unencrypted password in the
>Kopete config file instead?
Kwallet not enable.
This morning I started my computer read your mail and checked the rc file 
for passwds. The passwds were in the kopeterc (encrypted). Started kopete 
and pressed connect. it worked without prompts for passwds. So that works 
well out of the blue. BUT I tried a couple of things that will interest you. 
It seems that I have to quit kopete three times before the passwd is saved 
in the rc:

I quit kopete, then:
I removed the kopeterc in .kde/share/config/ to regenerate the problem.
Start kopete again. It pops up the Configure dialog. So I added a new 
account (ICQ) using the wizard
-- typed the UIN in the uin field
-- Remember passwd was checked by default so didn't touch that
-- typed passwd in passwd field
-- checked the Connect automatically at startup checkbox
Pressed next to finish wizard.
Now I was presented again with the Configure dialog. MY NEW ACCOUNT DOES NOT 
APPEAR in this dialog although the account is created. Also the icq flower 
icon is shown lower right in the main kopete screen!! Nevertheless I press 
ok.  A new kopeterc is created:

[Account_ICQProtocol_4300522]
AccountId=4300522
AutoConnect=false
Protocol=ICQProtocol
RememberPassword=false

[Away Messages]
Busy=Sorry, I'm busy right now
Gone=I'm gone right now, but I'll be back later
Titles=Busy,Gone

[Plugins]
kopete_icqEnabled=true

As you see there are two errors here!

I continue kopete. Now two things go wrong:
- the icq account does not start automatically (minor issue) so I press the 
connect button
- icq does login so it remembered my passwrd
Now I quit kopete (really quit, not just lowering window)
The rc file is updated ( a lot more info is added to the above file). Two 
interesting lines:
[Account_ICQProtocol_4300522]
AutoConnect=true
RememberPassword=false

I restart kopete. Now :
- no automatic connection ( although AutoConnect in rc file is true!!) AND
- when pressing the connect button kopete presents small gui to type in 
passwd and ask to connect automatically future sessions
So I type my passwd again and press connect button. ICQ connects.

The rc is not updated ( well at least RememberPassword=false)
I quit kopete

Now the rc file is updated and RememberPassword=true and my passwd is added

I restart kopete
- no automatic connection
- YES PASSWD IS REMEMBERED!! So when connect button is pressed kopete 
connects to icq.

Pfew a long mail. In my opinion kopete should save the passwd in the rc 
already the first when the account is created. Could it be that although in 
the gui the "Save Passwd" checkbox is checked but in the code the 
RememberPAsswd flag is set to false (or something like that). I'v only 
written very small programs in QT/KDE and I am not a c++ pro, but maybe I'll 
have a look at the code sometimes...

I'll do some more testing on the MSN protocol ( I do not have other like 
jabber/yahoo etc )
Also You have my UIN now (look above) so you might try to contact me through 
icq...

Regards Kees

_________________________________________________________________
Need a shot of Hank Williams or Patsy Cline?  The classic country stars are 
always singing on MSN Radio Plus.  Try one month free!  
http://join.msn.com/?page=offers/premiumradio

Subject: Re:  saving passwrd does not work

Here an update on the previous mail which concerned the saving of passwds 
when creating an ICQ account.

This mail concerns with creating an MSN account. A few issues different from 
the previous mail (concerning icq account) are reported here.

Again:
quit kopete, remove kopeterc, start kopete
1) kopete prompts COnfigure dialog. I started "New " wizard and selects MSN 
protocol and press next
Now at this point the kopete main window inserts a msn icon in the lower 
right corner. This is too early!! When creating icq account the icon is 
inserted much later at the end of the wizard.
2) I proceed by giving my MSN id and passwrd and end the wizard.
Now AGAIN a MSN icon is added in the lower right corner of the main kopete 
window. There are two icons!!!!!! ALSO like when adding icq account in the 
Configure dialog the newly created account is not visible and the rc-file is 
not updated correctly:
AutoConnect=false  #should be true since I selected this option in the 
wizard
Protocol=MSNProtocol
RememberPassword=false  # should be true

3) Just like in the icq case after quiting and restarting icq I have to 
press connect to connect and I am presented with a small dialog prompting 
for passwd and remember passwd and autoconnect. HERE IS AN OTHER (SMALL) 
DIFFERENCE WITH THE ICQ account: the auto connect checkbox is unchecked by 
default. For icq account it is checked by default.  (Inheritance issue??)

Concluding: msn icon is inserted twice in kopete main window and there is a 
small inconsistency with the "Passwd Required" dialog for different 
protocols.

Groeten,

Kees van wijk
cvanwijk@hotmail.com

_________________________________________________________________
Need a shot of Hank Williams or Patsy Cline?  The classic country stars are 
always singing on MSN Radio Plus.  Try one month free!  
http://join.msn.com/?page=offers/premiumradio

Subject: Re: [Kopete-devel]  saving passwrd does not work

That was a lot of text to read through :)

Summarizing, you see the following issues, right?

1. The RememberPassword flag is often not correctly written to disk
2. The default value for RememberPassword is inconsistent across protocols
3. The account data isn't written to disk when it changes, but only when
   exiting or otherwise saving the account config.
4. MSN somehow inserts two instead of one icon for a new account

Anything I missed?

As for #3, that one is known, and is at least partially caused by the XML that 
we used for the account config in the past. At that time the overhead of 
saving immediately was too big, so both the contact list and the account 
config were only written on exit. I hope to address that after KDE 3.2, I 
don't expect the patches suitable for now given that 3.2 is pretty close now.

The other 3 issues are not known to me, but with your explanantion they should 
be fairly easy to reproduce (didn't try yet). First I want to know that I 
understood everything correctly :)

Subject: Re:  saving passwrd does not work

>Summarizing, you see the following issues, right?
>
>1. The RememberPassword flag is often not correctly written to disk
>2. The default value for RememberPassword is inconsistent across protocols
>3. The account data isn't written to disk when it changes, but only when
>    exiting or otherwise saving the account config.
>4. MSN somehow inserts two instead of one icon for a new account
Ad 1) YES: RememberPassword is NOT writen to disk correctly when creating 
new account and also NOT correctly when quiting kopete for FIRST time. 
Starting kopete a second time and connect and kopete will popup a dialog to 
give passwd and query save passwd for previous created account. Closing this 
dialog and passwd is NOT saved (correctly). Quiting kopete and passwd IS 
saved correctly!!
Ad 2) NO, it is the default value for AutoConnect which is inconsitent
Ad 3) NO, i think it IS written on change but RememberPassword is set false 
instead of true!!
Ad 4) YES but only when there are not yet any accounts configured. (move 
your kopeterc and try!)

>Anything I missed?
You missed one thing. After finishing the "New Account" wizard the Configure 
dialog is in front again. BUT the new acount is not added to the list of 
already existing accounts visible in this dialog.


>I hope to address that after KDE 3.2, I don't expect the patches suitable 
>for now given that 3.2 is pretty close now.
Sure, besides that, eventually after running kopete for the 3th time 
passwrds are saved correctly

Regards,
Kees

_________________________________________________________________
Share holiday photos without swamping your Inbox.  Get MSN Extra Storage 
now!  http://join.msn.com/?PAGE=features/es

Subject: Re: [Kopete-devel]  saving passwrd does not work       
  

If this helps, i got the same problem with gadu recently. Have just tested 
it out. Gadu saves password when new account is created. Tested without 
wallet. I will have a closer look from my site.

Subject: Re: [Kopete-devel]  saving passwrd does not work

On Saturday 29 November 2003 13:25, Kees van Wijk wrote:
> >Anything I missed?
>
> You missed one thing. After finishing the "New Account" wizard the
> Configure dialog is in front again. BUT the new acount is not added to the
> list of already existing accounts visible in this dialog.

Are you using CVS or a packaged snapshot or beta?  I thought I had fixed this 
a couple of weeks ago.

Subject: Re:  saving passwrd does not work

> > You missed one thing. After finishing the "New Account" wizard the
> > Configure dialog is in front again. BUT the new acount is not added to 
>the
> > list of already existing accounts visible in this dialog.
>
>Are you using CVS or a packaged snapshot or beta?  I thought I had fixed 
>this
>a couple of weeks ago.
I'm using kde3.2 which has been installed on my gentoo system by emerging 
the kdenetwork ebuild. The version of kopete is 0.7.93. So indeed a packaged 
snapshot beta.

Kees

_________________________________________________________________
online games and music with a high-speed Internet connection!  Prices start 
at less than $1 a day average.  https://broadband.msn.com (Prices may vary 
by service area.)

*** Bug 66919 has been marked as a duplicate of this bug. ***

I'm using KDE 3.2 CVS 19 dec. 16utc (according the SuSE packagers).

I think this problem is related:

- First I updated from Kopete 0.7.3 to 0.7.4 to 0.8 beta 1 and than to the Kopete version in KDE 3.2 beta 2. All worked fine, no problems. After when I updated to the above listed CVS version, the following problem occured:

- When starting kopete, my ICQ password was gone, a messagebox complained about the fact I did not store any password. MSN didn't complain, but no password was there. MSN came online, couldn't check if that worked, cause all mu budies were offline. Jabber gave a 'Not Authorized' message and also did not store a password. Yahoo was the only only really asking for a password, but I didnt bother to test that one further (only one yahoo-buddy). I also was not able to change the account preferences (incl. passwords). They were not saved. 

-Kwallet had all the passwords stored, except ICQ and Yahoo. I fillid in the ICQ password in the Kwallet manager and reconected ICQ, the password box come up and after filling in the pw, icq connected well. After restarting Kopete, the problem reappeared, but the icq pw was still in Kwallet.

-I checked the kopeterc file and I noticed that there were 2 entries for icq, msn, jabber and yahoo. I closed kopete, removed the double entries from the kopeterc and restarted kopete, but still the same problems.

-I removed all accounts in kopete, closed the app, checked the kopeterc file for leftovers (there were not, removed all Kopete entries from Kwallet )incl. the 'always allow') and restarted kopete. I readded my icq and msn account and followed the instruction to store it in kwallet. Again the same problem.

- I did the last step all over, but I did let kopete not store the passwords in kwallet. All went fine, no problems since. Hoeray!

Hopefully this will help you.

Cheers,

Jeroen

Jeroen, I think you have a very unfortunate CVS checkout. There was a bug in KWallet that made a method always return true when in fact it should return false. At the same time Kopete had a bug that made KWallet actually work correctly because we had the logic reverted as well :)

Now the problem is that the KWallet bug got fixed around your snapshot, but only a couple of days later Kopete got the fix, making the two get out of sync.

If you can live without the wallet, just don't use it until your next update. Once you update to a more recent kdelibs _AND_ kopete, please report back to us, as the problem is supposed to be fixed now :)

Martijn

Ironically, my Kopete and kdelibs are a few days old, and forgets passwords when the wallet is DISABLED.

also seen in KDE 3.1

See patch in bug 72490. I found the cause.

Martijn


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

Kopete 0.8.90 CVS >=20040123 does not retain passwords at all.
Kwallet disabled,
Kopete shows Remember Passwords as checked, but NO
encrypted password line.
Also, Kopete quits and abends with a Signal 11 which I listing here since it MAY be related if the config files are not written out after passwords are input.
-----------------------
My system KDE 3.2.90 via CVS updated as of Feb 4, 2004
Kernel 2.6.2 with Supermount extension
OS Slackware 9.1 with a ton of updates!

Backrace:
[New Thread 16384 (LWP 6863)]
0x418715c9 in waitpid () from /lib/libpthread.so.0
#0  0x418715c9 in waitpid () from /lib/libpthread.so.0
#1  0x40f20737 in KCrash::defaultCrashHandler(int) ()
   from /mnt/src/src/kde/lib/libkdecore.so.4
#2  0x4186fc45 in __pthread_sighandler () from /lib/libpthread.so.0
#3  <signal handler called>
#4  0x400be059 in KopeteAccount::protocol() const ()
   from /mnt/src/src/kde/lib/libkopete.so.1
#5  0x400bae17 in KopeteAccountManager::accounts(KopeteProtocol const*) ()
   from /mnt/src/src/kde/lib/libkopete.so.1
#6  0x400838d5 in KopeteProtocol::~KopeteProtocol() ()
   from /mnt/src/src/kde/lib/libkopete.so.1
#7  0x426ba87e in AIMProtocol::~AIMProtocol() ()
   from /mnt/src/src/kde/lib/kde3/kopete_aim.so
#8  0x412f5883 in QObject::event(QEvent*) ()
   from /usr/lib/qt-3.2.1/lib/libqt-mt.so.3
#9  0x4129d035 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/qt-3.2.1/lib/libqt-mt.so.3
#10 0x4129c6eb in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/qt-3.2.1/lib/libqt-mt.so.3
#11 0x40e847d5 in KApplication::notify(QObject*, QEvent*) ()
   from /mnt/src/src/kde/lib/libkdecore.so.4
#12 0x4129dde8 in QApplication::sendPostedEvents(QObject*, int) ()
   from /usr/lib/qt-3.2.1/lib/libqt-mt.so.3
#13 0x4129dc68 in QApplication::sendPostedEvents() ()
   from /usr/lib/qt-3.2.1/lib/libqt-mt.so.3
#14 0x4124ae4b in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/qt-3.2.1/lib/libqt-mt.so.3
#15 0x412b0276 in QEventLoop::enterLoop() ()
   from /usr/lib/qt-3.2.1/lib/libqt-mt.so.3
#16 0x412b0118 in QEventLoop::exec() ()
   from /usr/lib/qt-3.2.1/lib/libqt-mt.so.3
#17 0x4129d281 in QApplication::exec() ()
   from /usr/lib/qt-3.2.1/lib/libqt-mt.so.3
#18 0x08061ae0 in main ()
#19 0x419bcd06 in __libc_start_main () from /lib/libc.so.6

Regards