Version-Release number of selected component: PackageKit-0.9.1-1.fc21 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: check_transfer_statuses executable: /usr/libexec/packagekitd kernel: 3.15.0-0.rc0.git9.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #1 check_transfer_statuses at /lib64/librepo.so.0 #2 lr_download at /lib64/librepo.so.0 #3 lr_download_single_cb at /lib64/librepo.so.0 #4 lr_yum_perform at /lib64/librepo.so.0 #5 lr_handle_perform at /lib64/librepo.so.0 #6 hif_source_update at /usr/lib64/packagekit-backend/libpk_backend_hawkey.so #7 hif_sack_add_source at /usr/lib64/packagekit-backend/libpk_backend_hawkey.so #8 hif_sack_add_sources at /usr/lib64/packagekit-backend/libpk_backend_hawkey.so #9 hif_utils_create_sack_for_filters at /usr/lib64/packagekit-backend/libpk_backend_hawkey.so #10 pk_backend_search_thread at /usr/lib64/packagekit-backend/libpk_backend_hawkey.so
Created attachment 884348 [details] File: backtrace
Created attachment 884349 [details] File: cgroup
Created attachment 884350 [details] File: core_backtrace
Created attachment 884351 [details] File: dso_list
Created attachment 884352 [details] File: environ
Created attachment 884353 [details] File: exploitable
Created attachment 884354 [details] File: limits
Created attachment 884355 [details] File: maps
Created attachment 884356 [details] File: open_fds
Created attachment 884357 [details] File: proc_pid_status
Created attachment 884358 [details] File: var_log_messages
Looks like a librepo crash. Reassigning.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
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.