Bug#908412: wine-development: regression: the game SimSig fails to run
Package: wine-development
Version: 3.14-2
Severity: normal
Dear Maintainer,
SimSig (from simsig.co.uk) ceased to work under wine in version 3.14-2
(was OK in 3.14-1). It prints out this error message:
000f:err:service:process_send_command service protocol error - failed to read pipe r = 0 count = 0!
002b:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\sfhlp02": c0000002
0014:err:service:process_send_command service protocol error - failed to write pipe!
wine: Unhandled page fault on write access to 0x00564000 at address 0x7bc55081 (thread 0031), starting debugger...
000f:err:service:process_send_command service protocol error - failed to read pipe r = 0 count = 0!
0009:err:seh:setup_exception_record stack overflow 1328 bytes in thread 0009 eip 7bc8483f esp 00240e00 stack 0x240000-0x241000-0x340000
where the fatal thing is probably the last line (the rest appears even
with applications that work, eg. cmd.
Regards
Jiri Palecek
-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-development.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 4.17.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE=cs_CZ (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages wine-development depends on:
ii wine32-development 3.14-1
wine-development recommends no packages.
Versions of packages wine-development suggests:
pn dosbox <none>
pn playonlinux <none>
ii winbind 2:4.8.5+dfsg-1
pn wine-binfmt <none>
ii winetricks 0.0+20170823-1
Versions of packages wine-development is related to:
ii fonts-wine 3.0.2-2
ii wine-development 3.14-1
ii wine32-development 3.14-1
pn wine64-development <none>
-- no debconf information
Reply to: