unity-2d-places crashed with SIGSEGV in QScriptValue::call()

[JP]

I stopped and then enter the warning came to report the error

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-places 4.12.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Fri Oct 7 05:13:10 2011
ExecutablePath: /usr/bin/unity-2d-places
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2)
ProcCmdline: /usr/bin/unity-2d-places
SegvAnalysis:
 Segfault happened at: 0x62c7726 <_ZN12QScriptValue4callERKS_RK5QListIS_E+1158>: mov %edi,0x88(%eax)
 PC (0x062c7726) ok
 source "%edi" ok
 destination "0x88(%eax)" (0x00aad550) in non-writable VMA region: 0x00a9e000-0x00aaf000 r--p /usr/lib/i386-linux-gnu/libQtDeclarative.so.4.7.4
SegvReason: writing VMA /usr/lib/i386-linux-gnu/libQtDeclarative.so.4.7.4
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 QScriptValue::call(QScriptValue const&, QList<QScriptValue> const&) () from /usr/lib/i386-linux-gnu/libQtScript.so.4
 ?? () from /usr/lib/i386-linux-gnu/libQtDeclarative.so.4
 ?? () from /usr/lib/i386-linux-gnu/libQtDeclarative.so.4
 ?? () from /usr/lib/i386-linux-gnu/libQtDeclarative.so.4
 ?? () from /usr/lib/i386-linux-gnu/libQtDeclarative.so.4
Title: unity-2d-places crashed with SIGSEGV in QScriptValue::call()
UpgradeStatus: Upgraded to oneiric on 2011-09-28 (8 days ago)
UserGroups: adm admin lpadmin sambashare
XsessionErrors:
 (nautilus:1494): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (nautilus:1494): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (firefox:1803): Gtk-CRITICAL **: IA__gtk_widget_get_display: assertion `GTK_IS_WIDGET (widget)' failed

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