Version-Release number of selected component: PackageKit-1.1.10-1.fc29 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: g_malloc executable: /usr/libexec/packagekitd journald_cursor: s=e1e421be63d3410e96934f07a3ebd339;i=834;b=36ba5e48ce57492abc0c9841c6f6ab2f;m=18901fd;t=56d09995db2b6;x=dca938d77726f338 kernel: 4.17.0-0.rc6.git1.1.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Potential duplicate: bug 1471891
Created attachment 1442436 [details] File: backtrace
Created attachment 1442437 [details] File: cgroup
Created attachment 1442438 [details] File: core_backtrace
Created attachment 1442439 [details] File: cpuinfo
Created attachment 1442440 [details] File: dso_list
Created attachment 1442441 [details] File: environ
Created attachment 1442442 [details] File: limits
Created attachment 1442444 [details] File: maps
Created attachment 1442446 [details] File: mountinfo
Created attachment 1442448 [details] File: open_fds
Created attachment 1442450 [details] File: proc_pid_status
Created attachment 1442452 [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.