nepomukservicestub crashed with SIGSEGV in operator->()

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

Bug Description

nepomukservicestub crashed with SIGSEGV in operator->()

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nepomuk-core 4:4.9.0a-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic i686
ApportVersion: 2.5.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sat Aug 25 00:59:29 2012
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120627)
ProcCmdline: /usr/bin/nepomukservicestub nepomukfilewatch
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb74cb1f4 <QDirIterator::hasNext() const+4>: mov 0x4(%eax),%eax
 PC (0xb74cb1f4) ok
 source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nepomuk-core
StacktraceTop:
 operator-> (this=0x4) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:113
 QDirIterator::hasNext (this=0x0) at io/qdiriterator.cpp:508
 ?? () from /usr/lib/kde4/nepomukfilewatch.so
 ?? () from /usr/lib/kde4/nepomukfilewatch.so
 QMetaCallEvent::placeMetaCall (this=0x8803fb8, object=0x836cbc8) at kernel/qobject.cpp:525
Title: nepomukservicestub crashed with SIGSEGV in operator->()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Simon Andric (simonandric5) wrote :
visibility: private → public
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 #1040921, 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.

tags: removed: need-i386-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.