tracker-extract crashed with signal 31 in __GI___fstatat64()

[(J)Aloittelija]

N/A

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: tracker-extract 2.3.5-2
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CrashCounter: 1
Date: Sun Feb 28 08:33:31 2021
ExecutablePath: /usr/libexec/tracker-extract
InstallationDate: Installed on 2020-08-22 (189 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcCmdline: /usr/libexec/tracker-extract
ProcEnviron:
 LANG=fi_FI.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
Signal: 31
SourcePackage: tracker-miners
StacktraceTop:
 __GI___fstatat64 (fd=fd@entry=15, file=file@entry=0x7f1a389c1cd6 "", buf=buf@entry=0x7f1a1c9f5890, flag=flag@entry=4096) at ../sysdeps/unix/sysv/linux/fstatat64.c:105
 __GI___fstat64 (fd=fd@entry=15, buf=buf@entry=0x7f1a1c9f5890) at ../sysdeps/unix/sysv/linux/fstat64.c:29
 _nl_load_domain (domain_file=0x7f19e000f7d0, domainbinding=domainbinding@entry=0x7f19e00107e0) at loadmsgcat.c:805
 _nl_find_domain (dirname=dirname@entry=0x7f1a389c9b00 <_nl_default_dirname> "/usr/share/locale", locale=locale@entry=0x7f1a1c9f59f0 "fi", domainname=domainname@entry=0x7f1a1c9f5a10 "LC_MESSAGES/gnome-control-center-2.0.mo", domainbinding=domainbinding@entry=0x7f19e00107e0) at finddomain.c:166
 __dcigettext (domainname=<optimized out>, msgid1=<optimized out>, msgid2=<optimized out>, plural=<optimized out>, n=<optimized out>, category=<optimized out>) at dcigettext.c:702
Title: tracker-extract crashed with signal 31 in __GI___fstatat64()
UpgradeStatus: Upgraded to hirsute on 2021-02-07 (20 days ago)
UserGroups: N/A
separator:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1916323, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.