xdg-desktop-portal-gtk crashed with SIGSEGV in FcPatternGetString()

[Gene Soo]

Crash occurred after installing ubuntu-desktop on Live server daily 22.10 and running normal operations.

ProblemType: Crash
DistroRelease: Ubuntu 22.10
Package: xdg-desktop-portal-gtk 1.14.0-1build1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.22.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 11 14:37:08 2022
ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk
InstallationDate: Installed on 2022-07-10 (1 days ago)
InstallationMedia: Ubuntu-Server 22.10 "Kinetic Kudu" - Alpha amd64 (20220709)
JournalErrors: -- No entries --
ProcCmdline: /usr/libexec/xdg-desktop-portal-gtk
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f960aba37f3: mov (%r8,%rdx,1),%edx
 PC (0x7f960aba37f3) ok
 source "(%r8,%rdx,1)" (0xff2c4435b0b8) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xdg-desktop-portal-gtk
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
 FcPatternGetString () from /lib/x86_64-linux-gnu/libfontconfig.so.1
 ?? () from /lib/x86_64-linux-gnu/libpangoft2-1.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libpangoft2-1.0.so.0
Title: xdg-desktop-portal-gtk crashed with SIGSEGV in FcPatternGetString()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lxd plugdev sudo
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 #1964526, 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.