gnome-control-center crashed with SIGSEGV in gtk_widget_set_visible()

Bug #1785509 reported by Till Kamppeter
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I opened the Thunderbolt page in the GNOME Control Center hoping to get a Lenovo USB-C Dock charging my Lenovo Thinkpad X1 Yoga. I clicked "Unlock" at the top and after entering my password I got the crash.

Starting GCC again and trying the same thing again I did not get a crash (but also not my laptop getting charged through the docking station).

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-control-center 1:3.29.90-1~ubuntu1
ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
Uname: Linux 4.17.0-6-generic x86_64
ApportVersion: 2.20.10-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 5 21:20:41 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-02-07 (179 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
ProcCmdline: gnome-control-center
SegvAnalysis:
 Segfault happened at: 0x7fe03f71f07d <gtk_widget_set_visible+29>: cmp %rax,(%rdx)
 PC (0x7fe03f71f07d) ok
 source "%rax" ok
 destination "(%rdx)" (0x6974616572632f2f) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 gtk_widget_set_visible () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ()
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_widget_set_visible()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_widget_set_visible (widget=0x55f61a055340, visible=0) at ../../../../gtk/gtkwidget.c:9011
 als_enabled_state_changed (self=0x55f61a00c1b0) at ../panels/power/cc-power-panel.c:1057
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7fff4e7f7ac0, fn=fn@entry=0x55f617982820 <als_enabled_state_changed>, rvalue=<optimized out>, avalue=avalue@entry=0x7fff4e7f79f0) at ../src/x86/ffi64.c:525
 g_cclosure_marshal_generic (closure=0x55f61a013da0, return_gvalue=0x0, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=<optimized out>) at ../../../../gobject/gclosure.c:1496

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-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, you were using a beta version at the time you reported the issue. It might have been fixed after that point, do you still see the problem in the stable 18.10?

Changed in gnome-control-center (Ubuntu):
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in gnome-control-center (Ubuntu):
status: Incomplete → Fix Released
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.