crashed with SIGSEGV in gtk_widget_get_ancestor()gnome control center cra

Bug #921342 reported by Rob Whyte
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Low
Unassigned

Bug Description

gnome-control-center crashed whilst in the clock tab from time and date

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.2.2-2ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic-pae 3.2.1
Uname: Linux 3.2.0-10-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Wed Jan 25 12:23:04 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: gnome-control-center bluetooth
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb7581853 <gtk_widget_get_ancestor+115>: mov 0x4c(%eax),%esi
 PC (0xb7581853) ok
 source "0x4c(%eax)" (0xaaaaaaf6) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 gtk_widget_get_ancestor () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 atk_object_ref_state_set () from /usr/lib/i386-linux-gnu/libatk-1.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_widget_get_ancestor()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo
usr_lib_gnome-control-center:
 deja-dup 21.2-0ubuntu4
 gnome-bluetooth 3.2.1-1ubuntu4
 indicator-datetime 0.3.1-0ubuntu4

Revision history for this message
Rob Whyte (fudge) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_widget_get_ancestor (widget=<optimized out>, widget_type=3109848104) at /build/buildd/gtk+3.0-3.3.10/./gtk/gtkwidget.c:9645
 gtk_widget_accessible_on_screen (widget=0xb9744c50) at /build/buildd/gtk+3.0-3.3.10/./gtk/a11y/gtkwidgetaccessible.c:758
 gtk_widget_accessible_ref_state_set (accessible=0xb97ca408) at /build/buildd/gtk+3.0-3.3.10/./gtk/a11y/gtkwidgetaccessible.c:354
 gtk_label_accessible_ref_state_set (accessible=0xb97ca408) at /build/buildd/gtk+3.0-3.3.10/./gtk/a11y/gtklabelaccessible.c:170
 atk_object_ref_state_set (accessible=0xb97ca408) at atkobject.c:966

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
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.

visibility: private → public
Changed in gnome-control-center (Ubuntu):
importance: Medium → Low
status: New → Incomplete
Revision history for this message
Rob Whyte (fudge) wrote :

Hi,
seems to be resolved.
can not re-produce now.
Recommend closing this bug.
Thank you

tags: added: amd64
Revision history for this message
Jeremy Lincicome (w0jrl1) wrote :

I can reproduce this bug with the latest updates on 12.04 64 bit. I noticed the crash when trying to change settings in the privacy dialog.
1. Go to System settings.
2. Click onn Privacy.
3. Try to make a change to the settings on the files tab.
It might take several tries to cause a crash. The crashes are random.

Changed in gnome-control-center (Ubuntu):
status: Incomplete → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

closing since the submitter can reproduce

@Jeremy: your issue is with the privacy capplet and another bug, please submit a new bug report

Changed in gnome-control-center (Ubuntu):
status: New → Invalid
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.