OpenGL programs crash with nvidia driver 280.13

Bug #919365 reported by Jussi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Signal 11 is raised by many previously (at least on 10.04) working programs that use OpenGL.
Crash happens always in /usr/lib/nvidia-current/libnvidia-glcore.so.280.13 .

I'm on Xubuntu 11.10 64bit.
Kernel 3.0.0-15-generic

Example:

glxgears will crash on startup.

$ gdb glxgears
GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/bin/glxgears...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/glxgears
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x00007ffff6383fe0 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#2 0x00007ffff5ddfa71 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#3 0x00007ffff5f34029 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#4 0x00007ffff5f02479 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#5 0x00007ffff5f0249d in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#6 0x00007ffff5c7742b in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#7 0x00007ffff5c77e45 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#8 0x0000000000401a72 in ?? ()
#9 0x0000000000403176 in ?? ()
#10 0x00007ffff719130d in __libc_start_main (main=0x402aa0, argc=1,
    ubp_av=0x7fffffffe2a8, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fffffffe298) at libc-start.c:226
#11 0x00000000004017b9 in ?? ()

nvidia-settings will crash when clicked on "OpenGL/GLX Information"

gdb nvidia-settings
GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/bin/nvidia-settings...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/nvidia-settings
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffec8b4700 (LWP 3239)]
[New Thread 0x7fffe7fff700 (LWP 3240)]
[Thread 0x7fffec8b4700 (LWP 3239) exited]

Program received signal SIGSEGV, Segmentation fault.
0x00007fffee13db44 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
(gdb) bt
#0 0x00007fffee13db44 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#1 0x00007fffee39c7c8 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#2 0x00007fffedf0cd83 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#3 0x00007fffee3a8060 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#4 0x00007fffedf18b91 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#5 0x00007fffee12bb10 in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#6 0x00007fffee10c74d in ?? ()
   from /usr/lib/nvidia-current/libnvidia-glcore.so.280.13
#7 0x00007fffef201561 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#8 0x00007fffef2071fe in ?? () from /usr/lib/nvidia-current/libGL.so.1
#9 0x0000000000415160 in ?? ()
#10 0x0000000000415ca8 in ?? ()
#11 0x000000000043412b in ?? ()
#12 0x000000000042eb2b in ?? ()
#13 0x00007ffff646e0a4 in g_closure_invoke ()

Revision history for this message
Jussi (jussi-lahtinen-gmail) wrote :

Video card is GeForce 8600 GT.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/919365/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → nvidia-graphics-drivers (Ubuntu)
Revision history for this message
Jussi (jussi-lahtinen-gmail) wrote :

Same binaries work in virtual machine with same OS, only difference seems to be video drivers.

Changed in nvidia-graphics-drivers (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
tags: added: xubuntu
Revision history for this message
Andrey (abelt) wrote :

Check if /tmp mounted as noexec. Nvidia proprietary drivers do not like that.

Revision history for this message
Jussi (jussi-lahtinen-gmail) wrote :

You are right, /tmp was mounted as noexec and removing it fixes the problem.

However I still think this is bug or at least new unwanted feature.
There shouldn't be any reason for video driver to execute anything from /tmp.

Thanks!

Revision history for this message
Jussi (jussi-lahtinen-gmail) wrote :

Of course crash itself is always bug...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.