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

[rokejulianlockhart (Mr. Beedell, Roke Julian Lockhart (RJLB))]

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 ↩︎