nepomukservicestub crashed with SIGSEGV in QMutex::lock()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdebase-runtime (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: kdebase-runtime
crashes on reboot
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: kdebase-runtime 4:4.4.2-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.32-20-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Apr 14 16:53:34 2010
ExecutablePath: /usr/bin/
InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100414)
ProcCmdline: /usr/bin/
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
LANGUAGE=
SegvAnalysis:
Segfault happened at: 0x7fd18a8e08dc <_ZN6QMutex4loc
PC (0x7fd18a8e08dc) ok
source "$0x0" ok
destination "(%rdx)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: kdebase-runtime
StacktraceTop:
QMutex::lock() () from /usr/lib/
?? () from /usr/lib/
QThreadStorage
?? () from /usr/lib/
QApplication:
Title: nepomukservicestub crashed with SIGSEGV in QMutex::lock()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (process:2214): GLib-CRITICAL **: g_once_init_leave: assertion `initialization
visibility: | private → public |
This crash has the same stack trace characteristics as bug #528235. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.