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

Bug #811339 reported by André Gondim on 2011-07-16
82
This bug affects 13 people
Affects Status Importance Assigned to Milestone
gnome-control-center
Expired
Critical
gnome-control-center (Ubuntu)
Critical
Bryce Harrington

Bug Description

I just input a HDMI monitor

[Next Action]
* Determine reproducibility of the bug (and test case)
* [Engineering] Investigate why screens was 0x0 in this case
* [Engineering] Determine if bailing early is the proper way to handle this error condition

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Fri Jul 15 21:55:10 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb40b112 <gnome_rr_config_load_current+146>: mov (%eax),%edi
 PC (0x0b40b112) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 gnome_rr_config_load_current () from /usr/lib/libgnome-desktop-3.so.2
 gnome_rr_config_new_current () from /usr/lib/libgnome-desktop-3.so.2
 ?? () from /usr/lib/control-center-1/panels/libdisplay.so
 g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gnome_rr_config_load_current()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

André Gondim (andregondim) wrote :
visibility: private → public

StacktraceTop:
 gnome_rr_config_load_current (config=0x2130fb28, error=0x0) at gnome-rr-config.c:509
 gnome_rr_config_new_current (screen=0x0, error=0x0) at gnome-rr-config.c:735
 on_screen_changed (scr=0x21195e40, data=0x212d1670) at xrandr-capplet.c:159
 g_cclosure_marshal_VOID__VOID (closure=0x212b6958, return_value=0x0, n_param_values=1, param_values=0x2133ed90, invocation_hint=0xbfe19130, marshal_data=0x0) at /build/buildd/glib2.0-2.29.10/./gobject/gmarshal.c:85
 g_closure_invoke (closure=0x212b6958, return_value=0x0, n_param_values=1, param_values=0x2133ed90, invocation_hint=0xbfe19130) at /build/buildd/glib2.0-2.29.10/./gobject/gclosure.c:773

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=655003

Changed in gnome-control-center (Ubuntu):
status: New → Triaged
Changed in gnome-control-center:
importance: Unknown → Critical
status: Unknown → New
Bryce Harrington (bryce) wrote :

[The Design Team has identified this as a blocker issue for precise, so setting the Importance to Critical. This may be adjusted down once the bug has received further design and engineering analysis, if appropriate.]

Changed in gnome-control-center (Ubuntu):
importance: Medium → Critical
Bryce Harrington (bryce) wrote :

Looks like in the recent refactoring work they forgot to check the rr_outputs pointer before dereferencing it.

Easy enough to check for this situation and bail, but not 100% this is the right way to solve this bug.

The real question is why screens was undefined to begin with.

Bryce Harrington (bryce) wrote :

Andrè, are you able to reproduce this bug fairly easily? Can you describe the steps that lead to this crash?

tags: added: precise
Changed in gnome-control-center (Ubuntu):
assignee: nobody → Bryce Harrington (bryce)
description: updated

The attachment "bail_if_no_screens.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
Bryce Harrington (bryce) wrote :

@Andrè, ping?

Bryce Harrington (bryce) wrote :

[Expired]

Changed in gnome-control-center (Ubuntu):
status: Triaged → Invalid
Changed in gnome-control-center:
status: New → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

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