Bug 455385 - Closing KWrite in GNOME brings up the 'application is not responding'-dialogue
Closing KWrite in GNOME brings up the 'application is not responding'-dialogue
Product: Fedora
Classification: Fedora
Component: kdebase (Show other bugs)
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-07-15 05:46 EDT by Tobias Vogel
Modified: 2009-06-07 19:26 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-06-07 19:26:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tobias Vogel 2008-07-15 05:46:55 EDT
Description of problem:

Closing KWrite via the "X" in the top-right position of the window, shows up the
normal "Save / Discard / Cancel" dialogue, but immediately the gnome
'application is not responding' pops up. 

Version-Release number of selected component (if applicable):

How reproducible:

Close KWrite via the "X".

Steps to Reproduce:
1. Start KWrite
2. Modify Document
3. Don't save
4. Close KWrite
Actual results:

'Application ist not responding' dialogue.

Expected results:

"Save / Discard / Cancel" dialogue
Comment 1 Kevin Kofler 2008-07-15 09:34:54 EDT
The question is: is it KWrite's fault or is it GNOME's (Metacity's?) fault?
Comment 2 Steven M. Parrish 2008-07-17 14:46:03 EDT
My feeling is that its a GNOME issue, but I'll assign it to Than and let him
make the call
Comment 3 Steven M. Parrish 2008-09-28 18:37:24 EDT
Comment 4 Steven M. Parrish 2009-02-06 12:19:40 EST
Is this still an issue?
Comment 5 Steven M. Parrish 2009-06-07 19:26:33 EDT
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.


Steven M. Parrish - KDE Triage Master
Fedora Bugzappers volunteer triage team

Note You need to log in before you can comment on or make changes to this bug.