• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Where can I find out more about xp_destroy_surface?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Where can I find out more about xp_destroy_surface?


  • Subject: Re: Where can I find out more about xp_destroy_surface?
  • From: Nathan Dornbrook <email@hidden>
  • Date: Sun, 12 Aug 2012 09:21:38 +0000
  • Thread-topic: Where can I find out more about xp_destroy_surface?

Okay, guys, just a heads up:

This was an error between the keyboard and chair (it was purely my
mistake).

There is an error in the X11 implementation - the WineskinX11
implementation.

Unless XQuartz is specified in the Wine wrapper, it will use it's own
implementation of X11, which has a race condition bug.

If XQuartz is specified, this error does not exist.

Please disregard.

Cheers!
	- Nathan

Nathan Dornbrook

Vacta, Ltd.

CBC House
24 Canning Street
Edinburgh
EH3 8EG

email@hidden
Mobile: 07909 686 776

www.vacta.co.uk <http://www.vacta.co.uk/>

International Number:  +44 (0) 131 272 2828
UK Only Freephone: 0800 083 0028
Fax:   0131 652 3918


Reg. No. SC 353002   Registered Address: 24 Canning Street, Edinburgh, EH3
8EG




On 11/08/2012 09:41, "Nathan Dornbrook" <email@hidden>
wrote:

>Hi, Jeremy!
>
>Thank you for your prompt response and help.
>
>I've also been working with the Wine community, on the off chance that
>this was something they'd know how to solve.
>
>Well, I started changing the Wine engines in the wrapper.
>
>And discovered that this made no difference. I only tried four wrappers -
>1.5.10, 1.5.10NoXInput2, 1.3.17 (known good with this app on WineHQ) and
>1.4.9 (known good from PaultheTall). I tried both the bundled X11 app and
>XQuartz. The same error each time.
>
>Then I rebooted the machine.
>
>On a clean reboot, the application launches every time. It throws these
>following errors (captured under Wine 1.5.10, clean boot, Mac OS X
>10.7.4):
>
>error: xp_attach_gl_context returned: 2
>X Error of failed request:  0
>  Major opcode of failed request:  148 (GLX)
>  Minor opcode of failed request:  26 (X_GLXMakeContextCurrent)
>  Serial number of failed request:  6646
>  Current serial number in output stream:  6646
>
>
>But still is able to run. This implies to me that the error you pointed me
>to is occurring whether the xp_destroy_surface race condition exists or
>not.
>
>I'm happy to work on this myself, albeit slowly, and share my work with
>the community, if only I knew where to start.
>
>Is there a way to enable verbose logging for XQuartz? I'll ask the Wine
>guys about Wine.
>
>- Nathan
>
>
>Nathan Dornbrook
>
>Vacta, Ltd.
>
>CBC House
>24 Canning Street
>Edinburgh
>EH3 8EG
>
>email@hidden
>Mobile: 07909 686 776
>
>www.vacta.co.uk <http://www.vacta.co.uk/>
>
>International Number:  +44 (0) 131 272 2828
>UK Only Freephone: 0800 083 0028
>Fax:   0131 652 3918
>
>
>Reg. No. SC 353002   Registered Address: 24 Canning Street, Edinburgh, EH3
>8EG
>
>
>
>
>On 10/08/2012 20:36, "Jeremy Huddleston" <email@hidden> wrote:
>
>>This looks like it might be this issue (or possibly the same root cause):
>>
>>http://xquartz.macosforge.org/trac/ticket/536
>>
>>On Aug 10, 2012, at 9:34 AM, Nathan Dornbrook
>><email@hidden> wrote:
>>
>>> Hi, complete new guy.
>>>
>>> I was trying to install a game ­ Anno 1404 ­ on a Mac.
>>>
>>> I thought I'd try and wrap it with Wine. It didn't work.
>>>
>>> Not really being a techie, I thought I'd look in the logs to see if
>>>they said anything that might hint at what had gone wrong.
>>>
>>> I googled each line in each log until one of the lines was the
>>>obviously fatal error.
>>>
>>> To cut to the chase, the salient log results are:
>>>
>>> xp_destroy_surface: assertion failed: s != NULL
>>> xp_destroy_surface error: 3
>>> X Error of failed request:  0
>>>  Major opcode of failed request:  148 (GLX)
>>>  Minor opcode of failed request:  26 (X_GLXMakeContextCurrent)
>>>  Serial number of failed request:  3782
>>>  Current serial number in output stream:  3782
>>>
>>> Okay, so before I run off and file a bug report, I've researched this
>>>error. It looks like it's caused by a race condition in XQuartz.
>>>
>>> Now, I want to know more.
>>>
>>> Where can I find out how XQuartz interacts with Wine and how do I
>>>troubleshoot XQuartz? Is there an FAQ or a tutorial somewhere?
>>>
>>> Thank you in advance ­ if I'm asking the wrong group, you have my
>>>apologies and I'll try and find somewhere else.
>>>
>>> - Nathan
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> X11-users mailing list      (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>.
>>>org
>>>
>>> This email sent to email@hidden
>>
>>
>
>
>
> _______________________________________________
>Do not post admin requests to the list. They will be ignored.
>X11-users mailing list      (email@hidden)
>Help/Unsubscribe/Update your Subscription:
>.co.uk
>
>This email sent to email@hidden


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list      (email@hidden)

This email sent to email@hidden


  • Follow-Ups:
    • Re: Where can I find out more about xp_destroy_surface?
      • From: Jeremy Huddleston Sequoia <email@hidden>
References: 
 >Re: Where can I find out more about xp_destroy_surface? (From: Nathan Dornbrook <email@hidden>)

  • Prev by Date: Re: Installing XQuartz 2.7.2 on OS X 10.8
  • Next by Date: Re: Installing XQuartz 2.7.2 on OS X 10.8
  • Previous by thread: Re: Where can I find out more about xp_destroy_surface?
  • Next by thread: Re: Where can I find out more about xp_destroy_surface?
  • Index(es):
    • Date
    • Thread