nepomukservicestub crashed with SIGSEGV in QDirIterator::hasNext()

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

Bug Description

I closed kraft soon after opening it, and this crash occurred.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nepomuk-core 4:4.9.0a-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Mon Sep 3 15:42:01 2012
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120821)
ProcCmdline: /usr/bin/nepomukservicestub nepomukfilewatch
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=
SegvAnalysis:
 Segfault happened at: 0x7f6c754177d0 <_ZNK12QDirIterator7hasNextEv>: mov 0x8(%rdi),%rax
 PC (0x7f6c754177d0) ok
 source "0x8(%rdi)" (0x00000039) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nepomuk-core
StacktraceTop:
 QDirIterator::hasNext() const () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/kde4/nepomukfilewatch.so
 ?? () from /usr/lib/kde4/nepomukfilewatch.so
 QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
Title: nepomukservicestub crashed with SIGSEGV in QDirIterator::hasNext()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Logan Rosen (logan) 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 #1044429, 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.

visibility: 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.