kdeinit4 crashed with SIGSEGV in QMutex::lock()

[Simone Tolotti]

I don't know what caused this crash. AFAIK this caused no issue at user level.

ProblemType: Crash
Architecture: amd64
Date: Tue Oct 13 18:54:13 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdeinit4
NonfreeKernelModules: nvidia
Package: kdelibs-bin 4:4.3.2-0ubuntu4
ProcCmdline: kdeinit4:\ krita\ [kdeinit]\ /home/username/Documenti/cartella.png
ProcEnviron:
 LANGUAGE=it_IT:it:en_GB:en
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SegvAnalysis:
 Segfault happened at: 0x7faad7069739 <_ZN6QMutex4lockEv+9>: mov (%rdi),%rdx
 PC (0x7faad7069739) ok
 source "(%rdi)" (0x00000098) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kde4libs
StacktraceTop:
 QMutex::lock() () from /usr/lib/libQtCore.so.4
 QMetaObject::activate(QObject*, int, int, void**) ()
 QAbstractItemView::activated(QModelIndex const&) ()
 QAbstractItemView::mouseReleaseEvent(QMouseEvent*)
 QWidget::event(QEvent*) ()
Title: kdeinit4 crashed with SIGSEGV in QMutex::lock()
Uname: Linux 2.6.31-13-generic x86_64
UserGroups: adm admin cdrom dialout fax floppy lpadmin plugdev sambashare syslog

[Jonathan Thomas (echidnaman)]

Unfortunately the backtrace is not complete enough to debug this properly. Since we don't know what caused the bug in the first place, I don't think there's much we can do about it. Thanks for reporting it all the same.