[nvidia] elisa crashed with SIGSEGV in glXSwapBuffers()

Bug #286130 reported by robsstartrek
4
Affects Status Importance Assigned to Milestone
elisa (Ubuntu)
Invalid
Undecided
Tormod Volden

Bug Description

Binary package hint: elisa

playing anime frame moving etc

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/elisa
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
Package: elisa 0.5.9-1-1ubuntu2
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/bin/elisa
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: elisa
StacktraceTop:
 ?? () from /usr/lib/libGL.so.1
 glXSwapBuffers () from /usr/lib/libGL.so.1
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch ()
Title: elisa crashed with SIGSEGV in glXSwapBuffers()
Uname: Linux 2.6.27-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
robsstartrek (robs-startrek) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /usr/lib/libGL.so.1
glXSwapBuffers () from /usr/lib/libGL.so.1
?? () from /usr/lib/pigment-0.3/0.3.7/libpgmopengl.so
?? () from /usr/lib/libglib-2.0.so.0
g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Thanks for your report. It looks like a bug in the proprietary nvidia libraries. Is this still an issue with updated nvidia drivers?

Changed in elisa:
assignee: nobody → tormodvolden
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in elisa:
status: Incomplete → Invalid
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.