Description of problem: I updated a Fedora 35 KDE Plasma installation on 2021-8-23 with sudo dnf offline-upgrade download sudo dnf offline-upgrade reboot The upgrade had 66 rpms including from glib2-2.69.0-1.fc35 to glib2-2.69.2-1.fc35. abrt-dbus segmentation faulted in abrt_p2_service_dbus when shutting down, rebooting, or logging out of Plasma after that update. The journal showed these crashes 27 times since that update. Many of the functions in the trace are in glib. Core was generated by `/usr/sbin/abrt-dbus -t133'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000055e14e7e7ea0 in abrt_p2_service_dbus (service=<optimized out>) at /usr/src/debug/abrt-2.14.6-7.fc35.x86_64/src/dbus/abrt_problems2_service.c:2513 2513 return service->pv->p2srv_dbus; [Current thread is 1 (Thread 0x7f3b45ca2900 (LWP 6638))] (gdb) bt #0 0x000055e14e7e7ea0 in abrt_p2_service_dbus (service=<optimized out>) at /usr/src/debug/abrt-2.14.6-7.fc35.x86_64/src/dbus/abrt_problems2_service.c:2513 #1 abrt_p2_object_destroy (object=0x55e14f34f290) at /usr/src/debug/abrt-2.14.6-7.fc35.x86_64/src/dbus/abrt_problems2_service.c:243 #2 0x00007f3b4594e703 in g_source_callback_unref (cb_data=0x55e14f299ae0) at ../glib/gmain.c:1666 #3 g_source_callback_unref (cb_data=0x55e14f299ae0) at ../glib/gmain.c:1659 #4 0x00007f3b459528bc in g_source_destroy_internal (source=0x55e14f6d0640, context=0x55e14f2d8ef0, have_lock=1) at ../glib/gmain.c:1331 #5 0x00007f3b45954480 in g_main_dispatch (context=0x55e14f2d8ef0) at ../glib/gmain.c:3411 #6 g_main_context_dispatch (context=0x55e14f2d8ef0) at ../glib/gmain.c:4099 #7 0x00007f3b459a9288 in g_main_context_iterate.constprop.0 (context=0x55e14f2d8ef0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4175 #8 0x00007f3b45953903 in g_main_loop_run (loop=0x55e14f29b8b0) at ../glib/gmain.c:4373 #9 0x000055e14e7e680d in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/abrt-2.14.6-7.fc35.x86_64/src/dbus/abrt-dbus.c:1084 Version-Release number of selected component (if applicable): abrt-2.14.6-7.fc35.x86_64 glib2-2.69.2-1.fc35.x86_64 How reproducible: abrt-dbus crashed 27 times which looked like most of not all the times I shut down, rebooted, or logged out of Plasma since the update Steps to Reproduce: 1. Boot a Fedora 35 KDE Plasma installation updated to 2021-8-24 2. Log in to Plasma on Wayland 3. Shut down, reboot, or log out of Plasma Actual results: abrt-dbus segmentation faulted in abrt_p2_service_dbus when shutting down, rebooting, or logging out of Plasma Expected results: No crashes would happen. Additional info:
I downgraded to glib2-2.69.0-1.fc35 and rebooted. abrt-dbus didn't crash when shutting down, rebooting, or logging out of Plasma with glib2-2.69.0-1.fc35. I upgraded to glib2-2.69.2-1.fc35 again. abrt-dbus segmentation faulted when shutting down, rebooting, or logging out of Plasma a few times with glib2-2.69.2-1.fc35. The crash is likely due to a change between glib2-2.69.0-1.fc35 and glib2-2.69.2-1.fc35. The crash also happened when I logged out of GNOME on Wayland.
Created attachment 1820404 [details] coredumpctl gdb, thread apply all bt full I've got almost a dozen of these myself in just a few days since upgrading to F35. abrt-dbus-2.14.6-7.fc35.x86_64 coredumpctl info coredumpctl gdb
Proposed as a Blocker for 35-final by Fedora user chrismurphy using the blocker tracking app because: https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#SELinux_and_crash_notifications We should be getting a crash notification for this, but we aren't probably because of the thing that's crashing. And it shouldn't crash: (a) it's in a release blocking desktop (b) in the default installation and configuration (c) it's a crash in a component of the "problem reporter" which is in the list of things that "must start successfully and withstand a basic functionality test" https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Default_application_functionality
This glib2 commit in 2.69.2 seems like it might be related to the problem here: https://gitlab.gnome.org/GNOME/glib/-/commit/72f692eae4954da8e0ad0651bb87984f2ed82cb1 But so far that is a speculation on my end. Still investigating...
Ok, I am not able to reproduce this problem on a fully up-to-date F35 installation. It is true that there are applications crashing when I log out and log in again. But abrt-dbus is not one of them. In fact, I was able to report two bugs using abrt on F35: https://bugzilla.redhat.com/show_bug.cgi?id=2001729 and already existing one: https://bugzilla.redhat.com/show_bug.cgi?id=1998569#c11 Could you please try again with fully up-to-date system?
The abrt-dbus crashes still happen when logging out of Plasma on Wayland with a F35 KDE Plasma installation fully updated to 2021-9-6 with updates-testing enabled except for the gnome-shell-41~rc-1.fc35 update due to the dnf errors reported by adamwill at https://bodhi.fedoraproject.org/updates/FEDORA-2021-ce1f1fbfff The abrt-dbus crashes didn't appear in gnome-abrt, but they did show up using coredumpctl and journalctl when logging out. The abrt-dbus crashes sometimes didn't show up using coredumpctl when I've rebooted or shut down, but they were in the journal. kwin_wayland segmentation faulted in KWin::LibInput::Context::closeRestricted when logging out of Plasma with libinput-1.18.901-1.fc35 using a mouse since 2021-9-3 https://bugzilla.redhat.com/show_bug.cgi?id=2001135 abrt-dbus crashed when kwin_wayland did, and Plasma restarted. xdg-desktop-portal-kde aborted sometimes when I've logged out of Plasma, but the xdg-desktop-portal-kde crashes were happening for months before the abrt-dbus ones. I'm not running F35 in a VM, but you reported you were using a VM at https://bugzilla.redhat.com/show_bug.cgi?id=1998569#c11 I haven't seen the klauncher crash recently.
Discussed at 2021-09-06 blocker/FE review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2021/fedora-blocker-review.2021-09-06-16.00.html . Accepted as a Final blocker as a violation of the criteria cited by Chris Murphy, and also as a Beta freeze exception as we believe it's worth fixing this for Beta so problem reporting works from the KDE live and first install environment.
I ran abrt-dbus under valgrind by changing a line in /usr/share/dbus-1/system-services/org.freedesktop.problems.service to Exec=valgrind --log-file=/home/matt/programs/abrt/valgrind-abrt-dbus-4.txt /usr/sbin/abrt-dbus -t133 I rebooted, logged into Plasma, then I rebooted again. abrt-dbus crashed as it was closing during the reboot. The valgrind log showed 3 invalid reads starting in abrt_p2_object_destroy at abrt_problems2_service.c:241 which looked like use-after-free errors since they had lines like "Address 0x14197790 is 16 bytes inside a block of size 56 free'd" The last invalid read at 0x18 in UnknownInlinedFun at abrt_problems2_service.c:2513 resulted in the segmentation fault. ==5082== Memcheck, a memory error detector ==5082== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==5082== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info ==5082== Command: /usr/sbin/abrt-dbus -t133 ==5082== Parent PID: 1 ==5082== ==5082== Invalid read of size 8 ==5082== at 0x110E74: abrt_p2_object_destroy (abrt_problems2_service.c:241) ==5082== by 0x4BB2702: UnknownInlinedFun (gmain.c:1666) ==5082== by 0x4BB2702: g_source_callback_unref (gmain.c:1659) ==5082== by 0x4BB68BB: g_source_destroy_internal (gmain.c:1331) ==5082== by 0x4BB847F: UnknownInlinedFun (gmain.c:3411) ==5082== by 0x4BB847F: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== Address 0x14197790 is 16 bytes inside a block of size 56 free'd ==5082== at 0x48430E4: free (vg_replace_malloc.c:755) ==5082== by 0x4BBD0BC: g_free (gmem.c:199) ==5082== by 0x4A2CB90: call_destroy_notify_data_in_idle.lto_priv.0 (gdbusconnection.c:239) ==5082== by 0x4BB452A: g_idle_dispatch (gmain.c:5897) ==5082== by 0x4BB833E: UnknownInlinedFun (gmain.c:3381) ==5082== by 0x4BB833E: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== Block was alloc'd at ==5082== at 0x4845464: calloc (vg_replace_malloc.c:1117) ==5082== by 0x4BC0CD0: g_malloc0 (gmem.c:136) ==5082== by 0x11116B: abrt_p2_object_new (abrt_problems2_service.c:288) ==5082== by 0x112191: UnknownInlinedFun (abrt_problems2_service.c:545) ==5082== by 0x112191: abrt_p2_service_get_session_for_caller (abrt_problems2_service.c:601) ==5082== by 0x113037: abrt_p2_service_caller_uid (abrt_problems2_service.c:652) ==5082== by 0x1197C4: handle_method_call (abrt-dbus.c:361) ==5082== by 0x4A3D551: call_in_idle_cb.lto_priv.0 (gdbusconnection.c:4916) ==5082== by 0x4BB452A: g_idle_dispatch (gmain.c:5897) ==5082== by 0x4BB833E: UnknownInlinedFun (gmain.c:3381) ==5082== by 0x4BB833E: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== ==5082== Invalid read of size 8 ==5082== at 0x110E99: UnknownInlinedFun (abrt_problems2_service.c:2513) ==5082== by 0x110E99: abrt_p2_object_destroy (abrt_problems2_service.c:243) ==5082== by 0x4BB2702: UnknownInlinedFun (gmain.c:1666) ==5082== by 0x4BB2702: g_source_callback_unref (gmain.c:1659) ==5082== by 0x4BB68BB: g_source_destroy_internal (gmain.c:1331) ==5082== by 0x4BB847F: UnknownInlinedFun (gmain.c:3411) ==5082== by 0x4BB847F: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== Address 0x14197780 is 0 bytes inside a block of size 56 free'd ==5082== at 0x48430E4: free (vg_replace_malloc.c:755) ==5082== by 0x4BBD0BC: g_free (gmem.c:199) ==5082== by 0x4A2CB90: call_destroy_notify_data_in_idle.lto_priv.0 (gdbusconnection.c:239) ==5082== by 0x4BB452A: g_idle_dispatch (gmain.c:5897) ==5082== by 0x4BB833E: UnknownInlinedFun (gmain.c:3381) ==5082== by 0x4BB833E: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== Block was alloc'd at ==5082== at 0x4845464: calloc (vg_replace_malloc.c:1117) ==5082== by 0x4BC0CD0: g_malloc0 (gmem.c:136) ==5082== by 0x11116B: abrt_p2_object_new (abrt_problems2_service.c:288) ==5082== by 0x112191: UnknownInlinedFun (abrt_problems2_service.c:545) ==5082== by 0x112191: abrt_p2_service_get_session_for_caller (abrt_problems2_service.c:601) ==5082== by 0x113037: abrt_p2_service_caller_uid (abrt_problems2_service.c:652) ==5082== by 0x1197C4: handle_method_call (abrt-dbus.c:361) ==5082== by 0x4A3D551: call_in_idle_cb.lto_priv.0 (gdbusconnection.c:4916) ==5082== by 0x4BB452A: g_idle_dispatch (gmain.c:5897) ==5082== by 0x4BB833E: UnknownInlinedFun (gmain.c:3381) ==5082== by 0x4BB833E: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== ==5082== Invalid read of size 4 ==5082== at 0x110E9C: abrt_p2_object_destroy (abrt_problems2_service.c:243) ==5082== by 0x4BB2702: UnknownInlinedFun (gmain.c:1666) ==5082== by 0x4BB2702: g_source_callback_unref (gmain.c:1659) ==5082== by 0x4BB68BB: g_source_destroy_internal (gmain.c:1331) ==5082== by 0x4BB847F: UnknownInlinedFun (gmain.c:3411) ==5082== by 0x4BB847F: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== Address 0x14197798 is 24 bytes inside a block of size 56 free'd ==5082== at 0x48430E4: free (vg_replace_malloc.c:755) ==5082== by 0x4BBD0BC: g_free (gmem.c:199) ==5082== by 0x4A2CB90: call_destroy_notify_data_in_idle.lto_priv.0 (gdbusconnection.c:239) ==5082== by 0x4BB452A: g_idle_dispatch (gmain.c:5897) ==5082== by 0x4BB833E: UnknownInlinedFun (gmain.c:3381) ==5082== by 0x4BB833E: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== Block was alloc'd at ==5082== at 0x4845464: calloc (vg_replace_malloc.c:1117) ==5082== by 0x4BC0CD0: g_malloc0 (gmem.c:136) ==5082== by 0x11116B: abrt_p2_object_new (abrt_problems2_service.c:288) ==5082== by 0x112191: UnknownInlinedFun (abrt_problems2_service.c:545) ==5082== by 0x112191: abrt_p2_service_get_session_for_caller (abrt_problems2_service.c:601) ==5082== by 0x113037: abrt_p2_service_caller_uid (abrt_problems2_service.c:652) ==5082== by 0x1197C4: handle_method_call (abrt-dbus.c:361) ==5082== by 0x4A3D551: call_in_idle_cb.lto_priv.0 (gdbusconnection.c:4916) ==5082== by 0x4BB452A: g_idle_dispatch (gmain.c:5897) ==5082== by 0x4BB833E: UnknownInlinedFun (gmain.c:3381) ==5082== by 0x4BB833E: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== ==5082== Invalid read of size 8 ==5082== at 0x110EA0: UnknownInlinedFun (abrt_problems2_service.c:2513) ==5082== by 0x110EA0: abrt_p2_object_destroy (abrt_problems2_service.c:243) ==5082== by 0x4BB2702: UnknownInlinedFun (gmain.c:1666) ==5082== by 0x4BB2702: g_source_callback_unref (gmain.c:1659) ==5082== by 0x4BB68BB: g_source_destroy_internal (gmain.c:1331) ==5082== by 0x4BB847F: UnknownInlinedFun (gmain.c:3411) ==5082== by 0x4BB847F: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== Address 0x18 is not stack'd, malloc'd or (recently) free'd ==5082== ==5082== ==5082== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==5082== Access not within mapped region at address 0x18 ==5082== at 0x110EA0: UnknownInlinedFun (abrt_problems2_service.c:2513) ==5082== by 0x110EA0: abrt_p2_object_destroy (abrt_problems2_service.c:243) ==5082== by 0x4BB2702: UnknownInlinedFun (gmain.c:1666) ==5082== by 0x4BB2702: g_source_callback_unref (gmain.c:1659) ==5082== by 0x4BB68BB: g_source_destroy_internal (gmain.c:1331) ==5082== by 0x4BB847F: UnknownInlinedFun (gmain.c:3411) ==5082== by 0x4BB847F: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== If you believe this happened as a result of a stack ==5082== overflow in your program's main thread (unlikely but ==5082== possible), you can try to increase the size of the ==5082== main thread stack using the --main-stacksize= flag. ==5082== The main thread stack size used in this run was 8388608. ==5082== ==5082== Process terminating with default action of signal 15 (SIGTERM) ==5082== at 0x110EA0: UnknownInlinedFun (abrt_problems2_service.c:2513) ==5082== by 0x110EA0: abrt_p2_object_destroy (abrt_problems2_service.c:243) ==5082== by 0x4BB2702: UnknownInlinedFun (gmain.c:1666) ==5082== by 0x4BB2702: g_source_callback_unref (gmain.c:1659) ==5082== by 0x4BB68BB: g_source_destroy_internal (gmain.c:1331) ==5082== by 0x4BB847F: UnknownInlinedFun (gmain.c:3411) ==5082== by 0x4BB847F: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== ==5082== Process terminating with default action of signal 11 (SIGSEGV) ==5082== General Protection Fault ==5082== at 0x4D4AC02: __pthread_once_slow (in /usr/lib64/libc.so.6) ==5082== by 0x4E06762: __rpc_thread_variables (in /usr/lib64/libc.so.6) ==5082== by 0x4E58CCC: free_mem (in /usr/lib64/libc.so.6) ==5082== by 0x4E58801: __libc_freeres (in /usr/lib64/libc.so.6) ==5082== by 0x48351E7: _vgnU_freeres (vg_preloaded.c:74) ==5082== by 0x4C9C3DF: ??? (in /usr/lib64/libglib-2.0.so.0.6902.0) ==5082== by 0x4BB2702: UnknownInlinedFun (gmain.c:1666) ==5082== by 0x4BB2702: g_source_callback_unref (gmain.c:1659) ==5082== by 0x4BB68BB: g_source_destroy_internal (gmain.c:1331) ==5082== by 0x4BB847F: UnknownInlinedFun (gmain.c:3411) ==5082== by 0x4BB847F: g_main_context_dispatch (gmain.c:4099) ==5082== by 0x4C0D287: g_main_context_iterate.constprop.0 (gmain.c:4175) ==5082== by 0x4BB7902: g_main_loop_run (gmain.c:4373) ==5082== by 0x10F80C: main (abrt-dbus.c:1084) ==5082== ==5082== HEAP SUMMARY: ==5082== in use at exit: 3,183,762 bytes in 55,937 blocks ==5082== total heap usage: 314,072 allocs, 258,135 frees, 76,611,653 bytes allocated ==5082== ==5082== LEAK SUMMARY: ==5082== definitely lost: 15 bytes in 1 blocks ==5082== indirectly lost: 0 bytes in 0 blocks ==5082== possibly lost: 1,344 bytes in 3 blocks ==5082== still reachable: 2,924,115 bytes in 52,421 blocks ==5082== suppressed: 0 bytes in 0 blocks ==5082== Rerun with --leak-check=full to see details of leaked memory ==5082== ==5082== For lists of detected and suppressed errors, rerun with: -s ==5082== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0) I tried logging out and rebooting a few other times, and abrt-dbus under valgrind segmentation faulted and a core dump was generated. The valgrind logs were incomplete though. Thanks.
Hi Michael, can we check in on the status of this? F35 Final is coming up fairly soon, and this is a blocker. Thanks!
Hi Adam, Soon-ish -- I hope to have the fix ready early next week!
Possibly related - bug 2010231. I also often see abrt-dbus crash on login, or perhaps after starting gnome-abrt.
Created attachment 1829067 [details] Journalctl output from the moment I exit ABRT - still crashing Operating System: Fedora Linux 35 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.9-300.fc35.x86_64 (64-bit) gnome-abrt-1.4.0-2.fc35.x86_64 abrt-debugsource-2.14.6-7.fc35.x86_64 abrt-debuginfo-2.14.6-7.fc35.x86_64 abrt-dbus-debuginfo-2.14.6-7.fc35.x86_64 abrt-libs-2.14.6-8.fc35.x86_64 abrt-dbus-2.14.6-8.fc35.x86_64 python3-abrt-2.14.6-8.fc35.x86_64 abrt-2.14.6-8.fc35.x86_64 abrt-addon-kerneloops-2.14.6-8.fc35.x86_64 abrt-retrace-client-2.14.6-8.fc35.x86_64 abrt-addon-ccpp-2.14.6-8.fc35.x86_64 abrt-addon-pstoreoops-2.14.6-8.fc35.x86_64 abrt-addon-vmcore-2.14.6-8.fc35.x86_64 abrt-addon-xorg-2.14.6-8.fc35.x86_64 abrt-plugin-bodhi-2.14.6-8.fc35.x86_64 python3-abrt-addon-2.14.6-8.fc35.noarch abrt-tui-2.14.6-8.fc35.x86_64 abrt-gui-libs-2.14.6-8.fc35.x86_64 abrt-gui-2.14.6-8.fc35.x86_64 abrt-desktop-2.14.6-8.fc35.x86_64 abrt-cli-2.14.6-8.fc35.x86_64
Created attachment 1829070 [details] Coredump gdb from previous log
Backport PR for F35: https://src.fedoraproject.org/rpms/abrt/pull-request/15
FEDORA-2021-418a00501f has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-418a00501f
*** Bug 2010231 has been marked as a duplicate of this bug. ***
As I mentioned in bz#2010231, this issue also happens on a clean, fully updated installation of Fedora 35 Beta Workstation (with GNOME Shell 41.0, using Wayland session).
https://bodhi.fedoraproject.org/updates/FEDORA-2021-418a00501f should land in updates-testing soon. It should fix this problem.
*** Bug 2010452 has been marked as a duplicate of this bug. ***
*** Bug 2009348 has been marked as a duplicate of this bug. ***
(In reply to Fedora Update System from comment #15) > FEDORA-2021-418a00501f has been submitted as an update to Fedora 35. > https://bodhi.fedoraproject.org/updates/FEDORA-2021-418a00501f Seems to fix the issue for me.
FEDORA-2021-418a00501f has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
yes, with abrt-2.14.6-9.fc35.x86_64 this bug is fixed here.