Bug 304458 - When I click on "New message..." in the notification area, the Compose window opens in minimised state
Summary: When I click on "New message..." in the notification area, the Compose window...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8.3
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-02 19:00 UTC by Christian
Modified: 2017-01-07 22:08 UTC (History)
1 user (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 Christian 2012-08-02 19:00:48 UTC
When I do not need KMail, I usually close the Kmail application so that only its icon in the notification area is still shown. Then I use that icon's right-click menu to open a New Message composer. However, it opens the Compose window to appear in minimised state. It should open in normal window state.
Comment 1 Laurent Montel 2012-08-31 10:47:32 UTC
not it's not minimize but it's right it's not the first application and it's normal.
Comment 2 Christian 2012-08-31 15:04:08 UTC
Dear Laurent! Maybe it's "right" for you, but it's not normal. When I click on something because I want a window to appear, then the window should appear in such a way that I don't have to click again to make it actually show up on my screen.
If you think this is "normal" for Kontact, then the bug is maybe in the Window manager? Could you move it to the appropriate application that is causing this behviour? Thanks!
Comment 3 Denis Kurz 2016-09-24 18:09:20 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 4 Denis Kurz 2017-01-07 22:08:30 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.