I tried to produce a usable backtrace by copying the crash file back to a VM that were in the state before the upgrade, but the backtrace there has GDB warnings: Section `.reg-xstate/$number' in core file too small. I assume that the crash happens when already some package were updated.
What I saw the the journal log: dbus-daemon[813]: Unknown group "power" in message bus configuration file
You can try to create the GDB backtrace directly after the crash. Modify ExecStart in
/usr/lib/systemd/user/tracker-extract.service to:
ExecStart=/usr/bin/gdb --batch --ex run --ex bt /usr/libexec/tracker-extract
I tried to produce a usable backtrace by copying the crash file back to a VM that were in the state before the upgrade, but the backtrace there has GDB warnings: Section `.reg-xstate/ $number' in core file too small. I assume that the crash happens when already some package were updated.
What I saw the the journal log: dbus-daemon[813]: Unknown group "power" in message bus configuration file
You can try to create the GDB backtrace directly after the crash. Modify ExecStart in systemd/ user/tracker- extract. service to:
/usr/lib/
ExecStart= /usr/bin/ gdb --batch --ex run --ex bt /usr/libexec/ tracker- extract