Bug 310509

Summary:	konsole crash after closing one of the tabs by Ctrl-Shift-W
Product:	[Applications] konsole	Reporter:	Shuai YUAN <yszheda>
Component:	general	Assignee:	Konsole Bugs <konsole-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version First Reported In:	2.9.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Shuai YUAN 2012-11-22 14:58:35 UTC

Application: konsole (2.9.1)
KDE Platform Version: 4.9.1
Qt Version: 4.8.3
Operating System: Linux 3.5.4-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
1.start konsole
2.create multiple tabs. (Usually I use ssh in some tabs, I am not sure whether it's related to this bug issue.)
3.use hotkey Ctrl-Shift-W to close one of the tabs. 
Normally the current tab should be closed, meanwhile other tabs should still remain. But konsole crash with all the tabs closed. The crash can be reproduced every time.

The crash can be reproduced every time.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc616e65780 (LWP 5146))]

Thread 2 (Thread 0x7fc601817700 (LWP 5147)):
#0  0x00007fc6103c5855 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#1  0x00007fc615367766 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#2  0x00007fc61533833f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#3  0x00007fc6153385c8 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#4  0x00007fc6152397c0 in QThread::exec() () from /usr/lib/libQtCore.so.4
#5  0x00007fc615318aff in ?? () from /usr/lib/libQtCore.so.4
#6  0x00007fc61523c79c in ?? () from /usr/lib/libQtCore.so.4
#7  0x00007fc614face0f in start_thread () from /usr/lib/libpthread.so.0
#8  0x00007fc6167b845d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fc616e65780 (LWP 5146)):
[KCrash Handler]
#5  0x0000000000000000 in ?? ()
#6  0x00007fc614546ed0 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4
#7  0x00007fc61456d892 in ?? () from /usr/lib/libQtGui.so.4
#8  0x00007fc6103c5475 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#9  0x00007fc6103c57a8 in ?? () from /usr/lib/libglib-2.0.so.0
#10 0x00007fc6103c5864 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#11 0x00007fc615367746 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#12 0x00007fc61456d50e in ?? () from /usr/lib/libQtGui.so.4
#13 0x00007fc61533833f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#14 0x00007fc6153385c8 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#15 0x00007fc61533d268 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#16 0x00007fc616a8feb7 in kdemain () from /usr/lib/libkdeinit4_konsole.so
#17 0x00007fc6166f3725 in __libc_start_main () from /usr/lib/libc.so.6
#18 0x0000000000400721 in _start ()

Possible duplicates by query: bug 309954, bug 309663, bug 309351, bug 309216, bug 308787.

Reported using DrKonqi

Comment 1 Jekyll Wu 2012-12-02 01:38:48 UTC

Are you using input methods? If yes, which one (fcitx/ibus/scim) ?

Comment 2 Shuai YUAN 2012-12-02 12:29:39 UTC

(In reply to comment #1)
> Are you using input methods? If yes, which one (fcitx/ibus/scim) ?
Yes, I use ibus.

Comment 3 Jekyll Wu 2012-12-02 17:32:03 UTC

Thanks. Then it is another symptom of one known problem: bug 252602 .

The unfortunate fact is although it is a known problem, it is hard to infer and find where the cause is. I made some investigation some time ago but still have no clear clue so far.

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

Comment 4 Shuai YUAN 2012-12-02 18:00:24 UTC

(In reply to comment #3)
> Thanks. Then it is another symptom of one known problem: bug 252602 .
> 
> The unfortunate fact is although it is a known problem, it is hard to infer
> and find where the cause is. I made some investigation some time ago but
> still have no clear clue so far.
> 
> *** This bug has been marked as a duplicate of bug 252602 ***
Thank you, Jekyll.
I did not recognize that the crash is related to ibus. I tried again without running ibus and found that this bug could not be reproduced, just like your description (comment #9) in bug 252602.