Bug 171060 - konsole crashed while connected to several terminals
Summary: konsole crashed while connected to several terminals
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2008-09-14 17:32 UTC by James
Modified: 2018-10-21 04:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James 2008-09-14 17:32:01 UTC
Version:           2.1 (using KDE 4.1.1)
Compiler:          gcc 4.2.4
OS:                Linux
Installed from:    Ubuntu Packages

I was using konsole. I then switched back to konqueror to lookup some information. While looking at the web page the konsole application crashed. 

Application: Konsole (konsole), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb615a940 (LWP 6354)]
[New Thread 0xb4ac5b90 (LWP 6355)]
[KCrash handler]
#6  0xb7fc7410 in __kernel_vsyscall ()
#7  0xb7dbe085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb7dbfa01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7483367 in qt_message_output (msgType=QtFatalMsg, 
    buf=0xbf81248c "ASSERT: \"columns > 0\" in file /build/buildd/kdebase-kde4-4.1.1/apps/konsole/src/Emulation.cpp, line 432") at global/qglobal.cpp:2061
#10 0xb7483458 in qFatal (msg=0xb75ca498 "ASSERT: \"%s\" in file %s, line %d")
    at global/qglobal.cpp:2263
#11 0xb7483505 in qt_assert (assertion=0xb7fb5522 "columns > 0", 
    file=0xb7fb119c "/build/buildd/kdebase-kde4-4.1.1/apps/konsole/src/Emulation.cpp", line=432) at global/qglobal.cpp:1831
#12 0xb7f3f720 in ?? () from /usr/lib/kde4/lib/libkdeinit4_konsole.so
#13 0xb7fa4a55 in ?? () from /usr/lib/kde4/lib/libkdeinit4_konsole.so
#14 0xb7fa5488 in ?? () from /usr/lib/kde4/lib/libkdeinit4_konsole.so
#15 0xb7f3f8c7 in ?? () from /usr/lib/kde4/lib/libkdeinit4_konsole.so
#16 0xb7f6dc49 in Konsole::Session::onReceiveBlock ()
   from /usr/lib/kde4/lib/libkdeinit4_konsole.so
#17 0xb7f706b3 in Konsole::Session::qt_metacall ()
   from /usr/lib/kde4/lib/libkdeinit4_konsole.so
#18 0xb758bf79 in QMetaObject::activate (sender=0x81a7000, 
    from_signal_index=25, to_signal_index=25, argv=0xbf8146f8)
    at kernel/qobject.cpp:3016
#19 0xb758c642 in QMetaObject::activate (sender=0x81a7000, m=0xb7fbe558, 
    local_signal_index=0, argv=0xbf8146f8) at kernel/qobject.cpp:3086
#20 0xb7f64ae9 in Konsole::Pty::receivedData ()
   from /usr/lib/kde4/lib/libkdeinit4_konsole.so
#21 0xb7f64c9c in Konsole::Pty::dataReceived ()
   from /usr/lib/kde4/lib/libkdeinit4_konsole.so
#22 0xb7f654c2 in Konsole::Pty::qt_metacall ()
   from /usr/lib/kde4/lib/libkdeinit4_konsole.so
#23 0xb758bf79 in QMetaObject::activate (sender=0x828f9f0, 
    from_signal_index=8, to_signal_index=8, argv=0x0)
    at kernel/qobject.cpp:3016
#24 0xb758c642 in QMetaObject::activate (sender=0x828f9f0, m=0xb7d911c0, 
    local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3086
#25 0xb7d8d297 in KPtyDevice::readyRead (this=0x828f9f0)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/obj-i486-linux-gnu/kpty/kptydevice.moc:88
#26 0xb7d8de60 in KPtyDevicePrivate::_k_canRead (this=0x828fcb0)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kpty/kptydevice.cpp:285
#27 0xb7d8def7 in KPtyDevice::qt_metacall (this=0x828f9f0, 
    _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf81495c)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/obj-i486-linux-gnu/kpty/kptydevice.moc:75
#28 0xb758bf79 in QMetaObject::activate (sender=0x828fc60, 
    from_signal_index=4, to_signal_index=4, argv=0xbf81495c)
    at kernel/qobject.cpp:3016
#29 0xb758c642 in QMetaObject::activate (sender=0x828fc60, m=0xb766ba90, 
    local_signal_index=0, argv=0xbf81495c) at kernel/qobject.cpp:3086
#30 0xb75c96b3 in QSocketNotifier::activated (this=0x828fc60, _t1=16)
    at .moc/release-shared/moc_qsocketnotifier.cpp:81
#31 0xb759260f in QSocketNotifier::event (this=0x828fc60, e=0xbf814d90)
    at kernel/qsocketnotifier.cpp:326
#32 0xb6acdf9c in QApplicationPrivate::notify_helper (this=0x8062ba8, 
    receiver=0x828fc60, e=0xbf814d90) at kernel/qapplication.cpp:3800
#33 0xb6ad2bf9 in QApplication::notify (this=0xbf815018, receiver=0x828fc60, 
    e=0xbf814d90) at kernel/qapplication.cpp:3392
#34 0xb79f41c3 in KApplication::notify (this=0xbf815018, receiver=0x828fc60, 
    event=0xbf814d90)
    at /build/buildd/kde4libs-4.1.1+really4.1.1/kdeui/kernel/kapplication.cpp:311
#35 0xb75770b9 in QCoreApplication::notifyInternal (this=0xbf815018, 
    receiver=0x828fc60, event=0xbf814d90) at kernel/qcoreapplication.cpp:591
#36 0xb75a2883 in socketNotifierSourceDispatch (source=0x806c108)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#37 0xb650add6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#38 0xb650e193 in ?? () from /usr/lib/libglib-2.0.so.0
#39 0xb650e74e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#40 0xb75a29f8 in QEventDispatcherGlib::processEvents (this=0x8062cb8, 
    flags=@0xbf814ed8) at kernel/qeventdispatcher_glib.cpp:325
#41 0xb6b61a25 in QGuiEventDispatcherGlib::processEvents (this=0x8062cb8, 
    flags=@0xbf814f08) at kernel/qguieventdispatcher_glib.cpp:204
#42 0xb757633d in QEventLoop::processEvents (this=0xbf814f80, 
    flags=@0xbf814f44) at kernel/qeventloop.cpp:149
#43 0xb75764cd in QEventLoop::exec (this=0xbf814f80, flags=@0xbf814f88)
    at kernel/qeventloop.cpp:200
#44 0xb757874d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:849
#45 0xb6acd897 in QApplication::exec () at kernel/qapplication.cpp:3330
#46 0xb7fad5c3 in kdemain () from /usr/lib/kde4/lib/libkdeinit4_konsole.so
#47 0x08048582 in _start ()
#0  0xb7fc7410 in __kernel_vsyscall ()
Comment 1 Dario Andres 2008-12-05 17:45:37 UTC
This may be related/duplicate of bug 172842
Comment 2 Dario Andres 2009-01-18 00:27:10 UTC
Have you experienced this bug again using a recent KDE (4.1.4 / 4.2beta2 / 4.2rc1 / 4.2svn / 4.3svn) ? Thanks :)
Comment 3 Dario Andres 2009-08-02 20:53:48 UTC
Marking as NEEDSINFO
Comment 4 Andrew Crouthamel 2018-09-20 03:15:55 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-21 04:43:00 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!