gnome-shell-extension-prefs crashed with SIGSEGV in gtk_container_real_check_resize()

Bug #1762397 reported by Rachel Greenham
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Expired
Low
Unassigned

Bug Description

It was a bit delayed but I think this probably relates to extension gnome-display-switcher, which is probably in need of an update. The configuration dialogue was failing to open either from the extensions site or the tweak-tool extensions tab... then this error appeared.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 9 12:57:42 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell-extension-prefs
InstallationDate: Installed on 2017-08-07 (244 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell-extension-prefs extension:///<email address hidden>
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6c4aa381c9: callq 0x7f6c4ac54380
 PC (0x7f6c4aa381c9) ok
 source "0x7f6c4ac54380" (0x7f6c4ac54380) ok
 destination "(%rsp)" (0x7ffc1a53bff0) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell-extension-prefs crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: Upgraded to bionic on 2018-03-10 (29 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Rachel Greenham (rachel-strangenoises) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_container_real_check_resize (container=0x564575170df0) at ../../../../gtk/gtkcontainer.c:2182
 _g_closure_invoke_va (closure=0x564574c501f0, return_value=0x0, instance=0x564575170df0, args=0x7ffc1a53c260, n_params=0, param_types=0x0) at ../../../../gobject/gclosure.c:867
 g_signal_emit_valist (instance=0x564575170df0, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffc1a53c260) at ../../../../gobject/gsignal.c:3300
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at ../../../../gobject/gsignal.c:3447
 g_closure_invoke (closure=0x5645751b9ee0, return_value=0x0, n_param_values=2, param_values=0x7ffc1a53c500, invocation_hint=0x7ffc1a53c480) at ../../../../gobject/gclosure.c:804

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 gnome-shell (Ubuntu):
importance: Undecided → Medium
summary: gnome-shell-extension-prefs crashed with SIGSEGV in
- g_signal_emit_valist()
+ gtk_container_real_check_resize()
tags: removed: need-amd64-retrace
Changed in gnome-shell (Ubuntu):
importance: Medium → Low
information type: Private → Public
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I can't find any other crashes that look like this. Is it still happening?

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
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.