Why has Abrt (silently) ceased to enumerate CoreDumpCtl's entries?

coredumpctl list -r returns:

TIME                           PID  UID  GID SIG     COREFILE     EXE                                                                                  SIZE
Mon 2025-11-17 18:36:00 GMT 213587 1000 1000 SIGABRT present      /usr/bin/ksecretd                                                                  747.1K
Mon 2025-11-17 18:36:00 GMT 213513 1000 1000 SIGABRT present      /usr/libexec/xdg-desktop-portal-kde                                                  1.1M
Mon 2025-11-17 18:35:59 GMT 213466 1000 1000 SIGABRT present      /usr/libexec/xdg-desktop-portal-kde                                                  1.1M
Mon 2025-11-17 18:35:59 GMT 213376 1000 1000 SIGABRT present      /usr/libexec/xdg-desktop-portal-kde                                                  1.1M
Mon 2025-11-17 18:35:59 GMT 213362 1000 1000 SIGABRT present      /usr/libexec/xdg-desktop-portal-kde                                                  1.2M
Mon 2025-11-17 11:33:14 GMT  59864 1000 1000 SIGABRT present      /usr/libexec/xdg-desktop-portal-kde                                                  1.1M
Mon 2025-11-17 11:33:09 GMT  59600 1000 1000 SIGABRT present      /usr/libexec/drkonqi                                                               949.5K
Mon 2025-11-17 11:33:09 GMT  57961 1000 1000 SIGSEGV present      /usr/bin/plasmashell                                                                47.8M
Mon 2025-11-17 11:12:57 GMT  49848    0    0 SIGABRT inaccessible /tmp/.mount_QEFI.EoPhbil/usr/bin/QEFIEntryManager                                       -
Fri 2025-11-14 19:49:14 GMT   1776 1000 1000 SIGSEGV inaccessible /usr/bin/kwin_wayland                                                                   -

However, abrt list [1] returns, last:

Id           d0faaab  
Component    kwin  
Count        1  
Time         2025-11-14 19:49:14  
User id      1000 (RokeJulianLockhart)  
Reported to    
ABRT Server  https://retrace.fedoraproject.org/faf/reports/bthash/18fecf5fea800aa4d3e835efbe8f52f41e25f6c1  
Bugzilla     https://bugzilla.redhat.com/show_bug.cgi?id=2413512

  1. github.com/abrt/abrt/issues/1680 ↩︎

After having discussion.fedoraproject.org/t/162891 recur, this was remediated. However, now, abrt-2.17.7-1.fc43.x86_64 and gnome-abrt-1.4.3-8.fc43.x86_64 are in an inconsistent state:

  • abrt

    1. #!/usr/bin/env sh
      abrt list
      
    2. No problems

  • gnome-abrt

    [1] [2] [3]

    1. #!/usr/bin/env sh
      tree -a /var/spool/abrt/ccpp-2025-11-18-17:10:22.573990-14027
      
    2. .
      ├── abrt_version
      ├── analyzer
      ├── architecture
      ├── cgroup
      ├── cmdline
      ├── component
      ├── coredump
      ├── coredump.zst
      ├── count
      ├── cpuinfo
      ├── dso_list
      ├── environ
      ├── event_log
      ├── executable
      ├── exploitable
      ├── hostname
      ├── journald_cursor
      ├── kernel
      ├── last_occurrence
      ├── .libreport
      │   └── owner
      ├── limits
      ├── .lock -> 65072
      ├── maps
      ├── mountinfo
      ├── open_fds
      ├── os_info
      ├── os_release
      ├── package
      ├── pid
      ├── pkg_arch
      ├── pkg_epoch
      ├── pkg_fingerprint
      ├── pkg_name
      ├── pkg_release
      ├── pkg_vendor
      ├── pkg_version
      ├── proc_pid_status
      ├── pwd
      ├── reason
      ├── rootdir
      ├── runlevel
      ├── time
      ├── type
      ├── uid
      ├── username
      └── uuid
      
      2 directories, 46 files
      

  1. bugs.kde.org/show_bug.cgi?id=510982#c14 ↩︎

  2. github.com/ichaoX/ext-textFragment/issues/26#issuecomment-3543405918 ↩︎

  3. stackoverflow.com/questions/8768719/coredump-is-getting-truncated#comment140861241_60147685 [4] ↩︎

  4. unix.stackexchange.com/revisions/155482/1 ↩︎

I had t/162891 recur yesterday. However, that didn’t prevent qdbus-qt6 --system org.freedesktop.DisplayManager /org/freedesktop/DisplayManager/Seat0 org.freedesktop.DisplayManager.Seat.SwitchToGreeter, as bugs.kde.org/show_bug.cgi?id=500038#c17 explains is problematic (which I was attempting to reproduce to confirm that bugzilla.redhat.com/show_bug.cgi?id=2325351#c28 was erroneously closed), from, somehow, inducing it:

gnome-abrt

drkonqi-coredump-gui [1]

6fe5155 1x plasma-workspace 2025-12-20 23:56:01
ad9e0ef 1x /home/RokeJulianLockhart/.local/share/Steam/steamapps/common/War Thunder/linux64/aces 2025-12-20 23:57:54
2a9874e 8x plasma-keyboard 2025-12-21 00:34:27
ee1f0f3 1x konsole 2025-12-21 15:21:51
54d1abf 5x konsole 2025-12-21 15:22:32
6a6a33c 2x konsole 2025-12-21 15:23:26
a1568b3 1x libreport 2025-12-21 15:24:23
c715fd9 1x plasma-workspace 2025-12-21 16:26:24
a07808a 1x minetest 2025-12-21 17:49:05
6590a32 1x minetest 2025-12-21 17:49:25
a56f723 2x 0ad 2025-12-21 17:50:21
a16f186 5x firefox 2025-12-21 22:59:25
670c59c 1x 0ad 2025-12-21 23:12:17
e738a4b 1x 0ad 2025-12-21 23:14:11
b2c1ad8 1x firefox 2025-12-21 23:27:47
d206786 1x gramps 2025-12-21 23:48:21
c987c0c 1x copyq 2025-12-22 00:43:01
ee9f09f 12x xdg-desktop-portal-kde 2025-12-22 00:43:01
14f6a75 2x kf6-kwallet 2025-12-22 00:43:13
33616d8 2x plasma-systemmonitor 2025-12-22 00:43:17
5e1ff26 2x plasma-drkonqi 2025-12-22 00:43:18
fbc9156 2x vesktop 2025-12-22 00:43:18
b84f66b 1x qt5-qttools 2025-12-22 13:15:43

Mon 2025-12-22 01:21:39 GMT 443572 1000 1000 SIGABRT present  /usr/libexec/xdg-desktop-portal-kde                                                      1.2M
Mon 2025-12-22 01:21:40 GMT 443604 1000 1000 SIGABRT present  /usr/bin/ksecretd                                                                      848.6K
Mon 2025-12-22 01:21:43 GMT 412026 1000 1000 SIGTRAP present  /usr/share/vesktop/vesktop                                                               5.9M
Mon 2025-12-22 12:53:17 GMT   1794 1000 1000 SIGSEGV present  /usr/bin/wireplumber                                                                     1.4M
Mon 2025-12-22 12:54:56 GMT   7731 1000 1000 SIGSEGV present  /usr/bin/plasmashell                                                                    43.8M
Mon 2025-12-22 12:54:56 GMT  10373 1000 1000 SIGABRT present  /usr/libexec/drkonqi                                                                   950.6K
Mon 2025-12-22 12:55:03 GMT  10970 1000 1000 SIGABRT present  /usr/bin/ksplashqml                                                                      1.2M
Mon 2025-12-22 12:55:05 GMT  11123 1000 1000 SIGABRT present  /usr/libexec/xdg-desktop-portal-kde                                                      1.2M
Mon 2025-12-22 12:55:05 GMT  11139 1000 1000 SIGABRT present  /usr/libexec/xdg-desktop-portal-kde                                                      1.2M
Mon 2025-12-22 12:55:05 GMT  11160 1000 1000 SIGABRT present  /usr/libexec/xdg-desktop-portal-kde                                                      1.2M
Mon 2025-12-22 12:55:05 GMT  11177 1000 1000 SIGABRT present  /usr/libexec/xdg-desktop-portal-kde                                                      1.2M
Mon 2025-12-22 12:55:06 GMT  11202 1000 1000 SIGABRT present  /usr/libexec/xdg-desktop-portal-kde                                                      1.2M
Mon 2025-12-22 12:55:06 GMT  11225 1000 1000 SIGABRT present  /usr/bin/ksecretd                                                                      848.3K
Mon 2025-12-22 12:55:09 GMT   8262 1000 1000 SIGTRAP present  /usr/share/vesktop/vesktop                                                              13.1M
Mon 2025-12-22 13:15:43 GMT  17085 1000 1000 SIGSEGV present  /usr/bin/qtdiag                                                                          2.3M

However, this doesn’t apply to new crashes, [2] so it might have forgotten to retroactively enumate journalctl’s data < the current -b:

Tangential Estimation

Perhaps, SysRq + R, E, I, S, U, B effects this, in a way that qdbus-1t6 org.kde.Shutdown /Shutdown org.kde.Shutdown.logoutAndReboot doesn’t remediate? I haven’t tried manually reinitialising the services:

├─abrt-journal-core.service
│ └─1248 /usr/bin/abrt-dump-journal-core -D -T -f -e
├─abrt-oops.service
│ └─1249 /usr/bin/abrt-dump-journal-oops -fxtD
├─abrt-xorg.service
│ └─1254 /usr/bin/abrt-dump-journal-xorg -fxtD
└─abrtd.service
  └─1182 /usr/sbin/abrtd -d -s
    └─2758 /usr/sbin/abrt-dbus -t133
       └─2594 /usr/bin/abrt-applet --gapplication-service
         └─12640 grep --color=auto abrt

  1. invent.kde.org/plasma/drkonqi/-/commit/a4b441573c9fe60e640c65c612c6ecf5678ebf74#note_1374560 ↩︎

  2. bugzilla.redhat.com/show_bug.cgi?id=2420648#c16 ↩︎