Bug 866135

Summary: [abrt] nepomuk-core-4.9.2-5.fc17: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: daramas444
Component: nepomuk-coreAssignee: Jaroslav Reznik <jreznik>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: dct996, enzo.arlati, jreznik, kevin, ltinkl, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e66f6fbf50e708ad2ed9fec919a6a5030b0bc178
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 01:38:14 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: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: maps
none
File: build_ids
none
File: open_fds none

Description daramas444 2012-10-14 09:55:16 UTC 
Description of problem:
error obtained right after opening the session. seems to be reproducible by just rebooting and opening the session again

Version-Release number of selected component:
nepomuk-core-4.9.2-5.fc17

Additional info:
libreport version: 2.0.14
abrt_version:   2.0.13
backtrace_rating: 4
cmdline:        /usr/bin/nepomukservicestub nepomukstorage
crash_function: QCoreApplication::notifyInternal
kernel:         3.6.1-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #1 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:915
: #2 sendEvent at kernel/qcoreapplication.h:231
: #3 socketNotifierSourceDispatch at kernel/qeventdispatcher_glib.cpp:110
: #7 g_main_context_iteration at gmain.c:3207
: #8 QEventDispatcherGlib::processEvents at kernel/qeventdispatcher_glib.cpp:424
: #9 QEventLoop::processEvents at kernel/qeventloop.cpp:149
: #10 QEventLoop::exec at kernel/qeventloop.cpp:204
: #11 QThread::exec at thread/qthread.cpp:501
: #12 Soprano::Server::ServerConnection::run at /usr/src/debug/soprano-2.8.0/server/serverconnection.cpp:151
: #13 QThreadPrivate::start at thread/qthread_unix.cpp:307
Comment 1 daramas444 2012-10-14 09:55:19 UTC 
Created attachment 626850 [details]
File: environ
Comment 2 daramas444 2012-10-14 09:55:22 UTC 
Created attachment 626851 [details]
File: backtrace
Comment 3 daramas444 2012-10-14 09:55:24 UTC 
Created attachment 626852 [details]
File: limits
Comment 4 daramas444 2012-10-14 09:55:26 UTC 
Created attachment 626853 [details]
File: cgroup
Comment 5 daramas444 2012-10-14 09:55:30 UTC 
Created attachment 626854 [details]
File: maps
Comment 6 daramas444 2012-10-14 09:55:32 UTC 
Created attachment 626855 [details]
File: build_ids
Comment 7 daramas444 2012-10-14 09:55:35 UTC 
Created attachment 626856 [details]
File: open_fds
Comment 8 Fedora End Of Life 2013-07-03 23:11:30 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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 9 Fedora End Of Life 2013-08-01 01:38:19 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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