nepomukservicestub crashed with SIGSEGV in malloc()

Bug #638851 reported by Roman Vatamanyuk on 2010-09-15
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kdebase-runtime (Ubuntu)

Bug Description

Binary package hint: kdebase-runtime

nepomukservicestub crashed with SIGSEGV in malloc()

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: kdebase-runtime 4:4.5.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-21.31-generic
Uname: Linux 2.6.35-21-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Sep 15 13:12:49 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
 Segfault happened at: 0x938939: call 0x8e0b1f
 PC (0x00938939) ok
 source "0x8e0b1f" (0x008e0b1f) ok
 destination "(%esp)" (0xb1945ffc) in non-writable VMA region: 0xb1945000-0xb1946000 ---p None
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA None
Signal: 11
SourcePackage: kdebase-runtime
 ?? () from /lib/
 malloc () from /lib/
 operator new(unsigned int) () from /usr/lib/
 QMutex::QMutex(QMutex::RecursionMode) () from /usr/lib/
 ?? () from /usr/lib/
Title: nepomukservicestub crashed with SIGSEGV in malloc()
UserGroups: adm admin cdrom dialout fax floppy lpadmin netdev plugdev sambashare saned syslog
XsessionErrors: (process:1729): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Roman Vatamanyuk (vatamanyuk) wrote :

 _int_malloc (av=0xa253c0, bytes=96) at malloc.c:4249
 *__GI___libc_malloc (bytes=96) at malloc.c:3660
 operator new () from /usr/lib/
 QMutex::QMutex () from /usr/lib/
 ?? () from /usr/lib/

Changed in kdebase-runtime (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Launchpad Janitor (janitor) wrote :

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

Changed in kdebase-runtime (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers