Re: Suggestions regarding a recent change in X11?
Re: Suggestions regarding a recent change in X11?
- Subject: Re: Suggestions regarding a recent change in X11?
- From: "Weller, Robert A" <email@hidden>
- Date: Tue, 27 Jul 2010 14:48:15 -0500
- Acceptlanguage: en-US
- Thread-topic: Suggestions regarding a recent change in X11?
Jeremy,
X11.bin-PR-423 found in the bug report you sent seems to fix the problem as far as Geant4 visualization is concerned. Of course, I haven't done any exhaustive testing, but "crash-on-startup" has morphed into "works-as-before" for the case I checked. In short it looks fixed to me.
I'm not sure how large the intersection is of Geant4 users who also use remote visualization on a Mac. My guess would be relatively small but non-zero.
Thanks for the quick reply.
Bob Weller
On Jul 27, 2010, at 1:57 PM, Jeremy Huddleston wrote:
> I just mentioned this in response to another email. It seems like you're suffering from:
> http://xquartz.macosforge.org/trac/ticket/423
>
> Please try the fix in that radar. This problem seems to be more wide-spread than I thought, so I may need to put out yet another update to 2.5.3. Can other people chime in and let me know how bad a regression this is?
>
> Thanks,
> Jeremy
>
> On Jul 27, 2010, at 10:43, Weller, Robert A wrote:
>
>> The following errors appeared in one of our custom codes following the 2.5.0 to 2.5.1 revision of X11 and remain in 2.5.2.
>>
>> This error occurs when the underlying program, a Monte Carlo radiation simulation, is run on a remote Linux cluster, but not when the same code is run locally on the Mac where the X server is running. The error evidently lies somewhere in the Geant4 c++ code (publicly available radiation simulation libraries) where graphical displays are generated.
>>
>> My question is, can anyone suggest what to look for in trying to find and fix the source of the error which is leading to this failure?
>>
>> Here are the lines that the program produces in lieu of the correct graphical display:
>> ------------------------------------------------------------------
>> X Error of failed request: BadMatch (invalid parameter attributes)
>> Major opcode of failed request: 147 (GLX)
>> Minor opcode of failed request: 5 (X_GLXMakeCurrent)
>> Serial number of failed request: 30
>> Current serial number in output stream: 30
>> -------------------------------------------------------------------
>>
>> What is this, and why should it begin with the 2.5.0 to 2.5.1 (and 2.5.2) revision?
>>
>> Any thoughts on a fix would be appreciated.
>>
>> Thanks,
>> Bob Weller
>> Vanderbilt University
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> X11-users mailing list (email@hidden)
>>
>> 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