gnome-shell crashed with SIGSEGV in g_simple_async_result_complete()

[tctwyan]

Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
gnome-shell:
  已安裝：3.10.4-0ubuntu3
  候選： 3.10.4-0ubuntu3
  版本列表：
 *** 3.10.4-0ubuntu3 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-shell 3.10.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-13.33-generic 3.13.5
Uname: Linux 3.13.0-13-generic i686
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Feb 28 23:02:25 2014
Disassembly: => 0x610077: Cannot access memory at address 0x610077
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2014-01-18 (41 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 (20131017)
ProcCmdline: gnome-shell --mode=gdm
SegvAnalysis:
 Segfault happened at: 0x610077: Cannot access memory at address 0x610077
 PC (0x00610077) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so
 ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so
 g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to trusty on 2014-02-22 (6 days ago)
UserGroups:

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