Bug 1093520

Summary: [abrt] PackageKit: hy_repo_get_string(): packagekitd killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Alan Schmidt <bucky>
Component: PackageKitAssignee: Richard Hughes <rhughes>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: bucky, bztdlinux, iweiss, jonathan, rdieter, rhughes, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b12da7259532bbfaa23340d58cdc79f4a4857507
Whiteboard: abrt_hash:4bf57b0ad8c1bbf81d1c56af0dd3c5c54a4404b4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:24:21 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Alan Schmidt 2014-05-02 00:37:41 UTC 
Description of problem:
Switched to hawkey backend recently. I know it's experimental.

Clicked on gear icon and agreed to an update. Crash came soon afterward.

Version-Release number of selected component:
PackageKit-0.8.17-1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: hy_repo_get_string
executable:     /usr/libexec/packagekitd
kernel:         3.13.10-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 hy_repo_get_string at /usr/src/debug/hawkey/py3/src/repo.c:156
 #1 load_yum_repo at /usr/src/debug/hawkey/py3/src/sack.c:538
 #2 hy_sack_load_yum_repo at /usr/src/debug/hawkey/py3/src/sack.c:916
 #3 hif_sack_add_source at hif-sack.c:101
 #4 hif_sack_add_sources at hif-sack.c:151
 #5 hif_utils_add_remote at pk-backend-hawkey.c:596
 #6 hif_utils_create_sack_for_filters at pk-backend-hawkey.c:721
 #7 pk_backend_update_packages_thread at pk-backend-hawkey.c:3863
 #8 pk_backend_job_thread_setup at pk-backend-job.c:792
 #9 g_thread_proxy at gthread.c:798

Potential duplicate: bug 1066170
Comment 1 Alan Schmidt 2014-05-02 00:37:44 UTC 
Created attachment 891660 [details]
File: backtrace
Comment 2 Alan Schmidt 2014-05-02 00:37:45 UTC 
Created attachment 891661 [details]
File: cgroup
Comment 3 Alan Schmidt 2014-05-02 00:37:46 UTC 
Created attachment 891662 [details]
File: core_backtrace
Comment 4 Alan Schmidt 2014-05-02 00:37:48 UTC 
Created attachment 891663 [details]
File: dso_list
Comment 5 Alan Schmidt 2014-05-02 00:37:49 UTC 
Created attachment 891664 [details]
File: environ
Comment 6 Alan Schmidt 2014-05-02 00:37:50 UTC 
Created attachment 891665 [details]
File: exploitable
Comment 7 Alan Schmidt 2014-05-02 00:37:52 UTC 
Created attachment 891666 [details]
File: limits
Comment 8 Alan Schmidt 2014-05-02 00:37:54 UTC 
Created attachment 891667 [details]
File: maps
Comment 9 Alan Schmidt 2014-05-02 00:37:55 UTC 
Created attachment 891668 [details]
File: open_fds
Comment 10 Alan Schmidt 2014-05-02 00:37:56 UTC 
Created attachment 891669 [details]
File: proc_pid_status
Comment 11 Alan Schmidt 2014-05-02 00:37:58 UTC 
Created attachment 891670 [details]
File: var_log_messages
Comment 12 Alan Schmidt 2014-07-01 16:08:13 UTC 
Another user experienced a similar problem:

Logged in this morning, and got an error automagically.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: hy_repo_get_string
executable:     /usr/libexec/packagekitd
kernel:         3.14.9-200.fc20.x86_64
package:        PackageKit-0.8.17-1.fc20
reason:         packagekitd killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            0
Comment 13 Fedora End Of Life 2015-05-29 11:44:02 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 14 Fedora End Of Life 2015-06-29 20:24:21 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.