wineskin crash if X11 is running and viceversa
Play your favorite Windows video games on Mac OS X
Brought to you by:
doh123
If there is a X11 session open (just click on Utilities/X11.app) then launching an application packaged with Wineskin will crash Wineskin. If they are incompatible each other then when starting Wineskin we could check if there exist a different X11 session and show a message to the user.
Viceversa if my Wineskin application is running and I start X11 then the X11 session will crash and lo in an infinite loop of crashes. That's maybe unavoidable.
I cannot seem to reproduce this problem at all... Wineskin and Apple's X11 and Xquartz all seem to open fine for me on several machines at the same time in any combination.
Can you give any more info on this? What OS version.. what X11 versions have you tried?
I know there is a problem with certain versions of X11 sometimes locking a file that can cause an infinite loop of crashes. I can add something to Wineskin to make sure that doesn't happen.
Try going into Terminal and removing a certain folder and see if that fixes your problem... The command to remove the folder is...
sudo rm -rf /tmp/.X11-unix/
make sure you type it 100% right or copy and paste since its sudo and rm together it can really hose your computer if you do it wrong.
I have seen that folder get locked and cause X11 versions to not launch right and get stuck in repeating loops.
Sorry for the delay, but it took me some time to understand what is happening and to reproduce the issue.
A) I confirm that wineskin and X11 run well at the same time, they work flawlessly. I tested the following systems:
OS X 10.7.1 + X11 XQuartz 2.6.3 xorg-server 1.10.2
OS X 10.6.8 Build 10K549 + X11 XQuartz 2.3.6 (xorg-server 1.4.2-apple56)
OS X 10.6.0 + X11 XQuartz 2.3.4 (xorg-server 1.4.2-apple45)
OS X 10.5.8 + X11 XQuartz 2.1.6 (xorg-server 1.4.2-apple33)
OS X 10.5.6 + X11 Xquartz 2.1.5 - (xorg-server 1.3.0-apple22) (2.1.5)
B) The incompatibility happened after I had a failure while starting a wineskin session.
My application is using the wldap32.dll. Under a default wineskin configuration it doesn't work and I get the following error (using wineskin Test Debug):
err:module:load_builtin_dll failed to load .so lib for builtin L"WLDAP32.dll" ...
(Note: The dll was available in the application folder)
After changing the configuration of the wldap32.dll from builtin to native I was able to run my application
(winecfg/libraries: override wldap32 to native, buildin)
But from that point on I had the incompatibility between wineskin and X11. I was able to run wineskin OR X11 successfully. I don't know why.
Your suggestion to delete the (empty) /tmp/.X11-unix/ folder works well (if X11 was in an infinte loop it stopped the loop) and both applications are again compatible at the same time.
I'm not sure why wineskin uses the .X11-unix folder, after running a successful wineskin applications the following folders are created.
folder: /tmp/.wine-501/server-...
folder: /tmp/.X11-unix
file: /tmp/.X5283-lock
file: /tmp/.wine-501/server-.../lock
The .X11-unix folder seems to be always empty.
Note: in the previous comment at B) I was using OS X 10.7.1 with the latest WS7 Engine 1.3.27 and Wineskin 2.4
Additional Note: if you want to test my application which needs the wldap32.dll then download this zip:
http://www.andreaplanet.com/andreamosaic/download.php?version=macbeta
and copy the whole folder
AndreaMosaic Beta.app/Contents/AndreaMosaic/drive_c/AndreaMosaic
to the drive_c folder of your wineskin wrapper and run "/AndreaMosaic/AndreaMosaic.exe -menu" as the initial application. Some buttons will not work because the windows registry have to be tweaked (web links, pdf viewer, etc). You can try to open the downloaded beta to see how the existing application is working using WineBottler.
Need to prevent the .X11-unix folder from remaining locked if there is a crash
This should be fixed in git now... Wineskin makes sure extra X11 lock files do not stay around. The Wine lock files are ignored, these do not harm anything and are much harder to keep track of. They clear themselves out in normal /tmp folder maintenance (like on a reboot)
author doh123 <doh123@doh123.com>
Mon, 5 Sep 2011 23:07:20 +0000 (18:07 -0500)
committer doh123 <doh123@doh123.com>
Mon, 5 Sep 2011 23:07:20 +0000 (18:07 -0500)
commit 2341ffc1660c1fdf46a609d74210fb83b70101b3
tree 1a6abb44844b7175d5d67d5340db7195f0eba68c
parent d615acd64fb93253dfc75ee9c081d2e66b682f0f
3402175 Wineskin will clean up WineskinX11 lock files