Bug 991194

Summary: [abrt] PackageKit-0.8.10-1.fc20: pk_backend_job_error_code: Process /usr/libexec/packagekitd was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Saurabh Pradhan <pradhanphy>
Component: PackageKitAssignee: Richard Hughes <rhughes>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: jonathan, kalevlember, pradhanphy, rdieter, rhughes, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f2094a4d3b9cc0096fff971f6d9d917bf9046b3b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-09 00:13:41 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: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Saurabh Pradhan 2013-08-01 19:44:07 UTC
Version-Release number of selected component:
PackageKit-0.8.10-1.fc20

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: pk_backend_job_error_code
executable:     /usr/libexec/packagekitd
kernel:         3.9.5-301.fc19.x86_64
runlevel:       N 5
uid:            0

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 pk_backend_job_error_code at pk-backend-job.c:1776
 #1 pk_backend_spawn_exit_cb at pk-backend-spawn.c:639
 #2 g_cclosure_marshal_VOID__INTv at gmarshal.c:410
 #3 _g_closure_invoke_va at gclosure.c:840
 #6 pk_spawn_check_child at pk-spawn.c:290

Comment 1 Saurabh Pradhan 2013-08-01 19:44:15 UTC
Created attachment 781731 [details]
File: backtrace

Comment 2 Saurabh Pradhan 2013-08-01 19:44:19 UTC
Created attachment 781732 [details]
File: cgroup

Comment 3 Saurabh Pradhan 2013-08-01 19:44:24 UTC
Created attachment 781733 [details]
File: core_backtrace

Comment 4 Saurabh Pradhan 2013-08-01 19:44:32 UTC
Created attachment 781734 [details]
File: dso_list

Comment 5 Saurabh Pradhan 2013-08-01 19:44:36 UTC
Created attachment 781735 [details]
File: environ

Comment 6 Saurabh Pradhan 2013-08-01 19:44:40 UTC
Created attachment 781736 [details]
File: limits

Comment 7 Saurabh Pradhan 2013-08-01 19:44:46 UTC
Created attachment 781737 [details]
File: maps

Comment 8 Saurabh Pradhan 2013-08-01 19:44:51 UTC
Created attachment 781738 [details]
File: open_fds

Comment 9 Saurabh Pradhan 2013-08-01 19:44:55 UTC
Created attachment 781739 [details]
File: proc_pid_status

Comment 10 Saurabh Pradhan 2013-08-01 19:45:01 UTC
Created attachment 781740 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2013-09-16 14:58:25 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 12 Richard Hughes 2013-12-11 09:20:32 UTC
Can you reproduce this?

Comment 13 Saurabh Pradhan 2013-12-11 11:38:01 UTC
I have update to recent rwahide. 
Not able to reproduce

Comment 14 Fedora End Of Life 2015-05-29 09:14:11 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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 15 Kalev Lember 2015-06-09 00:13:41 UTC
Closing as per comment #13.