The code here is if-defed for Win, Cocoa and X. I used X in sync mode so I could trace down where this happens, and it's actually in the first call to glXMakeCurrent.Īnd this is the place where the context is created for X (we share contexts so we can share display lists and textures but in this case it's the only context created so share = None): I ran latest root-5.34 remotely (on Fedora 20 with latest NVIDIA drivers) against XQuartz-2.7.8_beta3 (on osx-10.8.5, yeah, I'm lazy) and can also still reproduce the problem. Hi, I'm the guy that is mostly responsible for the GL code in ROOT :) Thank you very much for your effort to correct this commented on Feb 26, 2015 You can download both version of ROOT from Īfter you installed it and load environmental variables, type 'root' will let you in to ROOT.Īt the prompt, typing 'TEveManager::Create()' will cause the error. I'll send you the intruction to encounter that error commented on Feb 15, 2015 Can you help me reproduce this? Assuming I install ROOT on a remote Linux box, how do I use it to trigger the commented on Feb 15, 2015 I basically reverted the X11 GLX change that went into 2.7.7. I tried it and it also gives the same error message. Please test 2.7.8_beta2 and report if the issue is commented on Feb 15, 2015 ![]() I've rolled back to 2.7.6 to avoid this commented on Feb 15, 2015 I think the environmental variables are not set with 2.7.8 beta 1 version before. I'm sorry but recently I see the same error. Resolution set to commented on Dec 17, 2014.So, please close this commented on Dec 10, 2014 I can present you much information if you need.Įrror in : GLXBadContextTag (TGLWidget XID: 6292620, XREQ: 150)Įrror in : 'TGLViewerBase' unable to take DrawLock, already DrawLockĮrror in : 'TGLViewerBase' unable to take DrawLock, already commented on Oct 29, 2014 ![]() It was okay with XQuartz 2.7.6, so I think something is wrong with XQuartz 2.7.7. I'm using ROOT () remotely and it uses X11 forward for showing something.įor some parts of that package, it gives me errors like below.
0 Comments
Leave a Reply. |