Bug 327303 - Quitting Kontact when the mail component has the focus does not kill the Kontact process
Summary: Quitting Kontact when the mail component has the focus does not kill the Kont...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: mail (show other bugs)
Version: 4.11.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-08 12:02 UTC by sundoulos2
Modified: 2017-01-07 21:27 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sundoulos2 2013-11-08 12:02:34 UTC
When Kontact is running, if any component other than Mail has the focus (Contacts, Calendar, Feeds, Journal, etc.) quitting Kontact kills the Kontact process. If Mail has the focus, quitting makes the window disappear and it looks like the application has stopped. Try to restart Kontact, you get the bouncing cursor but the application never "starts". The only way to restart Kontact is to kill the process and then restart.

Reproducible: Always

Steps to Reproduce:
1. Start Kontact
2. Make sure the Mail activity has the focus
3. Quit (doesn't matter how: Ctrl-Q, File/Quit, Close button.
Actual Results:  
The Kontact process was still listed in the process table. Kontact would not restart, nor did it throw an error message.

Expected Results:  
Quitting Kontact should kill the process regardless of which activity has the focus, allowing it to be restarted.
Comment 1 Denis Kurz 2016-09-24 19:24:58 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 2 Denis Kurz 2017-01-07 21:27:01 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.