gnome-shell crashed with SIGSEGV in atk_object_notify_state_change()

[12th]

error on startup

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-shell 3.6.3.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
Uname: Linux 3.8.0-11-generic i686
ApportVersion: 2.9-0ubuntu2
Architecture: i386
Date: Wed Mar 6 21:36:06 2013
DisplayManager: lightdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.desktop.interface' b'cursor-theme' b"'KnotVista'"
 b'org.gnome.desktop.interface' b'document-font-name' b"'Ubuntu 11'"
 b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu 13'"
InstallationDate: Installed on 2012-09-05 (182 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb5e2af61 <atk_object_notify_state_change+49>: cmp %eax,(%edx)
 PC (0xb5e2af61) ok
 source "%eax" ok
 destination "(%edx)" (0x00000005) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 atk_object_notify_state_change () from /usr/lib/i386-linux-gnu/libatk-1.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libclutter-1.0.so.0
 g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in atk_object_notify_state_change()
UpgradeStatus: Upgraded to raring on 2013-03-03 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #963925, 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.