--Architecture(ia32,ia32e,compatiblity): ia32 & ia32e & compatibility --2D driver: git(eca082ca0fec12973a4dbb0106b841136b5b6cdb) --Xorg: 7.1 --Mesa: CVS tip --OS: FC5 --Kernel: 2.6.17 Glean can't run completely, and get following reports at the beginning: X Error of failed request: GLXBadContextTag Major opcode of failed request: 143 (GLX) Minor opcode of failed request: 5 (X_GLXMakeCurrent) Serial number of failed request: 816 Current serial number in output stream: 816
Created attachment 7299 [details] Xorg log file
Created attachment 7300 [details] Xorg conf file
Created attachment 7301 [details] Glean test log
1. This also happens on 915 and 945. 2. This is regression. It was working fine on Sep 28.
Just compiled cvs checkout and running xine -V opengl gives this: X Error of failed request: GLXBadContextTag Major opcode of failed request: 145 (GLX) Minor opcode of failed request: 5 (X_GLXMakeCurrent) Serial number of failed request: 2272 Current serial number in output stream: 2272 similar messages are emitted, when running gmplayer -vo gl2 and gmplayer -vo gl. But with these two, mplayer dies, when stopping the video - xine dies imediatly. I'm running a r300 based ATI Radeon - so it may be an error not in the driver but somewhere higher?!
Eric, how do you think about the correct place to report this bug?
Hi all! I've posted two different patches to bug 8443. Please try them out.
Just tested both patches and both patches (seperately) allowed me to start: -> xine -V opengl(ok, I got a screewed picture, but that is another field) -> wine opened C&C RA2 just fine -> supertux switched to and from opengl just fine Great work!
I just commited patch #7429. Could you verify that it resolves this problem? It should be version 1.30 of src/glx/x11/glxext.c. You'll need to rebuild libGL, of course.
Ian, thanks for the fix. Verified.
*** Bug 8700 has been marked as a duplicate of this bug. ***
Mass version move, cvs -> git
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.