Version-Release number of selected component: PackageKit-1.1.8-2.fc28 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: munmap_chunk executable: /usr/libexec/packagekitd journald_cursor: s=512cce9fcb9344418d7a11854c2c9b12;i=f826b;b=cee265b0a4a445d089553852a989d73a;m=4179c82c4;t=565ce5ab6a1a5;x=7d6f9114828ed231 kernel: 4.15.0-1.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0
Created attachment 1399588 [details] File: backtrace
Created attachment 1399589 [details] File: cgroup
Created attachment 1399590 [details] File: core_backtrace
Created attachment 1399591 [details] File: cpuinfo
Created attachment 1399592 [details] File: dso_list
Created attachment 1399593 [details] File: environ
Created attachment 1399594 [details] File: limits
Created attachment 1399595 [details] File: maps
Created attachment 1399596 [details] File: mountinfo
Created attachment 1399597 [details] File: open_fds
Created attachment 1399598 [details] File: proc_pid_status
Created attachment 1399599 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
This should hopefully be fixed in PackageKit 1.1.12 where we fixed a multithreading issue in DnfRepo handling that was likely causing this crash. If the crash is still reproducable after updating to 1.1.12, please reopen the ticket.
PackageKit-1.1.12-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c3dd0383fa
PackageKit-1.1.12-1.fc29 has been pushed to the Fedora 29 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-2018-c3dd0383fa
PackageKit-1.1.12-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.