xdg-desktop-portal-gnome crashed with SIGSEGV in gtk_tree_view_update_rubber_band_selection_range.constprop.0()

Bug #1966529 reported by Marco Antonio Molinari
48
This bug affects 7 people
Affects Status Importance Assigned to Milestone
GTK+
Fix Released
Unknown
gtk4 (Ubuntu)
Fix Committed
High
Unassigned
xdg-desktop-portal-gnome (Ubuntu)
Invalid
High
Unassigned

Bug Description

https://errors.ubuntu.com/problem/44bd0ca893055a3c496a03038023a8d0d4860802

---

Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04

xdg-desktop-portal-gnome:
  Instalado: 42.0.1-1
  Candidato: 42.0.1-1
  Tabela de versão:
 *** 42.0.1-1 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status

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-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Fri Mar 25 20:29:58 2022
ExecutablePath: /usr/libexec/xdg-desktop-portal-gnome
ProcCmdline: /usr/libexec/xdg-desktop-portal-gnome
SegvAnalysis:
 Segfault happened at: 0x7fe18cf2c03f: movzwl (%rsi),%edx
 PC (0x7fe18cf2c03f) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xdg-desktop-portal-gnome
StacktraceTop:
 ?? () 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
 ?? () 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 g_signal_emit_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
separator:

Revision history for this message
Marco Antonio Molinari (iranilom) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_tree_view_update_rubber_band_selection_range.constprop.0 (tree_view=0x55abde698b90, start_tree=<optimized out>, start_node=<optimized out>, end_node=0x55abdeba7040, select=1, skip_start=<optimized out>, skip_end=0, end_tree=<optimized out>) at ../../../gtk/gtktreeview.c:3796
 gtk_tree_view_update_rubber_band_selection (tree_view=0x55abde698b90) at ../../../gtk/gtktreeview.c:3899
 gtk_tree_view_update_rubber_band (tree_view=tree_view@entry=0x55abde698b90) at ../../../gtk/gtktreeview.c:4018
 gtk_tree_view_drag_gesture_update (gesture=0x7fe178011160, offset_x=<optimized out>, offset_y=<optimized out>, tree_view=0x55abde698b90) at ../../../gtk/gtktreeview.c:4112
 _gtk_marshal_VOID__DOUBLE_DOUBLEv (closure=<optimized out>, return_value=<optimized out>, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x55abde3d0b40) at gtk/gtkmarshalers.c:4147

tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xdg-desktop-portal-gnome (Ubuntu):
importance: Undecided → Medium
summary: - xdg-desktop-portal-gnome crashed with SIGSEGV in g_signal_emit_valist()
+ xdg-desktop-portal-gnome crashed with SIGSEGV in
+ gtk_tree_view_update_rubber_band_selection_range.constprop.0()
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu that you are using.

Thank you!

Changed in xdg-desktop-portal-gnome (Ubuntu):
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in xdg-desktop-portal-gnome (Ubuntu):
importance: Medium → High
status: Incomplete → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

seems to be a gtk issue reported upstream on https://gitlab.gnome.org/GNOME/gtk/-/issues/4453

description: updated
information type: Private → Public
Changed in gtk+3.0 (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Changed in gtk:
status: Unknown → New
affects: gtk+3.0 (Ubuntu) → ubuntu
affects: ubuntu → gtk4 (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in xdg-desktop-portal-gnome (Ubuntu):
status: Confirmed → Invalid
Changed in gtk4 (Ubuntu):
status: Confirmed → Fix Committed
Changed in gtk:
status: New → Fix Released
Revision history for this message
Raphaël Droz (raphael-droz) wrote :

Dears,
GTK 4.6.7 was released three weeks ago (https://gitlab.gnome.org/GNOME/gtk/-/tags/4.6.7)

Could we hope for a package update release anytime soon?

Revision history for this message
Mat (mathiascode) wrote :

Could GTK 4.6.9 be packaged for Ubuntu 22.04 in the near future to resolve this issue? Thank you.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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