Version: (using KDE 4.1.2) OS: Linux Installed from: Ubuntu Packages Anwendung: Dragon Player (dragon), Signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0x7f230a2206f0 (LWP 10454)] [New Thread 0x4203f950 (LWP 10455)] [KCrash handler] #5 0x00007f23071f2690 in strlen () from /lib/libc.so.6 #6 0x00007f23071bb44e in vfprintf () from /lib/libc.so.6 #7 0x00007f230726cd18 in __vsnprintf_chk () from /lib/libc.so.6 #8 0x00007f230781bfad in ?? () from /usr/lib/libxine.so.1 #9 0x00007f23077fe9f4 in xine_log () from /usr/lib/libxine.so.1 #10 0x00007f2307809ecc in ?? () from /usr/lib/libxine.so.1 #11 0x00007f22ff1fafc2 in ?? () from /usr/lib/kde4/phonon_xine.so #12 0x00007f22ff1fe5dc in KPluginFactory::createInstance<Phonon::Xine::Backend, QObject> () from /usr/lib/kde4/phonon_xine.so #13 0x00007f2309309695 in KPluginFactory::create () from /usr/lib/libkdecore.so.5 #14 0x00007f22ffa595b9 in ?? () from /usr/lib/kde4/plugins/phonon_platform/kde.so #15 0x00007f22ffa5af0d in ?? () from /usr/lib/kde4/plugins/phonon_platform/kde.so #16 0x00007f2308f0a4c8 in ?? () from /usr/lib/libphonon.so.4 #17 0x00007f2308f0b407 in Phonon::Factory::backend () from /usr/lib/libphonon.so.4 #18 0x00007f2308f0b710 in ?? () from /usr/lib/libphonon.so.4 #19 0x00007f2308f10326 in ?? () from /usr/lib/libphonon.so.4 #20 0x00007f2308f0ffcb in Phonon::VideoWidget::VideoWidget () from /usr/lib/libphonon.so.4 #21 0x00000000004184b1 in VideoWindow (this=0x24377c0, parent=<value optimized out>) at /build/buildd/kdemultimedia-4.1.2/dragonplayer/src/app/videoWindow.cpp:90 #22 0x0000000000430a83 in MainWindow (this=0x243ae10) at /build/buildd/kdemultimedia-4.1.2/dragonplayer/src/app/mainWindow.cpp:102 #23 0x000000000042b4bf in main (argc=1, argv=<value optimized out>) at /build/buildd/kdemultimedia-4.1.2/dragonplayer/src/app/main.cpp:56 #0 0x00007f2307218621 in nanosleep () from /lib/libc.so.6
Can you still reproduce this problem? If yes, are you using translations? Can you try to switch to the C-locale?
Assuming german translations... *** This bug has been marked as a duplicate of bug 175407 ***