Red Hat Bugzilla – Bug 91034
X logs out when using VRMLview or OpenGL ImmediateX viewer
Last modified: 2015-01-07 19:05:08 EST
Description of problem: Whenever I start VRMLview or open up an OpenGL ImmediateX viewer from a program made with the Geant4 toolkit, I am logged out of X. I am then presented with the GUI login screen. I have already contacted VRMLview support, and they feel as if Mesa is the problem. Version-Release number of selected component (if applicable): 3.4.2-10 How reproducible: This happens every time. Steps to Reproduce: 1. Execute either VRMLview or a program written with the Geant4 toolkit that opens up an OpenGL ImmediateX viewer. Actual results: X closes, and I'm presented with a GUI login screen. Expected results: VRMLview and the OpenGL ImmediateX viewer should run. Additional info: VRMLview is obtainable from http://www.sim.no -> downloads -> VRMLview/download Geant4 web page: http://geant4.web.cern.ch/geant4
I've managed to capture VRMLview's error stream output. Here it is. X Error: GLXBadDrawable 131 Major opcode: 129 QGLContext::makeCurrent(): Failed.
Created attachment 91738 [details] My XF86Config file This is my X configuration. I hope this helps.
The error message is telling you that the application is requesting a bad drawable. It's even saying where it is: QGLContext::makeCurrent() This isn't a Mesa bug IMHO, but an application bug.
Oops, I hit submit too early there... While I believe this to be an application bug, or a bug in a library that application uses, if the application's authors wont look into the problem, and insist it is a Mesa bug, please upgrade to Red Hat Linux 9, and try to reproduce it there, as we only issue security fixes for Red Hat Linux 7.2 at this point, so if Mesa is indeed at fault, which I believe is very unlikely, it isn't the type of bug that we would examine for an old distro release. If the problem is present in Red Hat Linux 9, which I believe is entirely likely, as I believe it is an application bug as said above, please report the problem to the dri-devel or mesa3d-dev mailing lists on sourceforge so the Mesa developers can give their opinion on the problem, and investigate it. Closing NOTABUG.