xdg-desktop-portal-gnome crashed with SIGSEGV in wl_proxy_get_version()

[Dean Trautner]

Clicked to download something when browsing on Google Chrome browser (commonly used browser) and encountered some internal error.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: xdg-desktop-portal-gnome 42.0.1-1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 3 00:32:59 2022
ExecutablePath: /usr/libexec/xdg-desktop-portal-gnome
InstallationDate: Installed on 2022-04-03 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcCmdline: /usr/libexec/xdg-desktop-portal-gnome
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f66059ede94 <wl_proxy_get_version+4>: mov 0x40(%rdi),%eax
 PC (0x7f66059ede94) ok
 source "0x40(%rdi)" (0x00000040) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xdg-desktop-portal-gnome
StacktraceTop:
 wl_proxy_get_version () from /lib/x86_64-linux-gnu/libwayland-client.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: xdg-desktop-portal-gnome crashed with SIGSEGV in wl_proxy_get_version()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare 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 #1966784, 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.