Version-Release number of selected component: PackageKit-1.1.5-3.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: repo_internalize_trigger executable: /usr/libexec/packagekitd global_pid: 1416 kernel: 4.10.0-1.fc26.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 repo_internalize_trigger at /usr/src/debug/libdnf-0.7.4/libdnf/hy-repo.c:59 #1 repo_internalize_all_trigger at /usr/src/debug/libdnf-0.7.4/libdnf/hy-repo.c:52 #2 dnf_sack_make_provides_ready at /usr/src/debug/libdnf-0.7.4/libdnf/dnf-sack.c:1578 #3 running_kernel at /usr/src/debug/libdnf-0.7.4/libdnf/hy-iutil.c:368 #4 dnf_sack_running_kernel at /usr/src/debug/libdnf-0.7.4/libdnf/dnf-sack.c:1610 #5 allow_uninstall_all_but_protected at /usr/src/debug/libdnf-0.7.4/libdnf/hy-goal.c:266 #6 construct_job at /usr/src/debug/libdnf-0.7.4/libdnf/hy-goal.c:345 #7 hy_goal_run_all_flags at /usr/src/debug/libdnf-0.7.4/libdnf/hy-goal.c:965 #8 hy_goal_run_flags at /usr/src/debug/libdnf-0.7.4/libdnf/hy-goal.c:952 #9 dnf_goal_depsolve at /usr/src/debug/libdnf-0.7.4/libdnf/dnf-goal.c:64
Created attachment 1264916 [details] File: backtrace
Created attachment 1264917 [details] File: cgroup
Created attachment 1264918 [details] File: core_backtrace
Created attachment 1264919 [details] File: dso_list
Created attachment 1264920 [details] File: environ
Created attachment 1264921 [details] File: exploitable
Created attachment 1264922 [details] File: limits
Created attachment 1264923 [details] File: maps
Created attachment 1264924 [details] File: mountinfo
Created attachment 1264925 [details] File: namespaces
Created attachment 1264926 [details] File: open_fds
Created attachment 1264927 [details] File: proc_pid_status
Created attachment 1264928 [details] File: var_log_messages
*** Bug 1458651 has been marked as a duplicate of this bug. ***
*** Bug 1470871 has been marked as a duplicate of this bug. ***
*** Bug 1471299 has been marked as a duplicate of this bug. ***
*** Bug 1475357 has been marked as a duplicate of this bug. ***
*** Bug 1476388 has been marked as a duplicate of this bug. ***
*** Bug 1476732 has been marked as a duplicate of this bug. ***
*** Bug 1478775 has been marked as a duplicate of this bug. ***
*** Bug 1479561 has been marked as a duplicate of this bug. ***
*** Bug 1480530 has been marked as a duplicate of this bug. ***
*** Bug 1481626 has been marked as a duplicate of this bug. ***
*** Bug 1482799 has been marked as a duplicate of this bug. ***
*** Bug 1484686 has been marked as a duplicate of this bug. ***
*** Bug 1485343 has been marked as a duplicate of this bug. ***
*** Bug 1485772 has been marked as a duplicate of this bug. ***
*** Bug 1486302 has been marked as a duplicate of this bug. ***
*** Bug 1486444 has been marked as a duplicate of this bug. ***
*** Bug 1486462 has been marked as a duplicate of this bug. ***
*** Bug 1487633 has been marked as a duplicate of this bug. ***
*** Bug 1494331 has been marked as a duplicate of this bug. ***
*** Bug 1499542 has been marked as a duplicate of this bug. ***
Similar problem has been detected: packagekitd sometimes crashes due to some background activity (checking for package updates?). $ sudo coredumpctl list /usr/libexec/packagekitd TIME PID UID GID SIG COREFILE EXE Thu 2017-06-22 08:47:13 CEST 1678 0 0 11 missing /usr/libexec/packagekitd Mon 2017-07-10 11:56:03 CEST 592 0 0 6 missing /usr/libexec/packagekitd Mon 2017-07-10 11:56:32 CEST 2393 0 0 6 missing /usr/libexec/packagekitd Thu 2017-07-20 12:23:48 CEST 541 0 0 11 missing /usr/libexec/packagekitd Tue 2017-09-05 08:23:53 CEST 524 0 0 6 missing /usr/libexec/packagekitd Tue 2017-09-19 10:41:32 CEST 556 0 0 6 missing /usr/libexec/packagekitd Tue 2017-09-19 10:41:36 CEST 3132 0 0 11 missing /usr/libexec/packagekitd Tue 2017-09-26 11:30:49 CEST 540 0 0 11 missing /usr/libexec/packagekitd Fri 2017-10-06 13:00:40 CEST 482 0 0 6 present /usr/libexec/packagekitd Mon 2017-10-09 08:48:35 CEST 491 0 0 11 present /usr/libexec/packagekitd reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: repo_internalize_trigger executable: /usr/libexec/packagekitd journald_cursor: s=173d8dcabd3441d18b7b3d596909623f;i=e12d;b=54939f318e60469eb1ddac1492d6352d;m=7147a9e;t=55a1454a7b38e;x=d04b0f803ce361e9 kernel: 4.13.1-200.fc26.x86_64 package: PackageKit-1.1.6-2.fc26 reason: packagekitd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1501453 has been marked as a duplicate of this bug. ***
*** Bug 1505068 has been marked as a duplicate of this bug. ***
*** Bug 1508156 has been marked as a duplicate of this bug. ***
*** Bug 1508641 has been marked as a duplicate of this bug. ***
*** Bug 1509538 has been marked as a duplicate of this bug. ***
*** Bug 1512234 has been marked as a duplicate of this bug. ***
*** Bug 1512254 has been marked as a duplicate of this bug. ***
*** Bug 1515578 has been marked as a duplicate of this bug. ***
*** Bug 1526299 has been marked as a duplicate of this bug. ***
*** Bug 1541764 has been marked as a duplicate of this bug. ***
*** Bug 1546307 has been marked as a duplicate of this bug. ***
*** Bug 1548338 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Crash recorded by openQA when testing installation of updates with gnome-software-3.24.3-6.fc26 (FEDORA-2018-32e6a673f0). Test basically involves installing a 'dummy' low-versioned python3-kickstart package to ensure an update is available, then running through the update workflow in Software. reporter: libreport-2.9.4 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: repo_internalize_trigger executable: /usr/libexec/packagekitd journald_cursor: s=415c2bbc2b194629adea26b250eaccd3;i=1604;b=c44acec9799c4d15a7254a754c4843b8;m=1304fa1e;t=56a214caf20e7;x=87bc9ff001f079c2 kernel: 4.15.17-200.fc26.x86_64 package: PackageKit-1.1.6-2.fc26 reason: packagekitd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
Kalev says the crash here is actually in libdnf, so we should get dnf devs to look at it. Re-assigning.
Fedora 26 is close to EOL. DNF team is not going to fix the issue. Please upgrade to Fedora 27 which should contain a fixed version.
*** Bug 1573007 has been marked as a duplicate of this bug. ***
*** Bug 1541747 has been marked as a duplicate of this bug. ***
We have reports of this crash, with an identical backtrace, up to at least recent Fedora 28. https://bugzilla.redhat.com/show_bug.cgi?id=1630936 is the most recent I have found. I will look some more to see if there are any F29 / Rawhide reports, but this at least either was not fixed in F27, or regressed in F28.
*** Bug 1576357 has been marked as a duplicate of this bug. ***
*** Bug 1581630 has been marked as a duplicate of this bug. ***
*** Bug 1582867 has been marked as a duplicate of this bug. ***
*** Bug 1519219 has been marked as a duplicate of this bug. ***
*** Bug 1519648 has been marked as a duplicate of this bug. ***
*** Bug 1524525 has been marked as a duplicate of this bug. ***
*** Bug 1528054 has been marked as a duplicate of this bug. ***
*** Bug 1529829 has been marked as a duplicate of this bug. ***
*** Bug 1532063 has been marked as a duplicate of this bug. ***
*** Bug 1540146 has been marked as a duplicate of this bug. ***
*** Bug 1542747 has been marked as a duplicate of this bug. ***
*** Bug 1544037 has been marked as a duplicate of this bug. ***
*** Bug 1544989 has been marked as a duplicate of this bug. ***
*** Bug 1546567 has been marked as a duplicate of this bug. ***
*** Bug 1547342 has been marked as a duplicate of this bug. ***
*** Bug 1550029 has been marked as a duplicate of this bug. ***
*** Bug 1551986 has been marked as a duplicate of this bug. ***
*** Bug 1552793 has been marked as a duplicate of this bug. ***
*** Bug 1553328 has been marked as a duplicate of this bug. ***
*** Bug 1554476 has been marked as a duplicate of this bug. ***
*** Bug 1556655 has been marked as a duplicate of this bug. ***
*** Bug 1556858 has been marked as a duplicate of this bug. ***
*** Bug 1557615 has been marked as a duplicate of this bug. ***
*** Bug 1558156 has been marked as a duplicate of this bug. ***
*** Bug 1559146 has been marked as a duplicate of this bug. ***
*** Bug 1562488 has been marked as a duplicate of this bug. ***
*** Bug 1562737 has been marked as a duplicate of this bug. ***
*** Bug 1563717 has been marked as a duplicate of this bug. ***
*** Bug 1564760 has been marked as a duplicate of this bug. ***
*** Bug 1567290 has been marked as a duplicate of this bug. ***
*** Bug 1568346 has been marked as a duplicate of this bug. ***
*** Bug 1568846 has been marked as a duplicate of this bug. ***
*** Bug 1570376 has been marked as a duplicate of this bug. ***
*** Bug 1572910 has been marked as a duplicate of this bug. ***
*** Bug 1572995 has been marked as a duplicate of this bug. ***
*** Bug 1574894 has been marked as a duplicate of this bug. ***
*** Bug 1575981 has been marked as a duplicate of this bug. ***
1444262, 1480846 and 1375895 are similar to this, they are all crashes between PackageKit's dnf backend and libdnf which happen in the same place in libdnf (repo_internalize_trigger), they just all get there in slightly different ways. It is possible that https://github.com/rpm-software-management/libdnf/pull/596 will fix all of these crashes; it kinda depends on whether the problem is that repo_internalize_trigger is getting called on a libsolv repo that doesn't exist, or whether the libsolv repo exists but its association to a hawkey repo is somehow lost, so the lookup of hrepo in repo_internalize_trigger fails. The problem is definitely one of those two things, but I at least am not certain which it is in each case.
Similar problem has been detected: starting terminal and "sudo dnf update" reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: repo_internalize_trigger executable: /usr/libexec/packagekitd journald_cursor: s=1df91f99aa9642f28ae8fadd93f8d566;i=1a94b;b=9b421a2c5e2d4aa0afeba671b870fe39;m=147c53ee6;t=5770743cc7396;x=ead818ba89e59f67 kernel: 4.17.18-200.fc28.x86_64 package: PackageKit-1.1.10-1.fc28 reason: packagekitd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: Using the Software application and it hung on getting application ratings. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: repo_internalize_trigger executable: /usr/libexec/packagekitd journald_cursor: s=d61624bf90fb45ce90ff2615bebf48d3;i=60308;b=54d0f43b8c48492ba79d48ae757e680a;m=9635d044;t=5795b8814a2be;x=f1dcb1bfff4087 kernel: 4.18.16-200.fc28.x86_64 package: PackageKit-1.1.10-1.fc28 reason: packagekitd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
Similar problem has been detected: Just updating the system reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/libexec/packagekitd crash_function: repo_internalize_trigger executable: /usr/libexec/packagekitd journald_cursor: s=30a647b59ecc4c30bb3896dfe65d299f;i=12bd;b=387d5e30b7dd41e6a7bbcc15c716cbfd;m=1d89eeccc;t=57898a5691a6f;x=f26522f514888c0e kernel: 4.16.3-301.fc28.x86_64 package: PackageKit-1.1.9-3.fc28 reason: packagekitd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
I am backporting important patches for libdnf and Fedora 27, 28.
libdnf-0.11.1-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-ce9924c3ba
libdnf-0.11.1-6.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-8d6bebf26e
woohoo! thanks for that.
libdnf-0.11.1-2.fc27 has been pushed to the Fedora 27 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-ce9924c3ba
libdnf-0.11.1-6.fc28 has been pushed to the Fedora 28 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-8d6bebf26e
libdnf-0.11.1-6.fc28.1 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-8d6bebf26e
libdnf-0.11.1-6.fc28.1 has been pushed to the Fedora 28 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-8d6bebf26e
libdnf-0.11.1-2.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
libdnf-0.11.1-6.fc28.1 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.