Version-Release number of selected component: PackageKit-1.1.11-1.fc29 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: g_variant_unref executable: /usr/libexec/packagekitd journald_cursor: s=d55e84882f3d4564ac944754110812d5;i=29848;b=93e6c168409e46d0a1e98ecdaedc3caf;m=a4d04cb1;t=5778b22e409c2;x=9e5bb863ceffab2c kernel: 4.18.11-301.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0
Created attachment 1491387 [details] File: backtrace
Created attachment 1491388 [details] File: cgroup
Created attachment 1491389 [details] File: core_backtrace
Created attachment 1491390 [details] File: cpuinfo
Created attachment 1491391 [details] File: dso_list
Created attachment 1491392 [details] File: environ
Created attachment 1491393 [details] File: limits
Created attachment 1491394 [details] File: maps
Created attachment 1491395 [details] File: mountinfo
Created attachment 1491396 [details] File: open_fds
Created attachment 1491397 [details] File: proc_pid_status
Created attachment 1491398 [details] File: var_log_messages
Looks like a crash in libmodulemd. Reassigning.
Yes, looks like a double-free somewhere in a cleanup function. Do you have a reproducer handy, by any chance?
I don't, but the original reporter maybe knows how to reproduce this?
I can't manage to reproduce this with libmodulemd itself; it's possible that it has something to do with how libdnf is wrapping it in a shared_ptr. CCing jmracek and dmach to look at that.
*** Bug 1658181 has been marked as a duplicate of this bug. ***
*** Bug 1659817 has been marked as a duplicate of this bug. ***
*** Bug 1666615 has been marked as a duplicate of this bug. ***
The shared_ptr might be the issue. Moving to libdnf for further investigation.
> The shared_ptr might be the issue. The problem was resolved by removing using of shared_ptr in related part of the libdnf. PR https://github.com/rpm-software-management/libdnf/pull/671 . PR https://github.com/rpm-software-management/libdnf/pull/775 .
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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.
libdnf-0.31.0-10.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-2019-dc3b5542ad
libdnf-0.31.0-10.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.