| 2011-04-15 16:32:39 |
Matthew Paul Thomas |
bug |
|
|
added bug |
| 2011-04-15 16:32:48 |
Matthew Paul Thomas |
summary |
No easy way to force-quit a program that has no visible windows |
No easy way to force-quit a program that has no visible window frames |
|
| 2011-04-15 16:33:23 |
Matthew Paul Thomas |
description |
Ubuntu 4.10, 5.04, 5.10, 6.06, 6.10, 7.04, 7.10, 8.04, 8.10, 9.04, 9.10, 10.04, 10.10, Natty beta 2
Ubuntu has never had an easy and reliable way of shutting down a badly behaving program.
The Task Manager exists, but it was always slow to find in Ubuntu, and it is even slower to find in Unity.
The window manager puts up a dialog if the program for a window you try to close doesn't respond, but that works only if (a) the program you need to shut down is one that has a window open, (b) the window even has a border, and (c) the window is not of a type that floats on top of the task manager. (That is, this is not a duplicate of bug 698031.) For example, it won't help you restart a frozen Unity launcher.
There needs to be a way to shut down any application, and secondarily any process, regardless of whether or how it uses windows, and regardless of how much CPU it was using before you invoked the interface. Ideally, for system processes the UI should reflect that they will be restarted rather than ended permanently.
It may save time to design the fix for bug 85170 at the same time as this bug. |
Ubuntu 4.10, 5.04, 5.10, 6.06, 6.10, 7.04, 7.10, 8.04, 8.10, 9.04, 9.10, 10.04, 10.10, Natty beta 2
Ubuntu has never had an easy and reliable way of shutting down a badly behaving program.
The System Monitor exists, but it was always slow to find in Ubuntu, and it is even slower to find in Unity.
The window manager puts up a dialog if the program for a window you try to close doesn't respond, but that works only if (a) the program you need to shut down is one that has a window open, (b) the window even has a border, and (c) the window is not of a type that floats on top of the task manager. (That is, this is not a duplicate of bug 698031.) For example, it won't help you restart a frozen Unity launcher.
There needs to be a way to shut down any application, and secondarily any process, regardless of whether or how it uses windows, and regardless of how much CPU it was using before you invoked the interface. Ideally, for system processes the UI should reflect that they will be restarted rather than ended permanently.
It may save time to design the fix for bug 85170 at the same time as this bug. |
|
| 2011-04-15 16:36:17 |
Matthew Paul Thomas |
description |
Ubuntu 4.10, 5.04, 5.10, 6.06, 6.10, 7.04, 7.10, 8.04, 8.10, 9.04, 9.10, 10.04, 10.10, Natty beta 2
Ubuntu has never had an easy and reliable way of shutting down a badly behaving program.
The System Monitor exists, but it was always slow to find in Ubuntu, and it is even slower to find in Unity.
The window manager puts up a dialog if the program for a window you try to close doesn't respond, but that works only if (a) the program you need to shut down is one that has a window open, (b) the window even has a border, and (c) the window is not of a type that floats on top of the task manager. (That is, this is not a duplicate of bug 698031.) For example, it won't help you restart a frozen Unity launcher.
There needs to be a way to shut down any application, and secondarily any process, regardless of whether or how it uses windows, and regardless of how much CPU it was using before you invoked the interface. Ideally, for system processes the UI should reflect that they will be restarted rather than ended permanently.
It may save time to design the fix for bug 85170 at the same time as this bug. |
Ubuntu 4.10, 5.04, 5.10, 6.06, 6.10, 7.04, 7.10, 8.04, 8.10, 9.04, 9.10, 10.04, 10.10, Natty beta 2
Ubuntu has never had an easy and reliable way of shutting down a badly behaving program.
The System Monitor exists, but it was always slow to find in Ubuntu, and it is even slower to find in Unity.
The window manager puts up a dialog if the program for a window you try to close doesn't respond, but that works only if (a) the program you need to shut down is one that has a window open, (b) the window even has a border, and (c) the window is not of a type that floats on top of the task manager. (That is, this is not a duplicate of bug 698031.) For example, it won't help you restart a frozen Unity launcher.
There needs to be a way to shut down any application, and secondarily any process, regardless of whether or how it uses windows, and regardless of how much CPU it was using before you invoked the interface. Ideally, for system processes the UI should reflect that they will be restarted rather than ended permanently.
It may save time to design the fix for bug 85170 at the same time as this bug.
See also: http://brainstorm.ubuntu.com/idea/25861/ |
|
| 2011-04-15 18:45:31 |
Mark Shuttleworth |
ayatana-design: status |
New |
Confirmed |
|
| 2011-04-17 16:35:03 |
Yann Dìnendal |
bug |
|
|
added subscriber Yann Dìnendal |
| 2011-06-07 21:02:57 |
Greg A |
bug |
|
|
added subscriber Greg Auger |
| 2012-05-31 15:19:35 |
Matthew Paul Thomas |
ayatana-design: assignee |
|
Matthew Paul Thomas (mpt) |
|
| 2012-05-31 15:23:38 |
Matthew Paul Thomas |
summary |
No easy way to force-quit a program that has no visible window frames |
No easy way to force closed a program without visible window frames (Force Quit, End Task) |
|
| 2012-05-31 15:23:38 |
Matthew Paul Thomas |
description |
Ubuntu 4.10, 5.04, 5.10, 6.06, 6.10, 7.04, 7.10, 8.04, 8.10, 9.04, 9.10, 10.04, 10.10, Natty beta 2
Ubuntu has never had an easy and reliable way of shutting down a badly behaving program.
The System Monitor exists, but it was always slow to find in Ubuntu, and it is even slower to find in Unity.
The window manager puts up a dialog if the program for a window you try to close doesn't respond, but that works only if (a) the program you need to shut down is one that has a window open, (b) the window even has a border, and (c) the window is not of a type that floats on top of the task manager. (That is, this is not a duplicate of bug 698031.) For example, it won't help you restart a frozen Unity launcher.
There needs to be a way to shut down any application, and secondarily any process, regardless of whether or how it uses windows, and regardless of how much CPU it was using before you invoked the interface. Ideally, for system processes the UI should reflect that they will be restarted rather than ended permanently.
It may save time to design the fix for bug 85170 at the same time as this bug.
See also: http://brainstorm.ubuntu.com/idea/25861/ |
Ubuntu 4.10, 5.04, 5.10, 6.06, 6.10, 7.04, 7.10, 8.04, 8.10, 9.04, 9.10, 10.04, 10.10, 11.04, 11.10, 12.04
1. Launch a full-screen application, such as a game.
2. Have the application hang, or get bogged down using 100% of CPU.
3. Try to get out of the application.
What happens: You can't, unless you are the sort of geek who knows about Fn Ctrl Alt F1 and ps and grep and kill -9.
What should happen:
a. You type a keyboard combo (that isn't overridable by anything, not even a game's X grab).
b. A window appears in front of everything else (no matter what other kinds of window are open).
c. The window lists running applications (by icon and proper name).
d. The window is responsive to your input (no matter how much CPU other programs have been using).
e. You select the application you want to force closed, maybe opt in to submitting an error report, and click a button. (If it was running in someone else's account, you authenticate as an administrator.)
f. The application shuts down.
Ubuntu has never had an easy and reliable way of shutting down a badly behaving program. The System Monitor exists, but it was always slow to find in Ubuntu, it is even slower to find in Unity, and it does not meet any of the bracketed requirements above.
The window manager puts up a dialog if the program for a window you try to close doesn't respond, but that works only if (a) the program you need to shut down is one that has a window open, (b) the window even has a border, and (c) the window is not of a type that floats on top of the task manager. (That is, this is not a duplicate of bug 698031.) For example, it won't help you restart a frozen Unity launcher.
There needs to be a way to shut down any application, and secondarily any process, regardless of whether or how it uses windows, and regardless of how much CPU it was using before you invoked the interface. Ideally, for system processes the UI should reflect that they will be restarted rather than ended permanently.
It may save time to design the fix for bug 85170 at the same time as this bug.
See also: http://brainstorm.ubuntu.com/idea/25861/ |
|
| 2012-05-31 15:26:22 |
Matthew Paul Thomas |
affects |
ayatana-design |
ubuntu |
|
