Bug 917617

Summary: [abrt] nepomuk-core-4.9.5-1.fc18: QCoreApplication::notifyInternal: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dan <dan.pannell>
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: jreznik, kevin, ltinkl, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:3e330365d7704d57157f1664e33fd2a38f861242
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 19:37:49 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 Dan 2013-03-04 12:17:56 UTC 
Description of problem:
This problem happened upon boot-up and logging in.  I do not know what the problem was or
what neomuk is. 

 This system duel-boots with MS-Windows 7.  RPM-Fusion (free and non-free are enabled)

I recently created a chroot directory using Yum.

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: QCoreApplication::notifyInternal
executable:     /usr/bin/nepomukservicestub
kernel:         3.7.9-205.fc18.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #1 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:946
 #2 sendEvent at kernel/qcoreapplication.h:231
 #3 socketNotifierSourceDispatch at kernel/qeventdispatcher_glib.cpp:110
 #7 g_main_context_iteration at gmain.c:3351
 #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:542
 #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:338

Potential duplicate: bug 861338
Comment 1 Dan 2013-03-04 12:18:00 UTC 
Created attachment 704922 [details]
File: backtrace
Comment 2 Dan 2013-03-04 12:18:03 UTC 
Created attachment 704923 [details]
File: build_ids
Comment 3 Dan 2013-03-04 12:18:05 UTC 
Created attachment 704924 [details]
File: cgroup
Comment 4 Dan 2013-03-04 12:18:07 UTC 
Created attachment 704925 [details]
File: core_backtrace
Comment 5 Dan 2013-03-04 12:18:09 UTC 
Created attachment 704926 [details]
File: environ
Comment 6 Dan 2013-03-04 12:18:10 UTC 
Created attachment 704927 [details]
File: limits
Comment 7 Dan 2013-03-04 12:18:13 UTC 
Created attachment 704928 [details]
File: maps
Comment 8 Dan 2013-03-04 12:18:15 UTC 
Created attachment 704929 [details]
File: open_fds
Comment 9 Dan 2013-03-04 12:18:28 UTC 
Created attachment 704930 [details]
File: proc_pid_status
Comment 10 Fedora End Of Life 2013-12-21 11:50:53 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 11 Fedora End Of Life 2014-02-05 19:37:49 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.