Wineskin Support Forum Help

Forums » Wineskin Support Forum » macOS Sierra

macOS Sierra

Just checking before updating OS on my mac - is latest Wineskin running smoothly on macOS Sierra? Or should I wait?

Yep, works fine. Of course, you might want to wait for the developers official word.


Somes 2.6.2 Wrapper works, others not, and I don't know why. It seems that sometime "Application tried to create a window, but no driver could be loaded." and crash.
A new one don't work, even the "config utility" tools. It's my experience on iMac 2013.

I installed wineskin winery to run Registax under El Capitan, which ran fine:  recognized four cores automatically.

I updated to Sierra and Registax won't launch, because wine is not running

First I got an X11 quit unexpectedly, then a Registax quit unexpectedly.

Here is the beginning of the crash report:

Process:               WineskinX11 1004

Path:                  /Applications/Registax.app/Contents/MacOS/WineskinX11

Identifier:            Registax682336378Wine.wineskin.prefs

Version:      (Wineskin 2.6.0)

Code Type:             X86 (Native)

Parent Process:        ??? 1

Responsible:           WineskinX11 1004

User ID:               501


Date/Time:             2016-10-01 16:18:38.679 -0400

OS Version:            Mac OS X 10.12 (16A323)

Report Version:        12

Anonymous UUID:        F580C8F3-9917-995D-4C50-C6EE5C05EA86



Time Awake Since Boot: 900 seconds


System Integrity Protection: enabled


Crashed Thread:        5


Exception Type:        EXC_CRASH (SIGABRT)

Exception Codes:       0x0000000000000000, 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY


Application Specific Information:

Failed to activate core devices.

X.Org X Server 1.13.0 Build Date: 20120921

abort() called


Here is Thread 5:


Thread 5 Crashed:

0   libsystem_kernel.dylib         0x9f68949a __pthread_kill + 10

1   libsystem_pthread.dylib       0x9f76ced3 pthread_kill + 90

2   libsystem_c.dylib             0x9f5e9a5c abort + 141

3   WineskinX11                   0x0014dd1b OsAbort + 11

4   WineskinX11                   0x00010fd0 AbortDDX + 32

5   WineskinX11                   0x00154daf AbortServer + 47

6   WineskinX11                   0x00155997 FatalError + 151

7   WineskinX11                   0x000ece22 InitCoreDevices + 162

8   WineskinX11                   0x0002f80b dix_main + 779

9   WineskinX11                   0x000170c2 server_thread + 50

10  libsystem_pthread.dylib       0x9f76a11b _pthread_body + 184

11  libsystem_pthread.dylib       0x9f76a063 _pthread_start + 243

12  libsystem_pthread.dylib       0x9f76993e thread_start + 34




The following gets registax working again:


sagittaemacSep 28, 2015 11:53 AM(in response to asaggynoodle)


Just to let you know, disabling rootless does work to restore the wrappers:


Restart, hold Command - R, once booted in the Restore partition go to the Utility Menu and select Terminal

In terminal:

csrutil disable


Then Restart, WineskinX11 should work within the wrappers.


To reenable roootless follow the same directions but in Terminal:

csrutil enable


I'm not a fan of this method but it works, perhaps Wine will update this issues soon.







Upgraded to Sierra yesterday and can confirm it doesn't let me run a previously installed program but crashes. Only one thing to do, running it inside a virtual machine instead. :-(

Anonymous, maybe you can try to recreate the wrapper? Or update it with the Porting Kit, in case your previous system was older than El Capitan.

I've had issues with apps created on eaier versions on OS X but now upgraded to OS X Serria, complaining about errors whe trying to lanch...

if 2.6.2 is needed, then that means i must chage pachage yes?

Also can these still be un from any folder? as i notice in Sierra Apple have now require su to run tings mmore ofte from /Applocations only..

not always, tighening this down. Also, just to be clear, is it only the package 2.6.2, and not the engine that needs to be changed ?Then again, I would also think if u have an old engine, then u mayrun into trouble with a new package wouldn't you ?  e.g  games which work on older engines only.


Can anyone confirm these?


If you upgrade a wrapper to 2.6.2 (needed for Sierra), you'll need to change the engine afterwards as well.  You can change it to the exact same engine you already had, it just needs to reinstall it in the wrapper to work right... due to security changes on Sierra, the installation process had to be modified.

ok thanks,,, must i re-download engines not already downloaded, with the Winskin app, or can i get these from  Medafire . (link from downlaod page) ?


On some of my apps, the wrapper is already 2.6.2, do i need to re-do this as well or not ?

Post new message

Attach file Maximum size: 10.00 Mb
Post new reply

Show posts: