unity-panel-service crashed with SIGSEGV in g_dbus_proxy_call()

[lostprophet]

wanted to move files by drag and drop ... system froze

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: unity-services 6.12.0daily13.03.11-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,place,imgpng,mousepoll,unitymtgrabhandles,gnomecompat,session,grid,regex,snap,move,resize,vpswitch,animation,wall,fade,expo,scale,workarounds,ezoom,unityshell]
Date: Tue Mar 12 13:49:04 2013
ExecutablePath: /usr/lib/unity/unity-panel-service
MarkForUpload: True
ProcCmdline: /usr/lib/unity/unity-panel-service
SegvAnalysis:
 Segfault happened at: 0x7f881dc50cc8: mov (%rbx),%rdx
 PC (0x7f881dc50cc8) ok
 source "(%rbx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_dbus_proxy_call () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_dbus_proxy_call()
UpgradeStatus: Upgraded to raring on 2013-03-11 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

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