matrixview crashed with SIGSEGV in _fini()

Bug #556381 reported by jarek
6
Affects Status Importance Assigned to Milestone
rss-glx (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: rss-glx

?

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: rss-glx 0.9.0-2ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 6 12:23:58 2010
ExecutablePath: /usr/lib/xscreensaver/matrixview
ProcCmdline: matrixview -r
ProcEnviron:
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f12cf809a80: mov (%rax),%r12d
 PC (0x7f12cf809a80) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rss-glx
StacktraceTop:
 ?? () from /usr/lib/nvidia-current/libGL.so.1
 _fini () from /usr/lib/nvidia-current/libGL.so.1
 ?? () from /lib64/ld-linux-x86-64.so.2
 exit () from /lib/libc.so.6
 _XDefaultError () from /usr/lib/libX11.so.6
Title: matrixview crashed with SIGSEGV in _fini()
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mythtv plugdev sambashare video

Revision history for this message
jarek (syskom) wrote :
jarek (syskom)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /usr/lib/nvidia-current/libGL.so.1
 _fini () from /usr/lib/nvidia-current/libGL.so.1
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in rss-glx (Ubuntu):
status: New → 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.