gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete()

[arpanaut]

Just did update/upgrade 8/23/11, rebooted and got crash and apport made this report.
Oneric Alpha 3+

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-9.13-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
Architecture: i386
Date: Tue Aug 23 12:44:57 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110628)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x6d52f6d: mov 0x8(%edx),%edx
 PC (0x06d52f6d) ok
 source "0x8(%edx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libmedia-keys.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
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[crtm (carlosrtm)]

after update, crash

[Anders Feder (afeder)]

Unity seems to have crashed for me, too.

[Apport retracing service (apport)]

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 #832603, 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.

[arpanaut (johnmac)]

bug #832603, was reported 15 hours after this one, but this bug is the duplicate?
OKAY
At the time I reported, launchpad said there was no similar bugs and automatically reported this as new, just saying?