$ abrt-cli list Id ed0117b Component pipewire Count 1 Time 2022-02-04 14:01:17 User id 1000 (ydroneaud) $ abrt-cli report -v ed0117b Reporting problem ed0117b Generating core_backtrace Error: File './coredump' is not a coredump uReport can't be sent without core_backtrace. Exiting. ('report_uReport' exited with 1) Error: File './coredump' is not a coredump $ coredumpctl list -1 TIME PID UID GID SIG COREFILE EXE SIZE Fri 2022-02-04 14:01:17 CET 2347 1000 1000 SIGABRT present /usr/bin/pipewire-pulse 4.6M $ coredumpctl dump -1 > /dev/null PID: 2347 (pipewire-pulse) UID: 1000 (ydroneaud) GID: 1000 (ydroneaud) Signal: 6 (ABRT) Timestamp: Fri 2022-02-04 14:01:15 CET (20min ago) Command Line: /usr/bin/pipewire-pulse Executable: /usr/bin/pipewire-pulse Control Group: /user.slice/user-1000.slice/user/session.slice/pipewire-pulse.service Unit: user User Unit: pipewire-pulse.service Slice: user-1000.slice Owner UID: 1000 (ydroneaud) Boot ID: 2d56df9d8258413daeb264011376b706 Machine ID: c46bfb54d9c34279999b237c193b4d14 Hostname: thinkpad-t460 Storage: /var/lib/systemd/coredump/core.pipewire-pulse.1000.2d56df9d8258413daeb264011376b706.2347.1643979675000000.zst (present) Disk Size: 4.6M Message: Process 2347 (pipewire-pulse) of user 1000 dumped core. ... Stack trace of thread 2347: #0 0x00007f1704730f0c __pthread_kill_implementation (libc.so.6 + 0x92f0c) #1 0x00007f17046e0a36 __GI_raise (libc.so.6 + 0x42a36) #2 0x00007f17046ca82f __GI_abort (libc.so.6 + 0x2c82f) #3 0x00007f170472501e __libc_message (libc.so.6 + 0x8701e) #4 0x00007f170473ab5c malloc_printerr (libc.so.6 + 0x9cb5c) #5 0x00007f170473cd1c _int_free (libc.so.6 + 0x9ed1c) #6 0x00007f170473f3d3 __GI___libc_free (libc.so.6 + 0xa13d3) #7 0x00007f16f615b35c impl_clear (libspa-audioconvert.so + 0x2035c) #8 0x00007f170490d94f n/a (/usr/lib64/libpipewire-0.3.so.0.343.0 (deleted) + 0x6d94f) ELF object binary architecture: AMD x86-64
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
I am also hitting this bug and I believe that it hinders testability of Fedora 36 because I have not been able to retrace a singe issue caught by Abrt.
There is another bug related to this problem, already accepted as a F36 blocker: https://bugzilla.redhat.com/show_bug.cgi?id=2052872
*** This bug has been marked as a duplicate of bug 2052872 ***