Bug 1209020

Summary: [abrt] kf5-kactivities: exit(): kactivitymanagerd killed by SIGSEGV
Product: [Fedora] Fedora Reporter: supamaxy
Component: kf5-kactivitiesAssignee: KDE SIG <kde-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: akurtako, bucky, danofsatx, facorread, jgrulich, kevin, ncross, pahan, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/6f0227f8acebe5233fd828436dbe1b3f72895c2c
Whiteboard: abrt_hash:5460eaed9d6da5b99965806fc7d47066833a8c8a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 13:38:09 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: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status none

Description supamaxy 2015-04-05 09:23:17 UTC 
Version-Release number of selected component:
kf5-kactivities-5.8.0-1.fc22

Additional info:
reporter:       libreport-2.5.0
backtrace_rating: 4
cmdline:        /usr/bin/kactivitymanagerd start-daemon
crash_function: exit
executable:     /usr/bin/kactivitymanagerd
global_pid:     6123
kernel:         4.0.0-0.rc5.git4.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
var_log_messages: [System Logs]:\n-- Logs begin at Sat 2015-03-28 22:36:44 EET, end at Thu 2015-04-02 16:03:14 EEST. --

Truncated backtrace:
Thread no. 1 (10 frames)
 #12 exit at exit.c:104
 #13 _IceDefaultIOErrorHandler at error.c:603
 #14 _IceRead at misc.c:292
 #15 IceProcessMessages at process.c:196
 #16 QMetaObject::activate at kernel/qobject.cpp:3716
 #18 QSocketNotifier::activated at .moc/moc_qsocketnotifier.cpp:133
 #19 QSocketNotifier::event at kernel/qsocketnotifier.cpp:296
 #20 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3720
 #21 QApplication::notify at kernel/qapplication.cpp:3503
 #22 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:935
Comment 1 supamaxy 2015-04-05 09:23:20 UTC 
Created attachment 1011078 [details]
File: backtrace
Comment 2 supamaxy 2015-04-05 09:23:21 UTC 
Created attachment 1011079 [details]
File: cgroup
Comment 3 supamaxy 2015-04-05 09:23:23 UTC 
Created attachment 1011080 [details]
File: core_backtrace
Comment 4 supamaxy 2015-04-05 09:23:24 UTC 
Created attachment 1011081 [details]
File: dso_list
Comment 5 supamaxy 2015-04-05 09:23:26 UTC 
Created attachment 1011082 [details]
File: environ
Comment 6 supamaxy 2015-04-05 09:23:27 UTC 
Created attachment 1011083 [details]
File: limits
Comment 7 supamaxy 2015-04-05 09:23:29 UTC 
Created attachment 1011084 [details]
File: maps
Comment 8 supamaxy 2015-04-05 09:23:30 UTC 
Created attachment 1011085 [details]
File: mountinfo
Comment 9 supamaxy 2015-04-05 09:23:31 UTC 
Created attachment 1011086 [details]
File: namespaces
Comment 10 supamaxy 2015-04-05 09:23:32 UTC 
Created attachment 1011087 [details]
File: open_fds
Comment 11 supamaxy 2015-04-05 09:23:34 UTC 
Created attachment 1011088 [details]
File: proc_pid_status
Comment 12 Daniel Vrátil 2015-07-16 12:13:53 UTC 
*** Bug 1210559 has been marked as a duplicate of this bug. ***
Comment 13 Alan Schmidt 2015-10-31 00:53:43 UTC 
Problem persists in FC23 beta as of this date and time.
Comment 16 Fedora End Of Life 2016-07-19 13:38:09 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.