Bug 74769 - After cancelling closure of a konqueror window kwin pops up with unresponsive application message
Summary: After cancelling closure of a konqueror window kwin pops up with unresponsive...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-09 22:12 UTC by Paul Sprakes
Modified: 2004-02-13 15:33 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 Paul Sprakes 2004-02-09 22:12:45 UTC
Version:           3.2.0 (using KDE 3.2 BRANCH >= 20040204, compiled sources)
Compiler:          gcc version 3.3.1
OS:          Linux (i686) release 2.4.22

(Not sure if this is really a kwin bug or not).

A new kwin feature detects when an application has become unresponsive and will ask the user if they wish to terminate the application.

If Konqueror has more then one tab open you will be asked to confirm the close. If you cancel it and wait a few moments you will get kwin telling you that konq has become unresponsive (when it hasn't).

When the user cancels the closure, konq should let kwin know about this so it doesn't display the warning box.
Comment 1 Andreas Leuner 2004-02-10 10:49:25 UTC
>If you cancel it and wait a few moments you will get kwin 
>telling you that konq has become unresponsive (when it hasn't). 
If you do _not_ cancel the confirmation dialog and just ignore it for a few seconds, kwin will also show the termination dialog.

The same seems to be true for every other application that displays a confirmation dialog upon window close. KEdit, Kate and Konsole are also candidates for this.
It seems that this is not specific to konqueror.

Non KDE applications like mozilla (1.6 in my case) or netbeans do _not_ show this behavior however.
Comment 2 Lubos Lunak 2004-02-13 15:33:04 UTC
*** Bug has been marked as fixed ***.