Why is Abrt refusing to process a trace?

How can I resolve this?

PS /home/RokeJulianLockhart> abrt retrace -f 7d68a88
Traceback (most recent call last):
  File "/usr/lib64/python3.14/site-packages/problem/proxies.py", line 53, in _dbus_call
    return getattr(self._iface, fun_name)(*args)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^
  File "/usr/lib64/python3.14/site-packages/dbus/proxies.py", line 141, in __call__
    return self._connection.call_blocking(self._named_service,
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
                                          self._object_path,
                                          ^^^^^^^^^^^^^^^^^^
    ...<3 lines>...
                                          args,
                                          ^^^^^
                                          **keywords)
                                          ^^^^^^^^^^^
  File "/usr/lib64/python3.14/site-packages/dbus/connection.py", line 696, in call_blocking
    reply_message = self.send_message_with_reply_and_block(
        message, timeout)
dbus.exceptions.DBusException: org.freedesktop.problems.InvalidProblemDir: Problem directory is being processed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/abrt", line 42, in <module>
    namespace.func(namespace)
    ~~~~~~~~~~~~~~^^^^^^^^^^^
  File "/usr/lib/python3.14/site-packages/abrtcli/cli/retrace.py", line 47, in run
    problem.chown()
    ~~~~~~~~~~~~~^^
  File "/usr/lib64/python3.14/site-packages/problem/__init__.py", line 286, in chown
    self._proxy.chown(self._probdir)
    ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.14/site-packages/problem/proxies.py", line 88, in chown
    return self._dbus_call('ChownProblemDir', dump_dir)
           ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.14/site-packages/problem/proxies.py", line 64, in _dbus_call
    raise problem.exception.InvalidProblem(e)
problem.exception.InvalidProblem: org.freedesktop.problems.InvalidProblemDir: Problem directory is being processed

The relevant log is:

PS /home/RokeJulianLockhart> coredumpctl debug                   
           PID: 8890 (thunderbird)
           UID: 1000 (RokeJulianLockhart)
           GID: 1000 (RokeJulianLockhart)
        Signal: 6 (ABRT)
     Timestamp: Sat 2026-10-10 12:37:07 BST (28min ago)
  Command Line: /usr/lib64/thunderbird/thunderbird
    Executable: /usr/lib64/thunderbird/thunderbird
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-net.thunderbird.Thunderbird@7b6cbfec610846aca98dc089ed1a5e6e.service
          Unit: user@1000.service
     User Unit: app-net.thunderbird.Thunderbird@7b6cbfec610846aca98dc089ed1a5e6e.service
         Slice: user-1000.slice
     Owner UID: 1000 (RokeJulianLockhart)
       Boot ID: 6a2e060edd43448f8bcd913ed507f119
    Machine ID: 427143abd98046a4b2c750e2ca0036ea
      Hostname: beedell.rokeJulianLockhart.skqy07
       Storage: /var/lib/systemd/coredump/core.thunderbird.1000.6a2e060edd43448f8bcd913ed507f119.8890.1791632227000000.zst (present)
  Size on Disk: 130.7M
       Message: Process 8890 (thunderbird) of user 1000 dumped core.

My Environment

hostnamectl status returns:

     Static hostname: beedell.rokeJulianLockhart.skqy07
   Chassis Asset Tag: FRANMZCPA74331003E
          Machine ID: 427143abd98046a4b2c750e2ca0036ea
             Boot ID: 6a2e060edd43448f8bcd913ed507f119
    Operating System: Fedora Linux 44 (KDE Plasma Desktop Edition)
         CPE OS Name: cpe:/o:fedoraproject:fedora:44
      OS Support End: Wed 2027-05-19
OS Support Remaining: 7month 1w
              Kernel: Linux 7.2.9-200.fc44.x86_64
        Architecture: x86-64
     Hardware Vendor: Framework
      Hardware Model: Laptop 16 _AMD Ryzen 7040 Series_
        Hardware SKU: FRANMZCP07
    Hardware Version: A7
    Firmware Version: 04.05

Waiting appears to work:

PS /home/RokeJulianLockhart> abrt report fa9862d    
Reporting problem fa9862d

Server responded with an error: 'Element 'desktop' is invalid: String '/usr/share/wayland-sessions/plasma.desktop' does not match the pattern  '^[a-zA-Z0-9_/-]+$''
no actions matching this problem found for event 'collect_GConf'
no actions matching this problem found for event 'collect_vimrc_system'
no actions matching this problem found for event 'collect_vimrc_user'
no actions matching this problem found for event 'collect_xsession_errors'
Generating backtrace
Backtrace is too big (1690586 bytes), reducing depth to 512
Backtrace is too big (1687744 bytes), reducing depth to 256
Backtrace is too big (1687744 bytes), reducing depth to 128
Backtrace is too big (1687744 bytes), reducing depth to 64
Backtrace is generated and saved, 132818 bytes
Looking for similar problems in bugzilla
abrt-action-find-bodhi-update [WARNING] Duplicate Bugzilla bug '#2254552' was found
Searching for updates
No updates for this package found
Bugzilla API key: $key

The report has been updated
Checking for duplicates
Bug is already reported: 2437594
Adding new comment to bug 2437594
Status: CLOSED RAWHIDE https://bugzilla.redhat.com/show_bug.cgi?id=2437594
This problem does not have an uReport assigned.
Lock file '.lock' was locked by process 37476, but it crashed?
PS /home/RokeJulianLockhart>

Though, knowing how to be notified when the relevant process has been completed would be helpful, so that I do not need to frequently, manually check.

abrt is dead and will be removed from f45.

It’s time to start using other tools like systemd-coredump⁠ and ⁠coredumpctl

@augenauf, I’m aware of what you refer to, although it shall solely cease to be installed by default. I contributed to the decision process.

Unfortunately, systemd’s coredumpd (which provides systemctl) does not provide reporting capabilities. Solely drkonqi equivalates it, and it does not integrate with RedHat Bugzilla.

Nothing provides or will provide reporting capabilities

@augenauf, abrt continues to, for bugzilla.redhat.com, and drkonqi does, for bugs.kde.org. (Additionally, supportconfig provides much of abrt’s functionality.)