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

Bug #1843699 reported by dinamic
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Incomplete
Low
Unassigned

Bug Description

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

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.0.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
Uname: Linux 5.2.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Sep 12 14:06:06 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-12-20 (265 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181214)
ProcCmdline: gnome-control-center
SegvAnalysis:
 Segfault happened at: 0x564c19690cb4 <cc_display_config_set_minimum_size+4>: mov (%rdi),%rax
 PC (0x564c19690cb4) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 cc_display_config_set_minimum_size ()
 ?? ()
 ?? ()
 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

Revision history for this message
dinamic (dinamic6661) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 cc_display_config_set_minimum_size (self=0x0, width=740, height=530) at ../panels/display/cc-display-config.h:139
 reset_current_config (panel=0x564c1bc9e4a0) at ../panels/display/cc-display-panel.c:882
 on_screen_changed (panel=0x564c1bc9e4a0) at ../panels/display/cc-display-panel.c:918
 g_closure_invoke () from /tmp/apport_sandbox_r4e0aw2g/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.0
 signal_emit_unlocked_R () from /tmp/apport_sandbox_r4e0aw2g/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6200.0

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
tags: added: focal
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
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. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

information type: Private → Public
Changed in gnome-control-center (Ubuntu):
importance: Medium → Low
status: Confirmed → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

> CurrentDesktop: Unity:Unity7:ubuntu

could be due to trying to use the settings under a non GNOME environment

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.