vlc crashed with SIGSEGV in QMetaObject::metacall()

[[e-mail]]

Binary package hint: vlc

VLC refuses to play videos, it does not recognize ... nothing appears on the playlist

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: vlc-nox 1.1.7-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Sun Feb 27 15:50:45 2011
ExecutablePath: /usr/bin/vlc
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/bin/vlc /home/User Name/Téléchargements/arthur123.avi
ProcEnviron:
 LANGUAGE=fr_FR:en
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7449616: mov 0x4(%edx),%ecx
 PC (0x07449616) 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:
 ?? () from /usr/lib/libQtDBus.so.4
 ?? () from /usr/lib/libQtDBus.so.4
 QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
 QObject::destroyed(QObject*) () from /usr/lib/libQtCore.so.4
Title: vlc crashed with SIGSEGV in QMetaObject::metacall()
UserGroups: Slmodemd adm admin audio avahi avahi-autoipd backup bin cdrom clamav couchdb crontab daemon dialout dip disk fax floppy fuse games gdm gnats haldaemon irc kmem libuuid list lp lpadmin mail man messagebus mlocate netdev news nopasswdlogin operator plugdev proxy pulse pulse-access root rtkit sambashare saned sasl shadow src ssh ssl-cert staff sudo sys syslog tape tty users utempter utmp uucp video voice www-data

[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.