Description of problem: m not sure why this crashed but now gnome boxes crashed with a windows 10 running on it during an update and it hasent created a abrt report. also automatic retrace failed again Version-Release number of selected component: PackageKit-1.2.2-2.fc33 Additional info: reporter: libreport-2.14.0 backtrace_rating: 3 cgroup: 0::/system.slice/packagekit.service cmdline: /usr/libexec/packagekitd crash_function: dnf_context_invalidate_full executable: /usr/libexec/packagekitd journald_cursor: s=63def85765c44d7c910bd424d3d0a5f6;i=4d9ed;b=9c1f92deade54783a79a8248204c8b98;m=36af980e;t=5c1de454fc8ac;x=c05a9c731bac8098 kernel: 5.11.18-200.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (8 frames) #0 dnf_context_invalidate_full #2 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3739 #5 g_cclosure_marshal_VOID__OBJECTv at ../gobject/gmarshal.c:1910 #6 _g_closure_invoke_va at ../gobject/gclosure.c:873 #9 update_mounts at ../gio/gunixvolumemonitor.c:411 #10 _g_closure_invoke_va at ../gobject/gclosure.c:873 #13 g_context_specific_source_dispatch at ../gio/gcontextspecificgroup.c:54 #16 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4119
Similar problem has been detected: m not sure why this crashed but now gnome boxes crashed with a windows 10 running on it during an update and it hasent created a abrt report. also automatic retrace failed again reporter: libreport-2.14.0 backtrace_rating: 3 cgroup: 0::/system.slice/packagekit.service cmdline: /usr/libexec/packagekitd crash_function: dnf_context_invalidate_full executable: /usr/libexec/packagekitd journald_cursor: s=63def85765c44d7c910bd424d3d0a5f6;i=4d9ed;b=9c1f92deade54783a79a8248204c8b98;m=36af980e;t=5c1de454fc8ac;x=c05a9c731bac8098 kernel: 5.11.18-200.fc33.x86_64 package: PackageKit-1.2.2-2.fc33 reason: packagekitd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
*** Bug 1965003 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I was up to report a packagekit problem from 3 days ago, when the reporting program crashed. Then in the notifications (top panel, just "behind" the date and time), a new packagekit problem was reported (this very one). reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/system.slice/packagekit.service cmdline: /usr/libexec/packagekitd crash_function: dnf_context_invalidate_full executable: /usr/libexec/packagekitd journald_cursor: s=e9df9f17c43245a6b27417b5bed52ce0;i=18c06c;b=2c494a54944f4b48934e028a19d8937c;m=15afcded;t=5c3ce8605d2d5;x=c8037e9a3601b501 kernel: 5.12.8-200.fc33.x86_64 package: PackageKit-1.2.2-2.fc33 reason: packagekitd killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 0
Created attachment 1788756 [details] File: backtrace
*** Bug 1974924 has been marked as a duplicate of this bug. ***
*** Bug 1975668 has been marked as a duplicate of this bug. ***
*** Bug 1975952 has been marked as a duplicate of this bug. ***
*** Bug 1980268 has been marked as a duplicate of this bug. ***
*** Bug 1983574 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 '33'. 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 33 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.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.