nepomukservicestub crashed with SIGSEGV in isEmpty()

Bug #1054551 reported by Chris Samuel
24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nepomuk-core (Ubuntu)
Medium
Unassigned

Bug Description

Logs SEGV's whenever I login, but I can't see any context for what it was trying to index at the time.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nepomuk-core 4:4.9.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 22 21:41:55 2012
ExecutablePath: /usr/bin/nepomukservicestub
ProcCmdline: /usr/bin/nepomukservicestub nepomukfilewatch
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff56f4b3584: movslq 0x8(%rax),%rdx
 PC (0x7ff56f4b3584) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nepomuk-core
StacktraceTop:
 ?? () from /usr/lib/kde4/nepomukfilewatch.so
 ?? () from /usr/lib/kde4/nepomukfilewatch.so
 QObject::event (this=0x1ee6040, e=<optimised out>) at kernel/qobject.cpp:1195
 QApplicationPrivate::notify_helper (this=this@entry=0x1d3e500, receiver=receiver@entry=0x1ee6040, e=e@entry=0xae566d0) at kernel/qapplication.cpp:4562
 QApplication::notify (this=0x7fff95f63170, receiver=0x1ee6040, e=0xae566d0) at kernel/qapplication.cpp:4423
Title: nepomukservicestub crashed with SIGSEGV in QObject::event()
UpgradeStatus: Upgraded to quantal on 2012-09-22 (0 days ago)
UserGroups: adm admin audio cdrom dialout dip disk floppy lpadmin mythtv netdev plugdev powerdev sambashare scanner video

Revision history for this message
Chris Samuel (chris-csamuel) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 isEmpty (this=0x1ee6118) at /usr/include/qt4/QtCore/qlist.h:99
 isEmpty (this=0x1ee6118) at /usr/include/qt4/QtCore/qlist.h:152
 KInotify::Private::_k_addWatches (this=0x1ee6100) at ../../../services/filewatch/kinotify.cpp:147
 qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./kinotify.moc:96
 KInotify::qt_static_metacall (_o=0x0, _c=QMetaObject::ReadProperty, _id=2046453505, _a=0xae44e20) at ./kinotify.moc:72

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
summary: - nepomukservicestub crashed with SIGSEGV in QObject::event()
+ nepomukservicestub crashed with SIGSEGV in isEmpty()
tags: removed: 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
information type: Private → Public
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!

Changed in nepomuk-core (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers