Bug 333607

Summary:	kde konsole crash when executing close command
Product:	[Applications] konsole	Reporter:	david davis <java007md>
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	386230606, ben, crucerucalincristian, qwerty0129, volkangezer
Priority:	NOR	Keywords:	drkonqi, triaged
Version:	2.13
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi

Description david davis 2014-04-19 04:13:11 UTC

Application: konsole (2.13)
KDE Platform Version: 4.13.0
Qt Version: 4.8.6
Operating System: Linux 3.13.0-24-generic x86_64
Distribution: Ubuntu 14.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
- typed 'exit' and hit return
- repeatable problem
- execution of other commands not required prior to the crash occurring

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe3104ed7c0 (LWP 20570))]

Thread 2 (Thread 0x7fe2fa21b700 (LWP 20571)):
#0  0x00007fe30fe22fbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fe309197fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe3091980ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe30e5317be in QEventDispatcherGlib::processEvents (this=0x7fe2f40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x00007fe30e5030af in QEventLoop::processEvents (this=this@entry=0x7fe2fa21ade0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fe30e5033a5 in QEventLoop::exec (this=this@entry=0x7fe2fa21ade0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fe30e3ffc5f in QThread::exec (this=this@entry=0x26ba520) at thread/qthread.cpp:537
#7  0x00007fe30e4e4823 in QInotifyFileSystemWatcherEngine::run (this=0x26ba520) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007fe30e40232f in QThreadPrivate::start (arg=0x26ba520) at thread/qthread_unix.cpp:349
#9  0x00007fe309a7e182 in start_thread (arg=0x7fe2fa21b700) at pthread_create.c:312
#10 0x00007fe30fe3030d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fe3104ed7c0 (LWP 20570)):
[KCrash Handler]
#6  0x000000000238b960 in ?? ()
#7  0x00007fe30d917090 in QApplication::x11ProcessEvent (this=0x7fffb22827a0, event=event@entry=0x7fffb22822a0) at kernel/qapplication_x11.cpp:3529
#8  0x00007fe30d93fb02 in x11EventSourceDispatch (s=0x2244400, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#9  0x00007fe309197e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007fe309198048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007fe3091980ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007fe30e5317a1 in QEventDispatcherGlib::processEvents (this=0x2189af0, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#13 0x00007fe30d93fbb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#14 0x00007fe30e5030af in QEventLoop::processEvents (this=this@entry=0x7fffb2282670, flags=...) at kernel/qeventloop.cpp:149
#15 0x00007fe30e5033a5 in QEventLoop::exec (this=this@entry=0x7fffb2282670, flags=...) at kernel/qeventloop.cpp:204
#16 0x00007fe30e508b79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#17 0x00007fe30d89c37c in QApplication::exec () at kernel/qapplication.cpp:3828
#18 0x00007fe3101136f7 in kdemain (argc=1, argv=0x7fffb22828e8) at ../../src/main.cpp:86
#19 0x00007fe30fd56ec5 in __libc_start_main (main=0x4006d0 <main(int, char**)>, argc=1, argv=0x7fffb22828e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffb22828d8) at libc-start.c:287
#20 0x00000000004006fe in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 332729.

Possible duplicates by query: bug 333521, bug 332729, bug 332662, bug 332095, bug 332023.

Reported using DrKonqi

Comment 1 Volkan 2014-04-19 10:37:04 UTC

Created attachment 86167 [details]
New crash information added by DrKonqi

konsole (2.13) on KDE Platform 4.13.0 using Qt 4.8.6

- What I was doing when the application crashed:

Executed exit on console while multiple tabs are open.

-- Backtrace (Reduced):
#7  0x00007f4ba855b090 in QApplication::x11ProcessEvent (this=0x7fff473eab50, event=event@entry=0x7fff473ea650) at kernel/qapplication_x11.cpp:3529
#8  0x00007f4ba8583b02 in x11EventSourceDispatch (s=0x19a3df0, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
[...]
#12 0x00007f4ba91757a1 in QEventDispatcherGlib::processEvents (this=0x18e4af0, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#13 0x00007f4ba8583bb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#14 0x00007f4ba91470af in QEventLoop::processEvents (this=this@entry=0x7fff473eaa20, flags=...) at kernel/qeventloop.cpp:149

Comment 2 Yu 2014-04-30 03:02:01 UTC

Created attachment 86359 [details]
New crash information added by DrKonqi

konsole (2.13) on KDE Platform 4.13.0 using Qt 4.8.6

- What I was doing when the application crashed:

I was running several konsoles at that time. But after I typed commond 'exit' to close one of the konsoles, the konsole crashed and all of the console windows were gone. The koncole can be restarted correctly.
The crash has happened many times.

-- Backtrace (Reduced):
#7  0x00007f9ce1789090 in QApplication::x11ProcessEvent (this=0x7fffdbda86a0, event=event@entry=0x7fffdbda81a0) at kernel/qapplication_x11.cpp:3529
#8  0x00007f9ce17b1b02 in x11EventSourceDispatch (s=0xc19670, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
[...]
#12 0x00007f9ce23a37a1 in QEventDispatcherGlib::processEvents (this=0xb60b00, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#13 0x00007f9ce17b1bb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#14 0x00007f9ce23750af in QEventLoop::processEvents (this=this@entry=0x7fffdbda8570, flags=...) at kernel/qeventloop.cpp:149

Comment 3 Cruceru Calin-Cristian 2014-06-18 11:50:59 UTC

Created attachment 87255 [details]
New crash information added by DrKonqi

konsole (2.13) on KDE Platform 4.13.0 using Qt 4.8.6

- What I was doing when the application crashed:
Tried to close one tab in terminal using Ctrl+D.

- What should have happened:
That tab should have been closed.

-- Backtrace (Reduced):
#7  0x00007f528872b090 in QApplication::x11ProcessEvent (this=0x7fffec537200, event=event@entry=0x7fffec536d00) at kernel/qapplication_x11.cpp:3529
#8  0x00007f5288753b02 in x11EventSourceDispatch (s=0x951c00, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
[...]
#12 0x00007f52893457a1 in QEventDispatcherGlib::processEvents (this=0x950890, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#13 0x00007f5288753bb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#14 0x00007f52893170af in QEventLoop::processEvents (this=this@entry=0x7fffec5370d0, flags=...) at kernel/qeventloop.cpp:149

Comment 4 Jacob Phillips 2014-06-18 20:30:04 UTC

Created attachment 87265 [details]
New crash information added by DrKonqi

konsole (2.13.1) on KDE Platform 4.13.1 using Qt 4.8.6

- What I was doing when the application crashed:

1.   Opened 7-10 new tabs in konsole.
2.   Typed exit in each shell tab until it crashed.

Does not always crash when closing a tab, as in my case it took 4-5 exits before this one crashed.

Also happens with Yakuake spawned tabs and split-screen sessions.

-- Backtrace (Reduced):
#7  0x00007f41df1d2090 in QApplication::x11ProcessEvent (this=0x7fff354565f0, event=event@entry=0x7fff354560f0) at kernel/qapplication_x11.cpp:3529
#8  0x00007f41df1fab02 in x11EventSourceDispatch (s=0x1408800, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
[...]
#12 0x00007f41dfdec7a1 in QEventDispatcherGlib::processEvents (this=0x134caf0, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#13 0x00007f41df1fabb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#14 0x00007f41dfdbe0af in QEventLoop::processEvents (this=this@entry=0x7fff354564c0, flags=...) at kernel/qeventloop.cpp:149

Comment 5 Ben Creasy 2018-08-19 04:22:56 UTC

Over 4 years - is this still happening for you xavier? Putting it into WAITINGFORINFO. Feel free to reopen if still happening.

Comment 6 Andrew Crouthamel 2018-09-28 03:07:36 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 7 Andrew Crouthamel 2018-10-28 03:35:23 UTC

Dear Bug Submitter,

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!