Unity "quit" button doesn't do anything when Wine application is frozen
Bug #1297150 reported by
Scott Ritchie
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Incomplete
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
wine1.6 (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
A Wine app that freezes up can be in a state where it is unkillable by using the interface. Killing the process in a terminal, or doing a wineserver -k command, can solve the situation, however there is no way to do this within Unity even after repeated "quit" demands.
Changed in wine1.6 (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
I've seen this behavior. Unity should have a way of being more forceful about its kills after an application doesn't respond to quits for a while (or perhaps infer it when the user issues repeated quit commands).
Other operating systems offer to do the equivalent of kill -9 ("Force quit") in similar situations. Wine is smart enough to clean up wineserver if all the application processes are removed this way.