r600g segfaults running glxgears. Here is a backtrace
#0 0x00007ffff5327f6e in loopback_VertexAttrib3svNV (index=1283, v=0x1e08) at main/api_loopback.c:1137
#1 0x00007ffff532800f in loopback_VertexAttribs3svNV (index=<value optimized out>, n=<value optimized out>, v=0x2dd) at main/api_loopback.c:1220
#2 0x00007ffff525eed6 in execute_list (ctx=0xb55960, list=<value optimized out>) at main/dlist.c:8163
#3 0x00007ffff526130a in _mesa_CallList (list=1) at main/dlist.c:8511
#4 0x0000000000401ce2 in draw ()
#5 0x00000000004035c9 in main ()
Try 'make clean'.
I had similar problem (with r300g) ,
In fact glxgears did not load the right mesa lib
despite a good ldconfig -v (added new mesa path 000_mesa.conf)
it should show the path of the lib used by the app
if it is wrong and you use natty or another ubuntu
a temporary fix is:
sudo rm /etc/ld.so.conf.d/GL.conf (symbolic link to original mesa)
don't know the right fix though
If ldd confirms you are using the good library, have a look at the following bug:
It may explain the problem. Otherwise, watchout for Natty, things are a real mess because drivers are now installed under the multiarch folder, but the dev files are installed in a different folder. So if you just compiled and installed like you were doing in previous Ubuntu version, you will end up in a dead end. I had to work a bit to figure everything out.
Interesting, I'm using LD_LIBRARY_PATH and LIBGL_DRIVERS_PATH I don't think that is the problem. It's only glxgears having this problem, however, so that problem may be with it.
*** This bug has been marked as a duplicate of bug 36282 ***