xdg-desktop-portal crashed with SIGSEGV in ffi_call()

[Sébastien]

mhhh

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: xdg-desktop-portal 1.16.0-2ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 6 16:32:56 2023
ExecutablePath: /usr/libexec/xdg-desktop-portal
InstallationDate: Installed on 2023-08-06 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230805)
JournalErrors:
 Aug 06 16:33:03 username-acer-aspire systemd[1734]: xdg-desktop-portal.service: Main process exited, code=dumped, status=11/SEGV
 Aug 06 16:33:03 username-acer-aspire systemd[1734]: xdg-desktop-portal.service: Failed with result 'core-dump'.
 Aug 06 16:33:03 username-acer-aspire firefox[3665]: Can't open portal file chooser: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
ProcCmdline: /usr/libexec/xdg-desktop-portal
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x558f5aaa5afb: mov (%r14),%rdi
 PC (0x558f5aaa5afb) ok
 source "(%r14)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xdg-desktop-portal
StacktraceTop:
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libffi.so.8
 ?? () from /lib/x86_64-linux-gnu/libffi.so.8
 ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8
 g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: xdg-desktop-portal crashed with SIGSEGV in ffi_call()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

[Paulo Flabiano Smorigo (pfsmorigo)]

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.