Bug#447197: X freeze when starting wine
Sylvain Beucler
Version: 0.9.44-1
Severity: important
When I run a .exe using wine, X freezes completely:
- mouse is frozen
- graphical output (eg the Gnome xload-style CPU monitor applet) freezes
- capslock and numlock don't respond
- even sound (eg xmms) stops after a few seconds
- Ctrl+Alt+FX and Ctrl+Alt+Backspace do not work
however
- SSH still works
- remote top shows 99% CPU is used by wine
- problem can be solved without rebooting by remote kill -9 on the .exe - everything is back to normal after that.
Cross-compiled (mingw) "hello world" app do not freeze; possibly this only affects GUIs.
"winecfg" freezes as well.
Problem persists after removing ~/.wine
Possibly related bug reports:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/149609
http://groups.google.com/group/comp.emulators.ms-windows.wine/browse_thread/thread/b9cdb8a07cd17814/
Output looks like:
$ winecfg
Invoking /usr/lib/wine/wine.bin winecfg.exe ...
wine: Unhandled page fault on read access to 0x00000348 at address 0x7e1fb734 (thread 0009), starting debugger...
Can't attach process 0008: error 5
/usr/bin/wine: line 396: 30481 Processus arrêté $WINEBIN/$WINE_BIN_NAME "$@"
Wine failed with return code 137
Processus arrêté
~/.xsession-errors do not get anything.
This appeared since I upgraded from Etch to Lenny around 1 or 2 weeks ago.
Please advice :)
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-2-k7 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages wine depends on:
ii libwine-alsa 0.9.44-1 Windows API Implementation (ALSA S
ii libwine-capi 0.9.44-1 Windows API Implementation (ISDN M
ii libwine-cms 0.9.44-1 Windows API Implementation (Color
ii libwine-gl 0.9.44-1 Windows API Implementation (OpenGL
ii libwine-gphoto2 0.9.44-1 Windows API Implementation (Camera
ii libwine-ldap 0.9.44-1 Windows API Implementation (LDAP M
ii libwine-print 0.9.44-1 Windows API Implementation (Printi
ii libwine-sane 0.9.44-1 Windows API Implementation (Scanne
ii wine-bin 0.9.44-1 Windows API Implementation (Binary
ii wine-utils 0.9.44-1 Windows API Implementation (Utilit
Versions of packages wine recommends:
pn msttcorefonts <none> (no description available)
-- no debconf information
Sylvain Beucler
Any idea on what I can investigate to track the origin of this issue?
I can't use wine at all.
--
Sylvain
Ove Kaaven
> No improvement when using 0.9.48 from the winehq.org Debian package :/
>
> Any idea on what I can investigate to track the origin of this issue?
> I can't use wine at all.
It's perhaps the same as #449202?
You should mention which X drivers you're using. Perhaps the buggy ATI
FireGL drivers, for example? Also mention whether you're using a
compositing window manager.
I'd suggest setting the WINEDEBUG environment variable to
"+seh,+tid,+win,+x11drv,+font,+opengl" or something, and capture the
output. It should give some hint about what Wine is doing when stuff
crashes. Also consider looking into /var/log/Xorg.0.log or whatever if
the X server crashes. Problems with X on Wine startup are usually
related to one of 1) running out of RAM, 2) loading corrupt fonts, 3)
unstable OpenGL drivers
After all, a (first-time) Wine startup involves enumerating and
calculating the metrics of all available fonts, testing available X
server features (including Render and OpenGL), and loading large amounts
of graphics.
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sylvain Beucler
I run an up-to-date Lenny.
Cheers and happy new year,
--
Sylvain