vlc crashed with SIGSEGV in QDBusAdaptorConnector::relaySlot()

[Marco]

Binary package hint: vlc

i have an issue opening a file with vlc on kde 4.6...after reboot of my system, i have this crash

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: vlc-nox 1.1.7-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-4.31-generic 2.6.38-rc5
Uname: Linux 2.6.38-4-generic x86_64
Architecture: amd64
Date: Fri Feb 18 17:20:43 2011
ExecutablePath: /usr/bin/vlc
ProcCmdline: /usr/bin/vlc /home/User Name/Download/the.big.bang.theory.s04e16.hdtv.xvid-fqm.avi
ProcEnviron:
 LANGUAGE=it_IT
 LANG=it_IT.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1955456b1b <QDBusAdaptorConnector::relaySlot(void**)+11>: mov 0x8(%rax),%edx
 PC (0x7f1955456b1b) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: vlc
StacktraceTop:
 QDBusAdaptorConnector::relaySlot (this=0x2d5d990, argv=0x7fff38c39d10) at qdbusabstractadaptor.cpp:270
 QDBusAdaptorConnector::qt_metacall (this=0x2d5d990, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff38c39d10) at qdbusabstractadaptor.cpp:366
 QMetaObject::activate (sender=0x2d5dae0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff38c39d10) at kernel/qobject.cpp:3280
 QObject::destroyed (this=<value optimized out>, _t1=0x2d5dae0) at .moc/release-shared/moc_qobject.cpp:149
 QObject::~QObject (this=0x2d5dae0, __in_chrg=<value optimized out>) at kernel/qobject.cpp:842
Title: vlc crashed with SIGSEGV in QDBusAdaptorConnector::relaySlot()
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 #718479, 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.