Bug 290404 - Password popup below main window
Summary: Password popup below main window
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 1.99.0
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-02 14:58 UTC by Pol
Modified: 2017-01-07 22:38 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Pol 2012-01-02 14:58:14 UTC 
Version:           1.99.0 (using KDE 4.7.2) 
OS:                Linux

POP accounts which prompt for password do pop up a password fill window, but this is hidden below the other windows, so users may wait ignorant of their fate for a few eons, then they kill KMail and say it's broken.

Reproducible: Always

Steps to Reproduce:
Create a POP account, check mail


Expected Results:  
pop the password window at the top level. Possibly dim the main window.

OS: Linux (i686) release 3.1.0-1.2-desktop
Compiler: gcc
Comment 1 Sergey Y. Afonin 2012-01-10 06:04:36 UTC 
This is actual for imap-accaunt also (I use KDE 4.7.4).
Comment 2 Laurent Montel 2012-01-12 11:21:11 UTC 
I confirm it. But it's an agent so not easy to make it modal to kmail
Comment 3 Florent Becker 2012-05-23 09:15:19 UTC 
Please raise it but do not make it modal. The password for one account is quite likely to be in an email received on another account, which should be accessible without closing the pop password dialog.
Comment 4 Denis Kurz 2016-09-24 18:05:05 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 kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 22:38:55 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.