tracker-extract-3 crashed with SIGSYS in __GI_epoll_pwait()

[bat]

i dont know much about this

ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: tracker-extract 3.4.6-3
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic aarch64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: arm64
CasperMD5CheckResult: pass
CasperVersion: 1.494
CloudArchitecture: aarch64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 26 12:38:36 2024
ExecutablePath: /usr/libexec/tracker-extract-3
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64 (20240316)
ProcCmdline: /usr/libexec/tracker-extract-3
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
Signal: 31
SignalName: SIGSYS
SourcePackage: tracker-miners
StacktraceTop:
 __GI_epoll_pwait (epfd=7, events=0xf1c82c00dad8, maxevents=1, timeout=0, set=0x0) at ../sysdeps/unix/sysv/linux/epoll_pwait.c:40
 ?? () from /lib/aarch64-linux-gnu/libmount.so.1
 0x0000f1c830ad29c8 [PAC] in mnt_monitor_get_fd () from /lib/aarch64-linux-gnu/libmount.so.1
 0x0000f1c8318df734 [PAC] in ?? () from /lib/aarch64-linux-gnu/libgio-2.0.so.0
 0x0000f1c83184b618 [PAC] in ?? () from /lib/aarch64-linux-gnu/libgio-2.0.so.0
Title: tracker-extract-3 crashed with SIGSYS in __GI_epoll_pwait()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
separator:

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!

[Seth Arnold (seth-arnold)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.