vlc crashed with SIGSEGV in TagLib::String::isEmpty()

[hype]

Binary package hint: vlc

I usually drag a folder containing mp3s into vlc's main window in order to add them to the playlist, while starting to play the first file of the folder straight away.
 In some cases, vlc crashes wihout any error message.

ProblemType: Crash
Architecture: amd64
Date: Wed Aug 26 00:59:03 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/vlc
NonfreeKernelModules: nvidia
Package: vlc-nox 1.0.1-1ubuntu1
ProcCmdline: vlc /media/data/downloads/dnb/VA-Stepback_Sessions_Volume_Two-STEPBACK002-VINYL-2009-sour/a-4hero-mr_kirks_nightmare_(mysterons_remix)-sour.mp3
ProcEnviron:
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
SegvAnalysis:
 Segfault happened at: 0x7f5eedb44948 <_ZNK6TagLib6String7isEmptyEv+8>: cmpq $0x0,-0x18(%rax)
 PC (0x7f5eedb44948) ok
 source "$0x0" ok
 destination "-0x18(%rax)" (0x20676e6968636e5d) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: vlc
StacktraceTop:
 TagLib::String::isEmpty() const ()
 ?? () from /usr/lib/libtag.so.1
 ?? ()
 __module_need () from /usr/lib/libvlccore.so.2
 ?? () from /usr/lib/libvlccore.so.2
Title: vlc crashed with SIGSEGV in TagLib::String::isEmpty()
Uname: Linux 2.6.31-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:TagLib::String::String () from /usr/lib/libtag.so.1
?? () from /usr/lib/libtag.so.1
ReadMeta (p_this=0x19b0358) at taglib.cpp:377
__module_need (p_this=0x19b0358,
InputSourceMeta (p_input=0x1975c08,

[Rémi Denis-Courmont (rdenis)]

Do you happen to have a sample to legally share?

[Benjamin Drung (bdrung)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Harald Sitter (apachelogger)]

 Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!