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

Bug #1967612 reported by DSHR
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xdg-desktop-portal-gnome (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Crash occured during file open dialog in google-chrome only in a wayland session.

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
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 2 14:15:07 2022
ExecutablePath: /usr/libexec/xdg-desktop-portal-gnome
InstallationDate: Installed on 2021-12-31 (91 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
ProcCmdline: /usr/libexec/xdg-desktop-portal-gnome
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/yash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7fd3651c4e94 <wl_proxy_get_version+4>: mov 0x40(%rdi),%eax
 PC (0x7fd3651c4e94) 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: Upgraded to jammy on 2022-03-21 (11 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
DSHR (s-heuer) wrote :
Revision history for this message
DSHR (s-heuer) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

tags: removed: need-amd64-retrace
Revision history for this message
DSHR (s-heuer) wrote :

Couldn't find xdg-desktop-portal-gnome=41.1-2 for a test with the previous version ...

no longer affects: xdg-desktop-portal-gnome (Fedora)
Revision history for this message
DSHR (s-heuer) wrote :

Can't see the duplicate bug because its private :-(

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xdg-desktop-portal-gnome (Ubuntu):
status: New → Confirmed
Revision history for this message
DSHR (s-heuer) wrote :

Setting the chrome://flags Preferred Ozone platform to Auto works around the problem in Google Chrome

Documentation:
Selects the preferred platform backend used on Linux. The default one is "X11". "Auto" selects Wayland if possible, X11 otherwise. – Linux

#ozone-platform-hint

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.