This has been tested with Quake III, the Marbleblast demo, DGen, Abuse_SDL, and ZSNES. Every time I open an application that requries the use of OpenGL (or is compiled with the ability to use OGL) it crashes with a SIGSEGV (Signal 11; Segmentation Fault). In Quake III, when it loads libGL.so.1, that is when it sends the SIGSEGV. To test to see if this is true, I swiched to the XFree OGL implentation, and everything's fine.
umm please provide more information ... `emerge info` what version of nvidia drivers ? what if you do `opengl-update nvidia` before you load the X
Sorry about not including the nvidia driver info: 1.0-3123 (1.0-3132-r2) right from portage. As for emerge info: Portage 2.0.46-r12 (default-x86-1.4, gcc-3.2.1, glibc-2.3.1-r2) ================================================================= System uname: 2.4.19-gentoo-r10 i686 AMD Athlon(tm) processor GENTOO_MIRRORS="http://gentoo.oregonstate.edu/ http://distro.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm arts avi crypt cups encode gif jpeg kde gnome libg++ libwww mikmod mmx mpeg ncurses nls pdflib png qtmt quicktime spell truetype xml2 xmms xv zlib gtkhtml gdbm berkdb slang readline bonobo svga java guile X sdl gpm tcpd pam ssl perl python esd imlib oggvorbis gtk qt motif opengl mozilla" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-tbird -O3 -pipe" CXXFLAGS="-march=athlon-tbird -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache" Also, I did do an opengl-update nvidia on the console before starting X -- same results.
Oops the NVIDIA_kernel should read 1.0-3123r2.
I have found just now that the segementation faults occuring in the module is due to __GL_SINGLE_THREADED=1 being exported into the enviroment. I don't know if you really can call this a bug or not; it seems strange to me anyway that having the applications not use multithreading would cause such behaviour in the program. Anyeay I apologize as I don't think this is really a bug.