vlc crashed with SIGSEGV in QMetaObject::activate()

[sobik2]

Binary package hint: vlc

1)
sobi@sobi-laptop:~$ lsb_release -rdic
Distributor ID: Ubuntu
Description: Ubuntu karmic (development branch)
Release: 9.10
Codename: karmic

2)
sobi@sobi-laptop:~$ apt-cache policy vlc
vlc:
  Instalovaná verze: 1.0.2-1ubuntu1
  Kandidát: 1.0.2-1ubuntu1
  Tabulka verzí:
 *** 1.0.2-1ubuntu1 0
        500 http://cz.archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status

3) clicked VIew -> add Interface -> Web Interface and then
clicked VIew -> add Interface -> Console

4) crash

ProblemType: Crash
Architecture: i386
Date: Sun Oct 4 23:30:28 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/vlc
Package: vlc-nox 1.0.2-1ubuntu1
ProcCmdline: /usr/bin/vlc
ProcEnviron:
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x7ea8846: mov 0x4(%edx),%ecx
 PC (0x07ea8846) 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-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (mmc:21983): GLib-CRITICAL **: g_hash_table_insert_internal: assertion `hash_table != NULL' 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.