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

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

Bug Description

I opened the control center to adjust the monitors settings. I double clicked on the monitors icon and nothing appeared to happen. I double clicked again and the control center disappeared, and then the control center disappeared. I was then asked if I'd like to submit a bug report, so I did :)

About a minute previously the panel crashed and offered me the chance to submit a report, but I clicked the wrong button and didn't.

I don't appear to be able to reproduce this right now.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.3-0ubuntu4
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic i686
Architecture: i386
Date: Sat Jul 9 22:07:14 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x332f1c: mov (%esi),%eax
 PC (0x00332f1c) ok
 source "(%esi)" (0x00000147) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 gnome_rr_config_new_current () from /usr/lib/libgnome-desktop-3.so.2
 ?? () from /usr/lib/control-center-1/panels/libdisplay.so
Title: gnome-control-center crashed with SIGSEGV in g_object_new_valist()
UpgradeStatus: Upgraded to oneiric on 2011-07-09 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Avi Greenbury (bigreds) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_value_object_collect_value (value=0x21ee3d5c, n_collect_values=1, collect_values=0xbfa5e230, collect_flags=0) at /build/buildd/glib2.0-2.29.10/./gobject/gobject.c:3068
 g_object_new_valist (object_type=568890056, first_property_name=0x7255462 "screen", var_args=0xbfa5e2bc "") at /build/buildd/glib2.0-2.29.10/./gobject/gobject.c:1597
 g_object_new (object_type=568890056, first_property_name=0x7255462 "screen") at /build/buildd/glib2.0-2.29.10/./gobject/gobject.c:1325
 gnome_rr_config_new_current (screen=0x147, error=0x0) at gnome-rr-config.c:733
 on_screen_changed (scr=0x21d0d608, data=0x21e8b790) at xrandr-capplet.c:159

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.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-i386-retrace
Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote : Re: gnome-control-center crashed with SIGSEGV in g_object_new_valist()

Thank you for your bug report, did you get the issue again since?

Changed in gnome-control-center (Ubuntu):
importance: Medium → Low
status: Confirmed → Incomplete
visibility: private → public
summary: - gnome-control-center crashed with SIGSEGV in g_object_new_valist()
+ gnome-control-center crashed with SIGSEGV in gnome_rr_config_new_current
+ ()
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.