Created attachment 47743 [details] A simple sample html file that can induce a crash Version: unspecified OS: Linux Using Krusader version 2.0.0 and KDE 4.4.4 (there are no options for these versions yet in the relevant drop-down menus so I couldn't specify it there) Krusader crashes with Signal 11: Segmentation Fault when closing with ALT+F4 or CTRL+Q an HTML file opened from the hard drive in KrViewer. For this crash to happen, is necessary and sufficient that the html file contains a <head> tag - therefore it happens with almost all html files. Interestingly, it does NOT crash if: - Doesn't crash if the html file is closed by pressing ESC, or clicking the X button with the mouse to close the window, or by clicking "Quit" with the mouse from the KrViewer menu. - I have only seen the crash with html files, i.e. it does not crash when closing with ALT+F4 or CTRL+Q a KrViewer window that has a .txt file open for example. - It doesn't crash when closing an html file that doesn't have a <head> tag. Reproducible: Always Steps to Reproduce: 1. Create an .html file containing a <head> element. A file containing only a single <head> element is sufficient to make it crash. Alternatively, download any html file from the internet, e.g.: http://en.wikipedia.org/ 2. Open it in KrViewer (by pressing F3 in Krusader) 3. Press either ALT+F4 or CTRL+Q attempting to close the KrViewer window Actual Results: Krusader crashes with Signal: 11 (Segmentation fault) Expected Results: Close the KrViewer window and return to Krusader Application: Krusader (krusader), signal: Segmentation fault [KCrash Handler] #5 0x00007fa1e3ac82ac in QWidget::window() const () from /usr/lib/libQtGui.so.4 #6 0x00007fa1e3a89b92 in QApplicationPrivate::dispatchEnterLeave(QWidget*, QWidget*) () from /usr/lib/libQtGui.so.4 #7 0x00007fa1e3b02ff1 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4 #8 0x00007fa1e3b287f2 in ?? () from /usr/lib/libQtGui.so.4 #9 0x00007fa1deb3eb33 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #10 0x00007fa1deb3f310 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #11 0x00007fa1deb3f5ad in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #12 0x00007fa1e30ad00f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #13 0x00007fa1e3b284be in ?? () from /usr/lib/libQtGui.so.4 #14 0x00007fa1e3083b82 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #15 0x00007fa1e3083dbc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #16 0x00007fa1e30880eb in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #17 0x000000000045bbde in _start ()
Is it reproducible in > 2.3. beta1 and a recent kde version ?
*** This bug has been marked as a duplicate of bug 198996 ***