Red Hat Bugzilla – Bug 212782
wine versions newer than 0.9.22 don't work
Last modified: 2007-11-30 17:11:46 EST
Description of problem:
The last Wine version that worked for me was 0.9.22 (which has just been removed
from the main Extras repository). 0.9.23 and 0.9.24 hang forever when I attempt
to run any application, including builtin applications like winecfg.
Version-Release number of selected component (if applicable):
Run winecfg, or any of the other builtin Wine apps, or any actual Windows executable
The application gets as far as displaying an empty window (just a titlebar and
frame) and then hangs
Application starts normally
Attached are strace -ff outputs from wine 0.9.22 (which works) and 0.9.23 (which
hangs) I hope these are useful in determining where the hang occurs
Created attachment 139655 [details]
strace -ff outputs
Could you please check which wine packages you have installed and if not install
the wine meta package so you are not missing anything important. After that
please go to your home directory and mave the ~/.wine folder somewhere else and
make a fresh start with wineprefixcreate and try this again.
I have the wine metapackage and all its dependencies installed. Deleting and
recreating ~/.wine/ makes no difference.
Have the same problem on fc6 with wine 0.9.23.
Someone find kill all scim related processes and then start winecfg could
circumvent the problem.
I can confirm that. If I disable SCIM (rename ~/.xinput.d/, log out, log back
in) then Wine starts normally.
I have also had the same problem since Wine 0.9.23. I live in Japan and need
SCIM for Japanese language input. Wine was working fine in it up to version
0.9.22. After that Wine hangs. However if I disable SCIM log out and then back
in again, Wine works fine. I am now using Wine version 0.9.24.
This is cause by a bug in x... see external bugzilla references and recent posts
on the wine list about it... closing as upstream.
Hi Andreas, could you post the "external bugzilla references and recent posts
on the wine list" link here? So, I could apply the patch. Thanks.
Just look below the posts =) There you can find that it is bug #1182 @