stellarium crashed with SIGSEGV in QReadWriteLock::lockForWrite()

[Alejandro Cuervo]

Binary package hint: stellarium

on latest maverick

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: stellarium 0.10.5-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Sep 30 12:50:50 2010
ExecutablePath: /usr/bin/stellarium
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: stellarium
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbd06246389 <_ZN14QReadWriteLock12lockForWriteEv+9>: mov (%rdi),%rsi
 PC (0x7fbd06246389) ok
 source "(%rdi)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: stellarium
StacktraceTop:
 QReadWriteLock::lockForWrite() () from /usr/lib/libQtCore.so.4
 ?? () from /usr/lib/libQtOpenGL.so.4
 QGLContext::deleteTexture(unsigned int) () from /usr/lib/libQtOpenGL.so.4
 StelTexture::~StelTexture() ()
 QSharedPointer<StelTexture>::~QSharedPointer() ()
Title: stellarium crashed with SIGSEGV in QReadWriteLock::lockForWrite()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video

[Alejandro Cuervo (a-cuervo)]

I think this may be QT related

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.