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

Bug #811631 reported by Removed by request
10
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

crash on startup

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
Architecture: i386
Date: Thu Jul 14 18:57:46 2011
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
ProcCmdline: gnome-control-center background
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x639b6e <g_timer_stop+30>: andb $0xfe,0x10(%esi)
 PC (0x00639b6e) ok
 source "$0xfe" ok
 destination "0x10(%esi)" (0xaaaaaaba) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_timer_stop (timer=0xaaaaaaaa) at /build/buildd/glib2.0-2.29.10/./glib/gtimer.c:148
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 g_timeout_dispatch (source=0x20c0eb40, callback=0x122bf0, user_data=0x20c2f100) at /build/buildd/glib2.0-2.29.10/./glib/gmain.c:3946
 g_main_dispatch (context=0x20b08518) at /build/buildd/glib2.0-2.29.10/./glib/gmain.c:2473
Title: gnome-control-center crashed with SIGSEGV in g_timer_stop()
UpgradeStatus: Upgraded to oneiric on 2011-06-24 (20 days ago)
UserGroups: adm admin cdrom dialout kmem lpadmin nvram plugdev sambashare

Revision history for this message
Removed by request (removed3500789) 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 #806196, 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.