Windows application with wine doesn't start : kernel 3.15?

English Install/Boot/Login
1

Hello,

I installed yesterday the last update from Tumbleweed.
Therein is the new kernel 3.15. I rebooted the system and I’m now running kernel 3.15

uname -a
Linux hpprol2 3.15.0-33.g9194b64-xen #1 SMP Tue Jun 10 13:35:22 UTC 2014 (9194b64) x86_64 x86_64 x86_64 GNU/Linux

Now I cannot more start a windows application with wine: Starting it in a console I receive these errors messages

wine /local/wingames/wg2/arachnid.exe
modify_ldt: Argument invalide
modify_ldt: Argument invalide
modify_ldt: Argument invalide
modify_ldt: Argument invalide
modify_ldt: Argument invalide
err:module:attach_process_dlls "krnl386.exe16" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for L"C:\\windows\\system32\\winevdm.exe" failed, status c0000005

Wine version is:

rpm -qa wine
wine-1.7.2-2.1.x86_64

winecfg can start and displays the windows version as “Windows XP”

Googling I found the same error here
https://lkml.org/lkml/2014/5/7/145
https://bugzilla.redhat.com/show_bug.cgi?id=1097970
but no solution
these two are related to kernel 3.14.3

Any idea?

Regards
Philippe

2

Hello,

the problem seems only affect 16-bit windows programs.
I found a solution in a comment on
http://www.linuxquestions.org/questions/slackware-14/kernel-3-14-4-and-the-nvidia-drivers-and-wine-4175504913/page2.html

disabled 16-bit segments on 64-bit kernels due to an information
    leak.  However, it does seem that people are genuinely using Wine to
    run old 16-bit Windows programs on Linux.
    
    A proper fix for this ("espfix64") is coming in the upcoming merge
    window, but as a temporary fix, create a sysctl to allow the
    administrator to re-enable support for 16-bit segments.
    
    It adds a "/proc/sys/abi/ldt16" sysctl that defaults to zero (off). If
    you hit this issue and care about your old Windows program more than
    you care about a kernel stack address information leak, you can do
    
       echo 1 > /proc/sys/abi/ldt16
    
    as root (add it to your startup scripts), and you should be ok.

the solution solve the problem :slight_smile:

Regards
Philippe