Your message dated Fri, 8 Sep 2017 11:02:00 +0200
with message-id <[email protected]>
and subject line Re: wine32: SegFault when run a program require OpenGL/Direct3D
has caused the Debian Bug report #766028,
regarding causes segfaults in wine compiled with bindnow
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
766028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766028
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wine32
Version: 1.6.2-11
Severity: normal
Dear Maintainer,
Running a win32 program which require OpenGL/Direct3D using wine32
will cause segmentation fault happen. This program may be a game
require Direct3D, a testing OpenGL program which only display OpenGL
information, or dxdiag.exe which is a DirectX deagnostic tool
distributed in Debian libwine package.
As dxdiag.exe is common, I use it to discuss below.
With 1.6.2-8, 1.6.2-10 wine32, running below command will not cause
SegFault and GL version can got from wine debug messages:
$ WINEDEBUG=+wgl wine32 dxdiag.exe 2> wine.log
$ grep "GL version" wine.log
trace:wgl:X11DRV_WineGL_InitOpenglInfo GL version :
3.3.0 NVIDIA 340.46.
With 1.6.2-11, 1.6.2-12 wine32, running the same command will cause SegFault:
$ WINEDEBUG=+wgl wine32 dxdiag.exe 2> wine.log
Segmentation fault
$ cat wine.log
Wine cannot find the ncurses library (libncurses.so.5).
fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030
fixme:wbemprox:enum_class_object_Next timeout not supported
Let core can be dumped when SegFault happen, then using gdb I found:
$ gdb wine32 core
...
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7de8ee0a in ?? () from /usr/lib/i386-linux-gnu/libGL.so.1
(gdb)
/usr/lib/i386-linux-gnu/libGL.so.1 is finally soft link to
/usr/lib/i386-linux-gnu/nvidia/current/libGL.so.340.46 which is
provide by libgl1-nvidia-glx:i386 package.
Next I try strace and found something interesting. The same above
command will NOT cause SegFault even with 1.6.2-11, 1.6.2-12 wine32:
$ WINEDEBUG=+wgl strace -f -o strace.log wine32 dxdiag.exe 2> wine.log
$ grep "GL version" wine.log trace:wgl:X11DRV_WineGL_InitOpenglInfo
GL version : 3.3.0 NVIDIA 340.46.
It is something wrong with wine32? Though from changelog, it seems
like no change in i386 when upgrade from 1.6.2-10 to 1.6.2-11.
Some other information:
change version of libwine have no effect on whether SegFault happen or not.
wine64 1.6.2-12 will NOT cause SegFault. Other version of wine64 not tested.
Lastest libgl1-nvidia-glx:i386 upgrade is earlier than wine32
upgrade, so I have not try different libgl1-nvidia-glx:i386 version.
Version of libgl1-nvidia-glx:i386 is 340.46-1, as it is not shown
below.
My video card is GeForce G 105M/PCIe/SSE2.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages wine32 depends on:
ii libc6 2.19-11
ii libwine 1.6.2-12
ii libwine-gecko-2.21 2.21+dfsg2-1
ii x11-utils 7.7+2
wine32 recommends no packages.
wine32 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Closing this ancient bug now. Please reopen if it is still reproducible
with the current nvidia driver versions.
Andreas
--- End Message ---
