Xlock crashes out and returns to X when it attempts to load one of the random screens. Below is the crash message on two different occasions. I'm not concerned about the GLX errors, just the portion regarding the missing files/directories. Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". could not read file "/usr/share/pixmaps/redhat/redhat-292.xbm" Xlib: extension "GLX" missing on display ":0.0". Access control list restored. xlock: caught signal 11 while running molecule mode (uid 1000). could not read file "/usr/share/pixmaps/redhat/redhat-292.xbm" could not read file "/usr/share/pixmaps/redhat/redhat-292.xbm" could not read file "/usr/share/pixmaps/redhat/redhat-292.xbm" could not read file "/usr/share/pixmaps/redhat/redhat-292.xbm" could not read file "/usr/share/pixmaps/redhat/redhat-292.xbm" could not read file "/usr/share/pixmaps/redhat/redhat-292.xbm" Xlib: extension "GLX" missing on display ":0.0". could not read file "/usr/share/pixmaps/redhat/redhat-292.xbm" could not read file "/usr/share/pixmaps/redhat/redhat-292.xbm" Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". Xlib: extension "GLX" missing on display ":0.0". could not read file "/usr/share/pixmaps/redhat/redhat-292.xbm" could not read file "/usr/share/pixmaps/redhat/redhat-292.xbm" Xlib: extension "GLX" missing on display ":0.0". Access control list restored. xlock: caught signal 11 while running molecule mode (uid 1000).
Brandon, Since you did the recent opengl fix, I think this might be related to that. Brandon, it also looks like there is a 5.0.4 release of this package (from what I saw on its ibilblio download location). Please see if that fixes the gtk/motif issues as mentioned in our ChangeLog in portage. Thanks.
Ok, grepping source trees comparing versions, this won't be a problem with the new version that seemant mentioned so I'm going to go ahead and finish up an ebuild for the new version and put it in portage for you to test.
I'm marking this as fixed, but let me know if there is still a problem when you are able to rsync the new version from portage.