Bug 215701 - konsole weird screen crash when closed
Summary: konsole weird screen crash when closed
Status: RESOLVED DUPLICATE of bug 203621
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-22 17:19 UTC by Morinehtar0
Modified: 2009-11-23 15:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Morinehtar0 2009-11-22 17:19:00 UTC
Application that crashed: konsole
Version of the application: 2.3.1
KDE Version: 4.3.1 (KDE 4.3.1) "release 6"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.5-0.1-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

What I was doing when the application crashed:
After session restore, one of two konsoles started with completely grey text-area. when closing this one both konsoles disappeared with this crash report.
The misbehaving konsole may have been a root-konsole; not sure...

 -- Backtrace:
Application: Konsole (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  QList (l=<value optimized out>, this=<value optimized out>) at /usr/include/QtCore/qlist.h:111
#6  Konsole::ViewContainer::views (l=<value optimized out>, this=<value optimized out>) at /usr/src/debug/kdebase-4.3.1/apps/konsole/src/ViewContainer.cpp:191
#7  0x00007f0d21570e89 in Konsole::ViewManager::viewProperties (this=<value optimized out>) at /usr/src/debug/kdebase-4.3.1/apps/konsole/src/ViewManager.cpp:886
#8  0x00007f0d217d3cb1 in Konsole::MainWindow::queryClose (this=0x73db20) at /usr/src/debug/kdebase-4.3.1/apps/konsole/src/MainWindow.cpp:341
#9  0x00007f0d2bca9281 in KMainWindow::closeEvent(QCloseEvent*) () from /usr/lib64/libkdeui.so.5
#10 0x00007f0d2b02c678 in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#11 0x00007f0d2b3860bb in QMainWindow::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#12 0x00007f0d2bce3d83 in KXmlGuiWindow::event(QEvent*) () from /usr/lib64/libkdeui.so.5
#13 0x00007f0d2afde2ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#14 0x00007f0d2afe557e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007f0d2bbd88d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#16 0x00007f0d2d1edddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#17 0x00007f0d2b031a51 in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from /usr/lib64/libQtGui.so.4
#18 0x00007f0d2b038ee6 in QApplication::x11ClientMessage(QWidget*, _XEvent*, bool) () from /usr/lib64/libQtGui.so.4
#19 0x00007f0d2b049864 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x00007f0d2b071b6c in ?? () from /usr/lib64/libQtGui.so.4
#21 0x00007f0d29f27dde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f0d29f2b7a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f0d29f2b8d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f0d2d2163a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007f0d2b07131e in ?? () from /usr/lib64/libQtGui.so.4
#26 0x00007f0d2d1ec712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007f0d2d1ecae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f0d2d1eec99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#29 0x00007f0d217d6263 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-4.3.1/apps/konsole/src/main.cpp:104
#30 0x0000000000406f88 in _start ()

This bug may be a duplicate of or related to bug 205972

Reported using DrKonqi
Comment 1 Dario Andres 2009-11-23 15:02:51 UTC
This is being tracked at bug 203621 Thanks

*** This bug has been marked as a duplicate of bug 203621 ***