Bug 234823 - crash in kdebase-runtime-4.4.2-1.fc12: Process /usr/bin/nepomukservicestub was killed by signal 11
Summary: crash in kdebase-runtime-4.4.2-1.fc12: Process /usr/bin/nepomukservicestub wa...
Status: RESOLVED FIXED
Alias: None
Product: nepomuk
Classification: Miscellaneous
Component: storage (show other bugs)
Version: 4.4
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-19 18:06 UTC by Christoph Wickert
Modified: 2012-11-30 01:45 UTC (History)
2 users (show)

See Also:
Latest Commit: 844b7c6212e5805f0f2bd885adec451c6043d76e
Version Fixed In: 4.5.1

Attachments
backtrace of the crash (31.78 KB, text/plain)
2010-04-19 18:07 UTC, Christoph Wickert 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Wickert 2010-04-19 18:06:07 UTC 
Version:           kdebase-runtime-4.4.2-1.fc12.x86_64 (using KDE 4.4.2)
Compiler:          gcc-4.4.3-4.fc12.x86_64 
OS:                Linux
Installed from:    Fedora RPMs

Forwarded from https://bugzilla.redhat.com/show_bug.cgi?id=583749

abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstorage
comment: I didn't actually do anything, I wasn't even at my computer when this
crash appeared. Kontact was the only KDE app running and AFAICS it still works
as usual.
component: kdebase-runtime
executable: /usr/bin/nepomukservicestub
kernel: 2.6.32.11-99.fc12.x86_64
package: kdebase-runtime-4.4.2-1.fc12
rating: 4
reason: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
How to reproduce: 1. Do nothing
Comment 1 Christoph Wickert 2010-04-19 18:07:06 UTC 
Created attachment 42901 [details]
backtrace of the crash
Comment 2 Simeon Bird 2012-11-30 01:45:42 UTC 
This looks like a crash on deletion of Nepomuk::Service::Private::MainModel in nepomukservice.cpp, which no longer exists since commit 844b7c6212e5805f0f2bd885adec451c6043d76e

Thus, this should be fixed.