vlc crashed with SIGSEGV in QDBusAdaptorConnector::relaySlot()

[ComPerkins]

Binary package hint: vlc

i watch a video on VLC and stop it a short time later; i start to shutdown the system and saw in the meanwhile an indicator message that vlc has crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: vlc-nox 1.1.8-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
CrashCounter: 1
Date: Mon Apr 11 03:03:31 2011
ExecutablePath: /usr/bin/vlc
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110301.4)
ProcCmdline: /usr/bin/vlc
ProcEnviron:
 LANGUAGE=de_DE
 LANG=de_DE.UTF-8
 LC_MESSAGES=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x6c5a476 <QDBusAdaptorConnector::relaySlot(void**)+22>: mov 0x4(%edx),%ecx
 PC (0x06c5a476) ok
 source "0x4(%edx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: vlc
StacktraceTop:
 QDBusAdaptorConnector::relaySlot (this=0xa274878, argv=0xbfd283e8) at qdbusabstractadaptor.cpp:270
 QDBusAdaptorConnector::qt_metacall (this=0xa274878, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfd283e8) at qdbusabstractadaptor.cpp:366
 QMetaObject::metacall (object=0xa274878, cl=QMetaObject::InvokeMetaMethod, idx=4, argv=0xbfd283e8) at kernel/qmetaobject.cpp:237
 QMetaObject::activate (sender=0xa279f30, m=0x4432230, local_signal_index=0, argv=0xbfd283e8) at kernel/qobject.cpp:3287
 QObject::destroyed (this=0xa279f30, _t1=0xa279f30) at .moc/release-shared/moc_qobject.cpp:149
Title: vlc crashed with SIGSEGV in QDBusAdaptorConnector::relaySlot()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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