Bug 187881 - Force Quit Dialog won't go away
Summary: Force Quit Dialog won't go away
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel   
(Show other bugs)
Version: 5
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-04-04 09:24 UTC by teamwassily
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-20 19:22:47 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description teamwassily 2006-04-04 09:24:07 UTC
Description of problem:
Okay, Firefox slowed my system down to a crawl and I'm only using the Firefox
that came with FC5.  No extensions or themes added.  So Firefox slowed to a
crawl as usual, and this time I was prepared with the 'Force Quit' panel
available at the top of my Gnome environment.  I clicked on it, things were slow
and finally killed the Firefox application.

Now the Force Quit dialog remains in the middle of the screen.  It won't go
away.  All it says is 'Click on a window to force the application to quit.  To
cancel press <ESC>.'

I've removed the Force Quit panel from the top bar and the dialog is still there.

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

How reproducible:
First time.

Steps to Reproduce:
1.Wait till Firefox slows system to a crawl.
2.Click on the 'Force Quit' applet
3.kill Firefox but leave behind the dialog.
Actual results:
The dialog is still bothering me.  I'm going to have to log out to get rid of it.

Expected results:
The dialog should go away, either with an <ESC> or at the end of it's use.

Additional info:

Comment 1 Ray Strode [halfline] 2007-08-20 19:22:47 UTC
seems to work okay now.  I'm going to close this WORKSFORME, but feel free to
reopen if you're still encountering problems.

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