http://bugs.winehq.org/show_bug.cgi?id=36664
Bug ID: 36664 Summary: Unable to run anything when with kernel version 3.14 and wine configured as Windows 98 Product: Wine Version: 1.7.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: doragasu@hotmail.com
Recently a security issue was fixed on Linux 3.14 kernel for x86_64 (and is being backported to previous versions as well). The security fix unfortunately caused win16 software to stop working, but 32 bit software is supposed to not be affected. This is being discussed here: http://forum.winehq.org/viewtopic.php?f=8&t=22568
The problem is configuring Wine as Windows 9x causes this error to appear even when trying to run 32 bit Windows applications: if you use a kernel with this security flaw fixed and configure Wine in Windows 9x mode, nothing works anymore, not even winecfg.
To reproduce the problem you need a Linux box running a 64-bit 3.14 kernel (I'm running up-to-date Archlinux). Then follow these steps:
1.- Create a fresh wine prefix:
$ WINEARCH=win32 WINEPREFIX=/home/jalon/wine/test wineboot
2.- Run winecfg:
$ WINEPREFIX=/home/jalon/wine/test winecfg
3.- In winecfg, in the default tab (Applications), select "Windows 98" in the "Windows Version" combo box and then click "OK".
4.- Try to run any 32 bit application (e.g. wineboot as in step 1):
$ WINEPREFIX=/home/jalon/wine/test wineboot
The application will not start, wineboot.exe will be freezed using 100% CPU, and these messages will be printed in the terminal:
modify_ldt: Invalid argument modify_ldt: Invalid argument modify_ldt: Invalid argument modify_ldt: Invalid argument modify_ldt: Invalid argument err:process:__wine_kernel_init boot event wait timed out modify_ldt: Invalid argument modify_ldt: Invalid argument modify_ldt: Invalid argument modify_ldt: Invalid argument modify_ldt: Invalid argument
As winecfg cannot be started anymore in this prefix, the only way to revert it to a working configuration is manually editing the registry and removing the Windows 98 config entry, so this bug is critical because might render existing wine prefixes useless if user sets Windows version to Windows 9x (and maybe also other versions like Windows Me, but I have not tested it).