Bug 927091

Summary: [abrt] nepomuk-core-4.10.1-1.fc18: _dbus_abort: Process /usr/bin/nepomukserver was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Carlos Rodríguez <informatic.0912>
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, mlportersr, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:bcebeb84be85a174b9252523a299ab63da5d37cf
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 20:16:30 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: cgroup
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Carlos Rodríguez 2013-03-25 04:12:07 UTC
Version-Release number of selected component:
nepomuk-core-4.10.1-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
core_backtrace: 
crash_function: _dbus_abort
executable:     /usr/bin/nepomukserver
kernel:         3.8.3-203.fc18.i686
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #3 _dbus_abort at dbus-sysdeps.c:94
 #4 _dbus_warn_check_failed at dbus-internals.c:290
 #5 dbus_pending_call_unref at dbus-pending-call.c:608
 #6 q_dbus_pending_call_unref at qdbus_symbols_p.h:317
 #7 QDBusPendingCallPrivate::~QDBusPendingCallPrivate at qdbuspendingcall.cpp:137
 #8 ~QExplicitlySharedDataPointer at ../../src/corelib/tools/qshareddata.h:166
 #9 QDBusPendingCall::~QDBusPendingCall at qdbuspendingcall.cpp:271
 #10 QDBusPendingReplyData::~QDBusPendingReplyData at qdbuspendingreply.cpp:246
 #11 ~QDBusPendingReply at /usr/include/QtDBus/qdbuspendingreply.h:115
 #12 Nepomuk2::ServiceController::stop at /usr/src/debug/nepomuk-core-4.10.1/server/servicecontroller.cpp:226

Potential duplicate: bug 873973

Comment 1 Carlos Rodríguez 2013-03-25 04:12:11 UTC
Created attachment 715832 [details]
File: backtrace

Comment 2 Carlos Rodríguez 2013-03-25 04:12:13 UTC
Created attachment 715833 [details]
File: cgroup

Comment 3 Carlos Rodríguez 2013-03-25 04:12:15 UTC
Created attachment 715834 [details]
File: environ

Comment 4 Carlos Rodríguez 2013-03-25 04:12:17 UTC
Created attachment 715835 [details]
File: limits

Comment 5 Carlos Rodríguez 2013-03-25 04:12:19 UTC
Created attachment 715836 [details]
File: maps

Comment 6 Carlos Rodríguez 2013-03-25 04:12:22 UTC
Created attachment 715837 [details]
File: open_fds

Comment 7 Carlos Rodríguez 2013-03-25 04:12:24 UTC
Created attachment 715838 [details]
File: proc_pid_status

Comment 8 Mike Porter 2013-04-26 03:20:18 UTC
I restarted the computer after the latest updates

backtrace_rating: 4
cmdline:        /usr/bin/nepomukserver
core_backtrace: 
crash_function: _dbus_abort
executable:     /usr/bin/nepomukserver
kernel:         3.8.8-202.fc18.i686
package:        nepomuk-core-4.10.2-2.fc18
reason:         Process /usr/bin/nepomukserver was killed by signal 6 (SIGABRT)
reported_to:    uReport: BTHASH=e8c5d5a3009974ca4717d465e8a1b3d5d964df4d
uid:            1000
ureports_counter: 2

Comment 9 Fedora End Of Life 2013-12-21 12:27:25 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 10 Fedora End Of Life 2014-02-05 20:16:30 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.