nepomukservicestub crashed with SIGSEGV in QDirIterator::hasNext()

Bug #1034985 reported by R3vo tester
78
This bug affects 12 people
Affects Status Importance Assigned to Milestone
kde4libs (Ubuntu)
Invalid
Medium
R3vo tester

Bug Description

nepomukservicestub crashed with SIGSEGV in QDirIterator::hasNext() Bug on Linux Ubuntu 12.10 quantal.

I use Ubuntu 12.10 quantal with KDE desktop (kubuntu-desktop) package

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nepomuk-core 4:4.9.0a-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 9 16:53:21 2012
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120805.1)
ProcCmdline: /usr/bin/nepomukservicestub nepomukfilewatch
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb8251f2820 <_ZNK12QDirIterator7hasNextEv>: mov 0x8(%rdi),%rax
 PC (0x7fb8251f2820) ok
 source "0x8(%rdi)" (0x00000049) 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
R3vo tester (anas-barcawi) wrote :
description: updated
visibility: private → public
description: updated
description: updated
Changed in nepomuk-core (Ubuntu):
assignee: nobody → R3vo tester (anas-barcawi)
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 QDirIterator::hasNext() const () from /tmp/tmpVs_3tU/usr/lib/x86_64-linux-gnu/libQtCore.so.4
 KInotify::Private::_k_addWatches (this=0x2592910) at ../../../services/filewatch/kinotify.cpp:149
 qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./kinotify.moc:96
 KInotify::qt_static_metacall (_o=0x41, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x24d32d0) at ./kinotify.moc:72
 QObject::event(QEvent*) () from /tmp/tmpVs_3tU/usr/lib/x86_64-linux-gnu/libQtCore.so.4

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nepomuk-core (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
R3vo tester (anas-barcawi) wrote :

need-amd64-retrace ?

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nepomuk-core (Ubuntu):
status: New → Confirmed
Revision history for this message
Rohan Garg (rohangarg) wrote :

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

affects: nepomuk-core (Ubuntu) → kde4libs (Ubuntu)
Changed in kde4libs (Ubuntu):
status: Confirmed → Invalid
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.