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

Bug #1696395 reported by Jean-Baptiste Lallement on 2017-06-07
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)

Bug Description

Test Case
1. In a live session, open system settings
2. Click on 'Users'

Expected result
The 'users' panel opens (even if I think the 'users' panel should not be there at all)

Actual result
This crash

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.24.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jun 7 10:37:41 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-09-03 (1372 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcCmdline: gnome-control-center --overview
 PATH=(custom, no user)
 Segfault happened at: 0x55c78b9944f8 <um_carousel_select_item+104>: mov 0x48(%rsi),%eax
 PC (0x55c78b9944f8) ok
 source "0x48(%rsi)" (0x00000048) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
 um_carousel_select_item ()
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/
 () at /usr/lib/x86_64-linux-gnu/
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/
Title: gnome-control-center crashed with SIGSEGV in um_carousel_select_item()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Jean-Baptiste Lallement (jibel) wrote :
information type: Private → Public Security
information type: Public Security → Public

 um_carousel_select_item (self=0x55c78de65520, item=0x0) at um-carousel.c:212
 reload_users (d=0x55c78d8fc440, selected_user=0x55c78dbfaec0) at um-user-panel.c:299
 g_closure_invoke (closure=0x55c78e06b900, return_value=return_value@entry=0x0, n_param_values=2, param_values=param_values@entry=0x7ffdbce75730, invocation_hint=invocation_hint@entry=0x7ffdbce756b0) at ../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x55c78e0204e0, detail=detail@entry=0, instance=instance@entry=0x55c78dbfadb0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7ffdbce75730) at ../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7ffdbce758f0) at ../../../../gobject/gsignal.c:3391

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Jeremy Bicha (jbicha) on 2017-06-27
tags: added: gnome-17.10
Changed in gnome-control-center (Ubuntu):
status: Confirmed → Triaged
importance: Medium → High
Changed in gnome-control-center:
importance: Unknown → Medium
status: Unknown → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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