Results 1 to 7 of 7
Hi there Linux Forums!
Whenever I run xlock I get this error message after a while:
Code:
xlock: main/renderbuffer.c:2078: _mesa_add_renderbuffer: Assertion `bufferName == BUFFER_DEPTH || bufferName == BUFFER_STENCIL || fb->Attachment[bufferName].Renderbuffer ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 04-15-2009 #1
[SOLVED] xlock troubles
Hi there Linux Forums!
Whenever I run xlock I get this error message after a while:
I have an onboard VIA Technologies, inc. KN400/KM400/P4M800 video card, can any one tell me how to fix this?Code:xlock: main/renderbuffer.c:2078: _mesa_add_renderbuffer: Assertion `bufferName == BUFFER_DEPTH || bufferName == BUFFER_STENCIL || fb->Attachment[bufferName].Renderbuffer == ((void *)0)' failed. Aborted
Thanks guys.
- 04-17-2009 #2Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 10,160
Sounds like a bug in xlock. It is aborting after detecting a null pointer access. Since it has source file information, it must be built for debugging. Have you customized and/or built any of your X-Windows components (such as xlock)?
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 04-17-2009 #3
No, i have all my X stuff through yum, i dont compile/customize critical components.
- 04-17-2009 #4Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 10,160
Well xlock isn't part of the xorg package on my system. I can get xlockmore from the rpmforge repository via yum. What distribution/version of Linux and which X server are you running?
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 04-18-2009 #5
Fedora 10,
X.Org X Server 1.5.3
i dont remember ever compiling or w/e xlock, and it isnt in the repos, it was just there one day, it was probably from one of my DEs/WMs
- 04-18-2009 #6Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 10,160
Well, that pretty much confirms the bug diagnosis then. Someone built or installed (probably built since it is in a debuggable state) a version that has a bug in it. In any case, xlock is pretty much deprecated these days. If you want xlock, then you can use xlockmore, which is xlock, but more up-to-date. It's available in the rpmforge repositories. I haven't tried it yet, but their web site is pretty well done.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 04-19-2009 #7
yeah, i got xlock more through rpmfusion, thanks for all your help!



