vlc crashed with SIGSEGV in QMetaObject::activate()

[archy]

Binary package hint: vlc

vlc crashes always after regarding a video ( mpeg),
stopping a video an closing vlc,
brings up the crash report..
This happens since upgrading to karmic via kpackage..
I have deinstalled the vlc-pulse-audio-plugin via synaptic,
after reboot, no more indications abaout pulse-audio,
but the crashes in vlc are still alive.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Nov 10 22:01:28 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/vlc
NonfreeKernelModules: nvidia
Package: vlc-nox 1.0.2-1ubuntu2
ProcCmdline: /usr/bin/vlc
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0xc06846: mov 0x4(%edx),%ecx
 PC (0x00c06846) 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::activate(QObject*, int, int, void**) ()
 QMetaObject::activate(QObject*, QMetaObject const*, int, int, void**) () from /usr/lib/libQtCore.so.4
 QObject::destroyed(QObject*) () from /usr/lib/libQtCore.so.4
Title: vlc crashed with SIGSEGV in QMetaObject::activate()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio avahi avahi-autoipd cdrom daemon dialout dip floppy fuse lpadmin mysql mythtv netdev ntp nx plugdev sambashare staff sudo users video www-data
XsessionErrors: (polkit-gnome-authentication-agent-1:1926): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' 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 #408719, 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.