Bug 902562

Summary: [abrt] nepomuk-core-4.9.5-1.fc18: QObject::~QObject: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: hitman2 <hit_man2>
Component: nepomuk-coreAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dew, jreznik, kevin, ltinkl, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6abac3ff4f793402fc8eb12e30551a064c3d681b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 15:34:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description hitman2 2013-01-21 23:59:40 UTC 
Version-Release number of selected component:
nepomuk-core-4.9.5-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/nepomukservicestub nepomukstorage
crash_function: QObject::~QObject
executable:     /usr/bin/nepomukservicestub
kernel:         3.7.2-204.fc18.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 QObject::~QObject at kernel/qobject.cpp:853
 #3 signalHandler at /usr/src/debug/nepomuk-core-4.9.5/servicestub/main.cpp:51
 #4 (anonymous namespace)::signalHandler at /usr/src/debug/nepomuk-core-4.9.5/servicestub/main.cpp:45
 #6 poll at ../sysdeps/unix/syscall-template.S:81
 #8 qt_safe_poll at kernel/qcore_unix.cpp:150
 #9 poll at io/qprocess_unix.cpp:1060
 #10 QProcessPrivate::waitForFinished at io/qprocess_unix.cpp:1183
 #11 QProcess::waitForFinished at io/qprocess.cpp:1759
 #12 Soprano::VirtuosoController::shutdown at /usr/src/debug/soprano-2.8.0/backends/virtuoso/virtuosocontroller.cpp:219
 #13 Soprano::VirtuosoController::~VirtuosoController at /usr/src/debug/soprano-2.8.0/backends/virtuoso/virtuosocontroller.cpp:89

Potential duplicate: bug 861517
Comment 1 hitman2 2013-01-21 23:59:44 UTC 
Created attachment 684704 [details]
File: backtrace
Comment 2 hitman2 2013-01-21 23:59:46 UTC 
Created attachment 684705 [details]
File: build_ids
Comment 3 hitman2 2013-01-21 23:59:48 UTC 
Created attachment 684706 [details]
File: cgroup
Comment 4 hitman2 2013-01-21 23:59:50 UTC 
Created attachment 684707 [details]
File: core_backtrace
Comment 5 hitman2 2013-01-21 23:59:52 UTC 
Created attachment 684708 [details]
File: environ
Comment 6 hitman2 2013-01-21 23:59:54 UTC 
Created attachment 684709 [details]
File: limits
Comment 7 hitman2 2013-01-21 23:59:56 UTC 
Created attachment 684710 [details]
File: maps
Comment 8 hitman2 2013-01-21 23:59:59 UTC 
Created attachment 684711 [details]
File: open_fds
Comment 9 hitman2 2013-01-22 00:00:01 UTC 
Created attachment 684712 [details]
File: proc_pid_status
Comment 10 Donald Edward Winslow 2013-03-05 03:36:23 UTC 
I installed updates, rebooted, and logged back into KDE.

backtrace_rating: 4
Package: nepomuk-core-4.9.5-1.fc18
OS Release: Fedora release 18 (Spherical Cow)
Comment 11 Fedora End Of Life 2013-12-21 10:40:50 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 12 Fedora End Of Life 2014-02-05 15:34:57 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.