Launcher - Quit does not actually quit applications
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ayatana Design |
Fix Committed
|
Medium
|
John Lea | ||
One Hundred Papercuts |
Fix Released
|
Medium
|
Unassigned | ||
Unity |
Won't Fix
|
Medium
|
Unassigned | ||
rhythmbox (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
This bug report is about the Quit option listed under the context menu for all running programs in the Unity shell.
I will start with examples:
* Choosing Quit with Rhythmbox will close the main window, but the process continues to run. (The indicator provides a duplicate Quit option that does the right thing, but even if that was merged with the existing Quit option it would not be a sustainable solution).
* I have Dropbox running in the background, and Unity has cleverly added it to the launcher panel with its indicator menu available. Choosing Quit does nothing, because Dropbox is a daemon with no toplevel windows.
From the looks of it, Unity is just closing every window attached to the application's process and wrongly assumes this will cause it to quit. In fact, that often does not happen, and it is a very strange, semantically unclear behaviour.
Desired solution:
- Do the right thing by sending the _process_ a QUIT signal. If a GUI app doesn't handle that signal properly, that is its problem and it should be fixed there.
Related branches
description: | updated |
Changed in unity: | |
milestone: | 2010-09-02 → 2010-09-16 |
Changed in unity: | |
milestone: | 2010-09-16 → backlog |
Changed in unity: | |
milestone: | backlog → none |
assignee: | Gord Allott (gordallott) → nobody |
description: | updated |
Changed in ayatana-design: | |
assignee: | nobody → John Lea (johnlea) |
importance: | Undecided → Low |
status: | New → Fix Committed |
Changed in unity: | |
status: | Opinion → Confirmed |
Changed in unity (Ubuntu): | |
status: | New → Confirmed |
Changed in unity (Ubuntu): | |
importance: | Undecided → Low |
tags: | added: udo |
tags: | added: udp |
Changed in ayatana-design: | |
status: | Fix Committed → Triaged |
Changed in unity: | |
assignee: | nobody → Jason Smith (jassmith) |
Changed in ayatana-design: | |
status: | Triaged → Fix Committed |
Changed in ayatana-design: | |
importance: | Low → High |
summary: |
- Quit does not actually quit applications + Launcher - Quit does not actually quit applications |
Changed in unity: | |
status: | Confirmed → Triaged |
Changed in unity (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in unity: | |
importance: | Low → Medium |
assignee: | Jason Smith (jassmith) → nobody |
Changed in unity (Ubuntu): | |
importance: | Low → Medium |
Changed in ayatana-design: | |
importance: | High → Medium |
Changed in hundredpapercuts: | |
status: | New → Triaged |
milestone: | none → raring-round-3 |
assignee: | nobody → Papercuts Ninja (papercuts-ninja) |
importance: | Undecided → Medium |
Changed in hundredpapercuts: | |
milestone: | none → papercuts-s-unity |
tags: | added: trusty |
Changed in hundredpapercuts: | |
assignee: | Papercuts Ninjas (papercuts-ninja) → nobody |
tags: | added: rls-w-incoming |
tags: |
added: rls-x-incoming removed: rls-w-incoming |
This makes sense to me. We need to be careful about quicklist options when there are no windows attached to the application, but we also need to make sure we don't leave users confused as to why they can't get rid of an icon.