Version: 3.5.5 (using KDE 3.5.5 "release 50.1" , openSUSE ) Compiler: Target: i586-suse-linux OS: Linux (i686) release 2.6.18.2-34-default Lonqueror crashes if and only if an .ogg file has accidentially been opened from the ark plugin with konqueror instead of a music player like amarok. The konqueror subwindow at first says that it does not know how to show the content. The crash appears when closing/quitting the konqueror base window running the ark plugin. build: kdebase3-3.5.5-138.1 Überprüfung der Systemkonfiguration beim Start deaktiviert. Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1230580048 (LWP 6664)] [KCrash handler] #9 0xb71e9400 in pthread_mutex_lock () from /lib/libpthread.so.0 #10 0xb72471ff in XInitThreads () from /usr/X11R6/lib/libX11.so.6 #11 0xb722ffcf in XrmDestroyDatabase () from /usr/X11R6/lib/libX11.so.6 #12 0xb721bb7c in _XFreeDisplayStructure () from /usr/X11R6/lib/libX11.so.6 #13 0xb720a51a in XCloseDisplay () from /usr/X11R6/lib/libX11.so.6 #14 0xb74bd428 in qt_cleanup () from /usr/lib/qt3/lib/libqt-mt.so.3 #15 0xb752ff04 in QApplication::~QApplication () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0xb7b413a9 in KApplication::~KApplication () from /opt/kde3/lib/libkdecore.so.4 #17 0xb68355d5 in kdemain () from /opt/kde3/lib/libkdeinit_konqueror.so #18 0xb7305534 in kdeinitmain () from /opt/kde3/lib/kde3/konqueror.so #19 0x0804e2ff in launch () #20 0x0804eb8a in handle_launcher_request () #21 0x0804ef0f in handle_requests () #22 0x0805010c in main ()
Created attachment 19282 [details] valgrind backtrace without crash No Crash appears if .ogg file cotained in the ark archive is directly opened with an appropriate application like Amarok.
Created attachment 19283 [details] valgrind backtrace with crash Trying to open the .ogg file directly konqueror does not know how to open it (message box). A crash appears due to some memory corruption not before the konqueror instance with the ark plugin for browsing has been closed.
*** This bug has been marked as a duplicate of 114198 ***