Bug 350699 - Notification prevents minimize to tray of Kmail (envelope icon)
Summary: Notification prevents minimize to tray of Kmail (envelope icon)
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.14.7
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-28 09:38 UTC by Sebastian Gruener
Modified: 2018-01-31 16:50 UTC (History)
2 users (show)

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 Sebastian Gruener 2015-07-28 09:38:36 UTC
Once a notification pops up, I can't minimize Kmail to the tray, by clicking on the envelope icon.
Kmail-Version is 4.14.10

Reproducible: Always

Steps to Reproduce:
1. Send an e-mail. Wait for the "E-Mail has been sent"-notfication-pop-up
2. While the pop-up-notication is visible, try minimize to tray by clicking on the envelope-icon


Actual Results:  
Unable to minimize. As a workaround, I have to wait till the notification disappears and minimize then.

Expected Results:  
I should be able to minimize, even if the notification is visible.

The bug is just a little inconvenience, but if it happens multiple times a day, this starts to get really annoying.
Comment 1 Martin Klapetek 2015-07-28 09:45:46 UTC
Thanks for the report

This looks more like KMail bug though, notification popups have nothing to do with systray icon clicking.
Comment 2 Denis Kurz 2017-06-23 20:03:31 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.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 oportunity 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 3 Denis Kurz 2018-01-31 16:50:50 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.