[Chimera-users] [3dem] Error to run chimera remotely on a GPU computer from Mac computer

Li, Zongli Zongli_Li at hms.harvard.edu
Thu Sep 30 19:44:19 PDT 2021


Hi Tom,

Thank you for the information.

Best,

Zongli
________________________________
From: Chimera-users <chimera-users-bounces at cgl.ucsf.edu> on behalf of Tom Goddard via Chimera-users <chimera-users at cgl.ucsf.edu>
Sent: Thursday, September 30, 2021 10:17 PM
To: M. Jason de la Cruz <mdelacr at gmail.com>
Cc: Zongli Li <zongli.li at gmail.com>; 3dem <3dem at ncmir.ucsd.edu>; chimera-users at cgl.ucsf.edu <chimera-users at cgl.ucsf.edu>
Subject: Re: [Chimera-users] [3dem] Error to run chimera remotely on a GPU computer from Mac computer

Hi Jason,

  Thanks for those tips.  We usually tell ChimeraX and Chimera users to give up any hope of OpenGL remote display with X windows as this rarely works unless the graphics drivers on the two machines are identical.  This has nothing to do with the specific apps, no OpenGL apps work.  This kind of remote display worked pretty reliably 20 years ago in the days of SGI but seems barely supported now.  Glad to hear that it can sometimes work for those who need to use this low performance 3D rendering method.  We recommend moving your data to the visualization machine for the best visualization experience.

Tom


On Sep 30, 2021, at 12:49 PM, M. Jason de la Cruz via Chimera-users <chimera-users at cgl.ucsf.edu<mailto:chimera-users at cgl.ucsf.edu>> wrote:

Hi Zongli,

As Colin mentioned, this error is likely due to GLX indirect rendering and XQuartz on the Mac client.  We had this problem a few months ago when Mac users updated their operating system to macOS Catalina (version 10.15.7) or later, and/or upgraded to the most recent version of XQuartz (version 2.8.1 at the time), and suddenly had trouble displaying remotely-rendered graphics on their local terminal.

The following instructions are what I sent to my colleagues on this issue back then (May 2021), hopefully they are still valid now:



1.  In a terminal on your Mac, enter the following command:



defaults write org.xquartz.X11 enable_iglx -bool true



2.  If you don’t have the most recent XQuartz on your system, go to https://www.xquartz.org<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.xquartz.org_&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=uQMJAWlPEv596kvCdV_ot7YTGNux4AXH5-WfTfSNGmY&m=bDNBV_qd4jNX6kYE6M4YlGm_Xg3SG1_qAxuOrc7-FSg&s=GSwXOAkF0cvLrs9vXOtvN_udfrIFEFlnC2Q0rtap9S0&e=>/ and download version 2.8.1 (you may also be able to update it when prompted by your system).  If you downloaded the package, mount the disk image and install the package to your computer.  Then log out and log back in again.



3.  On your Mac, open a terminal and connect to the remote Linux system using the ssh command such as below:



ssh -X [user]@[remote-computer] or ssh -Y [user]@[remote-computer]



4.  Source SBGrid if necessary, then try to open an image using 3dmod or e2display.py.  Alternatively, you can enter the commands glxinfo or glxgears to test and make sure you have no errors.



Hope that helps!



Best,
--Jason



On Thu, Sep 30, 2021 at 3:15 PM Colin Gauvin <colin at gauvin.id<mailto:colin at gauvin.id>> wrote:
It sounds like you need to enable indirect GLX (iGLX) on the client machine.
If you are using XQuartz, iGLX is disabled by default.

--
Best Regards,

Colin Gauvin
colin at gauvin.id<mailto:colin at gauvin.id>
Lawrence Laboratory, Montana State University
(401) 263-0343

On Thu, Sep 30, 2021 at 1:57 PM Zongli Li <zongli.li at gmail.com<mailto:zongli.li at gmail.com>> wrote:
Dear listers,

I ssh with "-Y"  from my Mac desktop to a GPU computer and process my data there. Quite often I need to look at the 3D volumes with chimera. This had been working nicely for long time. But all suddenly it stopped working and game the error 3:

X Error of failed request:  GLXBadCurrentWindow
  Major opcode of failed request:  149 (GLX)
  Minor opcode of failed request:  5 (X_GLXMakeCurrent)
  Serial number of failed request:  1400
  Current serial number in output stream:  1400


Did anyone encounter the same error? Any suggestions or tips to overcome this problem would be appreciated.

Thanks,

Zongli
_______________________________________________
3dem mailing list
3dem at ncmir.ucsd.edu<mailto:3dem at ncmir.ucsd.edu>
https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem<https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.ncmir.ucsd.edu_mailman_listinfo_3dem&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=uQMJAWlPEv596kvCdV_ot7YTGNux4AXH5-WfTfSNGmY&m=bDNBV_qd4jNX6kYE6M4YlGm_Xg3SG1_qAxuOrc7-FSg&s=IZQyFkNKOXNyhnY71mWsxUALhmiqBre1jmc3sE26PO4&e=>
_______________________________________________
Chimera-users mailing list: Chimera-users at cgl.ucsf.edu<mailto:Chimera-users at cgl.ucsf.edu>
Manage subscription: https://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users<https://urldefense.proofpoint.com/v2/url?u=https-3A__plato.cgl.ucsf.edu_mailman_listinfo_chimera-2Dusers&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=uQMJAWlPEv596kvCdV_ot7YTGNux4AXH5-WfTfSNGmY&m=bDNBV_qd4jNX6kYE6M4YlGm_Xg3SG1_qAxuOrc7-FSg&s=GWUKsujDV_b9z8KQooTB2JP2NnJM45Fj41T9wcAOuFw&e=>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://plato.cgl.ucsf.edu/pipermail/chimera-users/attachments/20211001/95d0652d/attachment.html>


More information about the Chimera-users mailing list