Bug 242195

Summary:	KWallet requires authorization every time when kopete starts on boot
Product:	[Unmaintained] kopete	Reporter:	Oleg <qwertier>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	CLOSED WORKSFORME
Severity:	normal	CC:	brian, foss, valir
Priority:	NOR
Version First Reported In:	1.0.0
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Oleg 2010-06-19 20:49:58 UTC

Version:           1.00 (using KDE 4.4.4) 
OS:                Linux

Kopete is set to autostart. When I shutdown my pc it closes automatically.
But it does not work with kwallet properly. KWallet requires shows request that kopete requests access to and on every boot I need to enter my login/password.

When I exit Kopete manually before shutdown, kopete works good, but kwallet switchs on Amarok. And I need to enter my login for it. 
There is 2 probable reasons:
1) On shutdown linux send SIGKILL to all the app. Kopete does not recongnize it correctly. It should catch it and call the same close method as is for "Close..." or "X" button. It is easy to do in Qt - it has special event queue checker.
2) KWallet is the reason. It explains that if close manually Kopete the same occurs for Amarok. 

But for a moment kwallet requires authentification only for amarok and kopete. That is why I'm reporting about the bug here...



Reproducible: Always

Steps to Reproduce:
Simply reboot without closing kopete



OS: Linux Kubuntu 10.04 LTS (x86_64) release 2.6.32-22-generic
Compiler: cc (but wasn't compiled - was used apt-get update to kde4.4.4 from kde-org site)

Comment 1 Christian Reiner 2010-07-05 23:02:41 UTC

I don't see why this is a bug. 

First it is correct that the password is requested to open the wallet after a fresh login / reboot, since the wallet is closed at that time. No way it should be opened without a password ! How anyway ? By storing the password on disk during reboot ?

The strategy after a login is: all applications that require access to a wallet ask for it, the walletmanager fires the authorization dialog for the first applciation in the queue. All other requests are kept back, since one dialog is enough to open the wallet. So in the end it is a question of order and speed in which the applications are started upon login. 

The fact that things change slightly for you most likely depend on either kopete not starting when being closed before logout, this might be because you restore the last session used. Or simply because the order or speed in which the two applications request for opening the wallet. 

Whatever is the case: there is no way around the fact that the wallet has to be opened after login / reboot, triggered first by which application ever.

Comment 2 Brian DeRocher 2011-01-15 15:20:35 UTC

Maybe Oleg didn't explain it right, but there's definitely an issue.  I'm using kwallet 1.5 and Kopete 1.0 (KDE 4.4.5).  Kopete Initial Status is set to Online.  And i have one account marked to include with global connection to my jabber server.

Kopete and Kwallet are restored when i log in.  I get password prompts for both Kwallet and Kopete.  When i open the wallet my Kopete password is in there and it's correct.  To me the bug is in Kopete.

Comment 3 Valentin Rusu 2011-08-30 07:43:04 UTC

Can you confirm that still reproduces in KDE 4.7.1 or master?

Comment 4 Oleg 2011-08-30 07:57:13 UTC

By now, the bug does not reproduce: Kubuntu 11.04, KDE 4.6.5

Comment 5 Valentin Rusu 2011-08-30 08:19:41 UTC

Could you please change it's status to "CLOSED" as "WORKSFORME" then?
If not, I can do it for you.

Comment 6 Oleg 2011-08-30 08:28:51 UTC

sure