Description of problem: Not sure what's triggering this, but it seems to be preventing GNOME Software from working correctly on my F22 laptop. Version-Release number of selected component: PackageKit-1.0.6-6.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: hy_repo_get_string executable: /usr/libexec/packagekitd global_pid: 1815 kernel: 4.1.3-201.fc22.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-0.5.7/py3/src/repo.c:200 #1 load_yum_repo at /usr/src/debug/hawkey-0.5.7/py3/src/sack.c:552 #2 hy_sack_load_repo at /usr/src/debug/hawkey-0.5.7/py3/src/sack.c:999 #3 hy_sack_load_yum_repo at /usr/src/debug/hawkey-0.5.7/py3/src/sack.c:992 #4 hif_sack_add_source at hif-sack.c:148 #5 hif_sack_add_sources at hif-sack.c:201 #6 hif_utils_add_remote at pk-backend-hif.c:490 #7 hif_utils_create_sack_for_filters at pk-backend-hif.c:686 #8 pk_backend_search_thread at pk-backend-hif.c:909 #9 pk_backend_job_thread_setup at pk-backend-job.c:815
Created attachment 1063090 [details] File: backtrace
Created attachment 1063091 [details] File: cgroup
Created attachment 1063092 [details] File: core_backtrace
Created attachment 1063093 [details] File: dso_list
Created attachment 1063094 [details] File: environ
Created attachment 1063095 [details] File: limits
Created attachment 1063096 [details] File: maps
Created attachment 1063097 [details] File: mountinfo
Created attachment 1063098 [details] File: namespaces
Created attachment 1063099 [details] File: open_fds
Created attachment 1063100 [details] File: proc_pid_status
The backtrace here looks a lot like https://bugzilla.redhat.com/show_bug.cgi?id=1135740 , but the libhif I have should be new enough to have that fixed...
*** Bug 1271851 has been marked as a duplicate of this bug. ***
This should be properly fixed upstream in https://github.com/rpm-software-management/libhif/commit/98e7f20ecc9d713239e6d68e4966a2195f62e642 , but we haven't managed to get that fix into Fedora yet.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
libhif-0.2.2-3.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ba5f1759c7
libhif-0.2.2-3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ba5f1759c7
libhif-0.2.2-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.