Version: 2.2 (using KDE 4.2.0) OS: Linux Installed from: Unlisted Binary Package After I have started my new-version konsole for the first time, it didn't display the command line (just the menu headers) and crashed when I closed it. Here is the trace: Application: Konsole (konsole), signal SIGABRT Thread 1 (Thread 0xb5ff06c0 (LWP 3456)): [KCrash Handler] #6 0xb7f9c424 in __kernel_vsyscall () #7 0xb7d73640 in raise () from /lib/i686/cmov/libc.so.6 #8 0xb7d75018 in abort () from /lib/i686/cmov/libc.so.6 #9 0xb718e6cd in qt_message_output (msgType=QtFatalMsg, buf=0xbfbb56a0 "ASSERT: \"container\" in file ../../../../apps/konsole/src/ViewManager.cpp, line 858") at global/qglobal.cpp:2102 #10 0xb718e796 in qFatal (msg=0xb72d6438 "ASSERT: \"%s\" in file %s, line %d") at global/qglobal.cpp:2303 #11 0xb718e825 in qt_assert (assertion=0xb7f74130 "container", file=0xb7f73d0c "../../../../apps/konsole/src/ViewManager.cpp", line=858) at global/qglobal.cpp:1872 #12 0xb7f50775 in Konsole::ViewManager::viewProperties (this=0xa0f2018) at ../../../../apps/konsole/src/ViewManager.cpp:858 #13 0xb7f653ad in Konsole::MainWindow::queryClose (this=0xa044050) at ../../../../apps/konsole/src/MainWindow.cpp:344 #14 0xb78dab40 in KMainWindow::closeEvent (this=0xa044050, e=0xbfbb7d24) at ../../kdeui/widgets/kmainwindow.cpp:587 #15 0xb69d31e3 in QWidget::event (this=0xa044050, event=0xbfbb7d24) at kernel/qwidget.cpp:7313 #16 0xb6d231c7 in QMainWindow::event (this=0xa044050, event=0xbfbb7d24) at widgets/qmainwindow.cpp:1268 #17 0xb78d97f7 in KMainWindow::event (this=0xa044050, ev=0xbfbb7d24) at ../../kdeui/widgets/kmainwindow.cpp:1093 #18 0xb791edcc in KXmlGuiWindow::event (this=0xa044050, ev=0xbfbb7d24) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:131 #19 0xb697b79c in QApplicationPrivate::notify_helper (this=0x9fe31d0, receiver=0xa044050, e=0xbfbb7d24) at kernel/qapplication.cpp:3803 #20 0xb69836ea in QApplication::notify (this=0xbfbb8494, receiver=0xa044050, e=0xbfbb7d24) at kernel/qapplication.cpp:3768 #21 0xb77f078d in KApplication::notify (this=0xbfbb8494, receiver=0xa044050, event=0xbfbb7d24) at ../../kdeui/kernel/kapplication.cpp:307 #22 0xb72860d1 in QCoreApplication::notifyInternal (this=0xbfbb8494, receiver=0xa044050, event=0xbfbb7d24) at kernel/qcoreapplication.cpp:587 #23 0xb69d6313 in QWidgetPrivate::close_helper (this=0xa044238, mode=QWidgetPrivate::CloseWithSpontaneousEvent) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:212 #24 0xb69db46b in QApplication::x11ClientMessage (this=0xbfbb8494, w=0xa044050, event=0xbfbb81ac, passive_only=6) at kernel/qapplication_x11.cpp:4808 #25 0xb69eb5c1 in QApplication::x11ProcessEvent (this=0xbfbb8494, event=0xbfbb81ac) at kernel/qapplication_x11.cpp:3291 #26 0xb6a1560a in x11EventSourceDispatch (s=0x9fdfe98, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:142 #27 0xb63551b8 in IA__g_main_context_dispatch (context=0x9fe6078) at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c:2012 #28 0xb6358853 in g_main_context_iterate (context=0x9fe6078, block=1, dispatch=1, self=0x9fe43c0) at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c:2645 #29 0xb6358a11 in IA__g_main_context_iteration (context=0x9fe6078, may_block=1) at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c:2708 #30 0xb72b05d8 in QEventDispatcherGlib::processEvents (this=0x9fe3e88, flags={i = -1078230168}) at kernel/qeventdispatcher_glib.cpp:319 #31 0xb6a14d45 in QGuiEventDispatcherGlib::processEvents (this=0x9fe3e88, flags={i = -1078230120}) at kernel/qguieventdispatcher_glib.cpp:198 #32 0xb728479a in QEventLoop::processEvents (this=0xbfbb8410, flags={i = -1078230056}) at kernel/qeventloop.cpp:143 #33 0xb728495a in QEventLoop::exec (this=0xbfbb8410, flags={i = -1078229992}) at kernel/qeventloop.cpp:194 #34 0xb7287015 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #35 0xb697b617 in QApplication::exec () at kernel/qapplication.cpp:3331 #36 0xb7f678d2 in kdemain (argc=3, argv=0xbfbb85c4) at ../../../../apps/konsole/src/main.cpp:104 #37 0x08048592 in main (argc=) at konsole_dummy.cpp:3 All subsequent konsole runs were ok.
*** This bug has been marked as a duplicate of bug 175758 ***