gnome-shell-extension-prefs crashed with SIGSEGV in gtk_css_gadget_set_state() from gtk_switch_state_flags_changed()

[Prasanna Loganathar]

https://errors.ubuntu.com/problem/b9099237efc0ed3a713ac34e260c33a215c4599d

Crashes when updating extensions using gnome-tweaks on Gnome 3.32+

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0+git20190410-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Apr 21 19:32:17 2019
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell-extension-prefs
InstallationDate: Installed on 2019-01-01 (110 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcCmdline: gnome-shell-extension-prefs <email address hidden>
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f32337f2a77: mov (%rdi,%rax,1),%rdi
 PC (0x7f32337f2a77) ok
 source "(%rdi,%rax,1)" (0xffffffffffffffd0) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_cclosure_marshal_VOID__UINTv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell-extension-prefs crashed with SIGSEGV
UpgradeStatus: Upgraded to disco on 2019-04-19 (2 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-01-15T04:51:59.517661
separator:

[Apport retracing service (apport)]

StacktraceTop:
 gtk_css_gadget_set_state (gadget=0x0, state=state@entry=GTK_STATE_FLAG_DIR_LTR) at ../../../../gtk/gtkcssgadget.c:413
 gtk_switch_state_flags_changed (widget=0x561618fca200, previous_state_flags=(GTK_STATE_FLAG_DIR_LTR | GTK_STATE_FLAG_CHECKED)) at ../../../../gtk/gtkswitch.c:630
 g_cclosure_marshal_VOID__UINTv (closure=<optimized out>, return_value=<optimized out>, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x561618916a80) at ../../../gobject/gmarshal.c:704
 _g_closure_invoke_va (closure=0x561618916a30, return_value=0x0, instance=0x561618fca200, args=0x7fffd6343c30, n_params=1, param_types=0x561618916a80) at ../../../gobject/gclosure.c:873
 g_signal_emit_valist (instance=0x561618fca200, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fffd6343c30) at ../../../gobject/gsignal.c:3300

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

I'm hoping this is fixed. There have been no reports since 3.36.0.