Bug 96395 - after exit krusader-editor (root-mode) (ESC) - krusader crash
Summary: after exit krusader-editor (root-mode) (ESC) - krusader crash
Status: RESOLVED FIXED
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Shie Erlich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-05 21:18 UTC by Jorj_K
Modified: 2009-01-02 23:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Debug Traceback on my machine (4.19 KB, text/plain)
2005-05-20 14:59 UTC, Benjamin Otto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jorj_K 2005-01-05 21:18:04 UTC
Version:           1.5.1 (using KDE KDE 3.3.2)
Installed from:    RedHat RPMs
OS:                Linux

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -151128384 (LWP 15085)]
[KCrash handler]
#4  0x025ea47a in QMetaObject::inherits ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#5  0x025f5b0f in QObject::inherits () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#6  0x02c6e41a in KXMLGUIBuilder::removeContainer ()
   from /usr/lib/libkdeui.so.4
#7  0x02c6b13f in KXMLGUI::ContainerNode::destruct ()
   from /usr/lib/libkdeui.so.4
#8  0x02c6b209 in KXMLGUI::ContainerNode::destructChildren ()
   from /usr/lib/libkdeui.so.4
#9  0x02c6affe in KXMLGUI::ContainerNode::destruct ()
   from /usr/lib/libkdeui.so.4
#10 0x02c6b209 in KXMLGUI::ContainerNode::destructChildren ()
   from /usr/lib/libkdeui.so.4
#11 0x02c6affe in KXMLGUI::ContainerNode::destruct ()
   from /usr/lib/libkdeui.so.4
#12 0x02c65710 in KXMLGUIFactory::removeClient () from /usr/lib/libkdeui.so.4
#13 0xf6ac4964 in KateDocument::disablePluginGUI ()
   from /usr/lib/kde3/libkatepart.so
#14 0xf6ac4a1d in KateDocument::disablePluginGUI ()
   from /usr/lib/kde3/libkatepart.so
#15 0xf6ac4a84 in KateDocument::unloadPlugin ()
   from /usr/lib/kde3/libkatepart.so
#16 0xf6ac9cd8 in KateDocument::unloadAllPlugins ()
   from /usr/lib/kde3/libkatepart.so
#17 0xf6acb68b in KateDocument::~KateDocument ()
   from /usr/lib/kde3/libkatepart.so
#18 0x0262de40 in QWidget::~QWidget () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x026eb217 in QMainWindow::~QMainWindow ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x02befbd9 in KMainWindow::~KMainWindow () from /usr/lib/libkdeui.so.4
#21 0x00bf7f3d in KParts::MainWindow::~MainWindow ()
   from /usr/lib/libkparts.so.2
#22 0x080db3f8 in KrViewer::~KrViewer ()
#23 0x025f6a49 in QObject::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#24 0x0262ed8a in QWidget::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x026e7c5c in QMainWindow::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x0259a849 in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#27 0x0259a9da in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x001b94e8 in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0x0259b9a6 in QApplication::sendPostedEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#30 0x0259ba32 in QApplication::sendPostedEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#31 0x0254a6a8 in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#32 0x025afe75 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#33 0x025afdce in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#34 0x02599a4b in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#35 0x0807ed12 in main ()
Comment 1 Benjamin Otto 2005-05-20 14:59:18 UTC
Created attachment 11114 [details]
Debug Traceback on my machine

Here is the output of the traceback function on my machine. I have a Debian
Sarge installation with Krusader 1.51 and everytime i close an editor, which
has been openend using "F4" through krusader, krusader crashes. This is very
annoying. It would be great if that gets fixed. Thanks.
Comment 2 Benjamin Otto 2005-05-20 15:05:11 UTC
Sorry, i just saw the Changelog, and the fix seems to be applied already, this bug can therefore be closed.
Comment 3 Nicolas L. 2009-01-02 23:46:21 UTC
closing as told by comment 2