Unity "quit" button doesn't do anything when Wine application is frozen

Bug #1297150 reported by Scott Ritchie on 2014-03-25
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Unity
Incomplete
Undecided
Unassigned
unity (Ubuntu)
Undecided
Unassigned
wine1.6 (Ubuntu)
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.

shankao (shankao) on 2014-03-25
Changed in wine1.6 (Ubuntu):
status: New → Confirmed
Scott Ritchie (scottritchie) wrote :

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.

Changed in wine1.6 (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged

I'm not sure whether this is a bug in Unity...

When launching a wine application here, then killall -STOP it.exe, the window freezes and when trying to close it the unity force-quit dialog shows up as it happens with other applications. And it also seems to do what is expected.

Changed in unity (Ubuntu):
status: New → Incomplete
Changed in unity:
status: New → Incomplete
Scott Ritchie (scottritchie) wrote :

Don't try it with a signal stopped process, try it with an actual hanging process.

Is there anything we can use to reproduce this in an easy way?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers