nepomukserver crashed with SIGSEGV in write()

Bug #1112168 reported by Charles Lease
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nepomuk-core (Ubuntu)
New
Undecided
Unassigned

Bug Description

Booted into KDE and got message that nepomuk search indexing crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nepomuk-core 4:4.9.98-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-3.7-generic 3.8.0-rc5
Uname: Linux 3.8.0-3-generic x86_64
ApportVersion: 2.8-0ubuntu3
Architecture: amd64
Date: Fri Feb 1 01:01:51 2013
ExecutablePath: /usr/bin/nepomukserver
InstallationDate: Installed on 2013-01-18 (14 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130117)
MarkForUpload: True
ProcCmdline: /usr/bin/nepomukserver
ProcEnviron:
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f956438790c <_ZN9QHashData14detach_helper2EPFvPNS_4NodeEPvEPFvS1_Eii+236>: mov (%rax,%rdx,8),%rbx
 PC (0x7f956438790c) 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: nepomuk-core
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 cdrom debian-tor dip lpadmin plugdev sambashare sudo

Revision history for this message
Charles Lease (mellowchuck-y) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #928745, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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