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

[Seth Arnold]

I upgraded from 12.10 to Raring; I opened the control center and went through most of the subwindows.

The crash happened when the window was partially covered by a terminal window and left idle for ten or fifteen seconds.

Thanks

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-control-center 1:3.6.3-0ubuntu15
ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Sun Mar 17 23:36:12 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2012-10-18 (151 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff60892e7ba: movzbl 0x4(%rdx),%eax
 PC (0x7ff60892e7ba) ok
 source "0x4(%rdx)" (0xaaaaaaaaaaaaaaae) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_image_set_from_gicon () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_image_set_from_gicon()
UpgradeStatus: Upgraded to raring on 2013-03-18 (0 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu6.1
 deja-dup 25.5-0ubuntu1
 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1
 indicator-datetime 12.10.3daily13.03.07-0ubuntu1

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1041921, 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.