nepomukserver crashed with SIGSEGV in write()

Bug #928745 reported by HughDaniel
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kde-runtime (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This bugreport was entirely generated by the bug catch&report softare from a failure that happened the second time
I booted Alpha2 (after a full set of upgrades) and the first time I has used this account (setup in the first boot session). I can't tell you anything more then I did the MOST simple install (nothing else worked...), an update/upgrade cycle (hand installing the kept back packages, ALL of them), created a second account and then rebooted and got the error indicator as soon as I was logged in.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kde-runtime 4:4.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Wed Feb 8 04:52:03 2012
ExecutablePath: /usr/bin/nepomukserver
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
ProcCmdline: /usr/bin/nepomukserver
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe432a41b53 <_ZN9QHashData14detach_helper2EPFvPNS_4NodeEPvEPFvS1_Eii+227>: mov (%rax,%rdx,8),%rbx
 PC (0x7fe432a41b53) ok
 source "(%rax,%rdx,8)" (0x00000041) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kde-runtime
StacktraceTop:
 write () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 exit () from /lib/x86_64-linux-gnu/libc.so.6
 __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
Title: nepomukserver crashed with SIGSEGV in write()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip fax floppy fuse local lpadmin operator plugdev root sambashare src staff sudo sys701 sys702 sys703 sys704 sys705 tape users uucp video voice www-data

Revision history for this message
HughDaniel (hugh-toad) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 write () at ../sysdeps/unix/syscall-template.S:82
 qt_safe_write (len=1, data=0x7fe432b8a593, fd=6) at ../../include/QtCore/private/../../../src/corelib/kernel/qcore_unix_p.h:262
 QProcessManager::~QProcessManager (this=0x7fe432e7b4e0, __in_chrg=<optimized out>) at io/qprocess_unix.cpp:209
 __run_exit_handlers (status=0, listp=0x7fe433fce5a8, run_list_atexit=true) at exit.c:78
 __GI_exit (status=<optimized out>) at exit.c:100

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in kde-runtime (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
tags: added: raring running-unity
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.