nepomukservicestub crashed with SIGSEGV in QObject::event()

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

Bug Description

I was away from computer, so no more information available.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nepomuk-core 4:4.9.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Tue Oct 2 15:21:12 2012
ExecutablePath: /usr/bin/nepomukservicestub
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
ProcCmdline: /usr/bin/nepomukservicestub nepomukfilewatch
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbd02837584: movslq 0x8(%rax),%rdx
 PC (0x7fbd02837584) 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=0x1640c00, e=<optimized out>) at kernel/qobject.cpp:1195
 QApplicationPrivate::notify_helper (this=this@entry=0x1454810, receiver=receiver@entry=0x1640c00, e=e@entry=0x11d7e4f0) at kernel/qapplication.cpp:4562
 QApplication::notify (this=0x7fff0a1d2d80, receiver=0x1640c00, e=0x11d7e4f0) at kernel/qapplication.cpp:4423
Title: nepomukservicestub crashed with SIGSEGV in QObject::event()
UpgradeStatus: Upgraded to quantal on 2012-09-10 (22 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
opi (opi-gmx) 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 #1054551, 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.