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

Bug #832535 reported by haug
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

Do not know why teh control center crash

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-9.13-generic-pae 3.0.3
Uname: Linux 3.0.0-9-generic-pae i686
Architecture: i386
Date: Wed Aug 24 08:26:49 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: gnome-control-center display
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb6fe9f4c: mov (%esi),%eax
 PC (0xb6fe9f4c) ok
 source "(%esi)" (0x00000057) 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-08-24 (0 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev powerdev sambashare tape vboxusers video

Revision history for this message
haug (josefa4) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #808121, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
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.