Bug 223521

Summary:	at start kontact pops up kwallet window under other windows
Product:	[Applications] kontact	Reporter:	p92
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description p92 2010-01-20 03:32:10 UTC

Version:           4.3.4 (using KDE 4.3.4)
OS:                Linux
Installed from:    Ubuntu Packages

I have several email accounts in pop3 and one in imap. For each of theses accounts the password is kept in kwallet. kwallet if protected by a main password.

To reproduce :
- start kontact
- kontact starts kmail 
- kmail requests the accounts passwords 
- kwallet launches a window to get the master password of the wallet 

EXPECTED: the kwallet window pops up above all other desktop windows to be noticed by the user.

BUT the kwallet window is under all other windows on the desktop so is only visible on the taskbar. This can confuse a user to think that kontact cannot start.

Comment 1 p92 2010-02-16 17:36:03 UTC

Still true with :

kwallet Version 1.5
Utilisation de la plate-forme de développement de KDE 4.4.00 (KDE 4.4.0)

and

Qt: 4.6.1
KDE Development Platform: 4.4.00 (KDE 4.4.0)
KMail: 1.13.0

Comment 2 Christophe Marin 2010-03-28 23:19:46 UTC

Do you have the same issue if you start KMail instead of Kontact ?

Comment 3 p92 2010-03-29 00:28:42 UTC

yes same behaviour when started kmail alone.

I add that at kontact or kmail startup I also see a kde notification poping up asking me to switch to kwallet window. This can help, but notifications don't stay up forever and can be missed.

Comment 4 Denis Kurz 2016-09-24 19:32:14 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 5 Denis Kurz 2017-01-07 22:45:48 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.