tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04

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

Turns out disabling the service wasn't that easy, but bdrung's helpful tip allowed me to narrow down the first problematic syscall to be fstatat64, which in turn led me to an upstream patch that we actually already cherry-picked in Hirsute.

Attached is the debdiff for the package that I'd like to upload, I'll just find a helpful Desktop team member to review it before actually uploading.

That patch makes sense to me. It would be nice to get this SRU expedited so that most people upgrading from 20.04 LTS can avoid the crash.

IMO we should get this fix into jammy-updates before enabling the upgrade for everyone.

Uploaded, waiting in the Unapproved queue for now.

Hello Simon, or anyone else affected,

Accepted tracker-miners into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tracker-miners/2.3.3-2ubuntu0.20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Tested in a VM: Enabled -proposed, upgraded the two packages, disabled -proposed and ran an upgrade:

```
sudo apt install tracker-extract/focal-proposed tracker-miner-fs/focal-proposed
update-manager -cd
```

/var/crash was still empty after an successful upgrade to Ubuntu 22.04. So successful verified the fix.

This bug was fixed in the package tracker-miners - 2.3.3-2ubuntu0.20.04.1

---------------
tracker-miners (2.3.3-2ubuntu0.20.04.1) focal; urgency=medium

  * d/p/libtracker-miners-common-Add-newstatat-statat64-syscalls.patch:
    cherry-picked from upstream to prevent seccomp crashes with newer glibc,
    notably during dist-upgrade. (LP: #1983859)

 -- Simon Chopin <email address hidden> Wed, 10 Aug 2022 14:05:34 +0200

The verification of the Stable Release Update for tracker-miners has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.