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

[David Alvarado]

I was in the process of exporting favorites from Microsoft Edge into Google Web when this error occured.

Thank you,

David Alvarado
<email address hidden>

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: xdg-desktop-portal-gnome 42.0.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 10 12:38:35 2022
ExecutablePath: /usr/libexec/xdg-desktop-portal-gnome
InstallationDate: Installed on 2022-04-10 (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: 0x7faaa7432a36: cmpq $0x0,(%r12)
 PC (0x7faaa7432a36) ok
 source "$0x0" ok
 destination "(%r12)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: xdg-desktop-portal-gnome
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libpango-1.0.so.0
 pango_layout_get_cursor_pos () from /lib/x86_64-linux-gnu/libpango-1.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: xdg-desktop-portal-gnome crashed with SIGSEGV in pango_layout_get_cursor_pos()
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 #1968492, 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.