Bug 353824 - Kontact window continues grey after closing modal dialogue
Summary: Kontact window continues grey after closing modal dialogue
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-12 11:15 UTC by Mark Stanton
Modified: 2018-01-31 16:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Stanton 2015-10-12 11:15:39 UTC
Version 4.14.9

On opening the "configure Kontact" dialogue the rest of the app is greyed out behind it, which is fine, it's a modal dialogue.
However, on closing the dialogue the app is *still* greyed out. It functions as usual but all grey.
Opening another  dialogue, like a bug reporting tool, clears the problem.

Reproducible: Always

Steps to Reproduce:
1. I opened the "configure KMail" window (to set up accounts).
2. Created a new account, but cancelled rather than saving
3. Close configure dialogue

Actual Results:  
The app window remains very grey. It functions correctly. Switching between various "sub-apps" (contact, mail, calendar) doesn't clear the problem.

Expected Results:  
The main window should be restored to normal contrast.
Comment 1 Denis Kurz 2017-06-23 20:17:04 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:53:44 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.