Application: konsole (2.8.3) KDE Platform Version: 4.8.3 (4.8.3) (Compiled from sources) Qt Version: 4.8.1 Operating System: Linux 3.3.4-gentoo-ck1 x86_64 Distribution: "Gentoo Base System release 2.1" -- Information about the crash: Konsole crashes randomly and all my konsole windows (not tabs) are gone. The crash can be reproduced some of the time. -- Backtrace: Application: Konsole (kdeinit4), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 q_func (this=0x0) at ../../include/QtGui/private/../../../src/gui/kernel/qwidget_p.h:362 #7 QWidgetPrivate::assignedInputContext (this=0x0) at kernel/qwidget.cpp:422 #8 0x00007f781049dc79 in QWidgetPrivate::inputContext (this=<optimized out>) at kernel/qwidget.cpp:435 #9 0x00007f78104fd79a in QKeyMapperPrivate::translateKeyEvent (this=0x1a974c0, keyWidget=0x26b9770, event=0x7fff5a50b0c0, grab=false) at kernel/qkeymapper_x11.cpp:1724 #10 0x00007f78104da034 in QApplication::x11ProcessEvent (this=0x7fff5a50b4c0, event=0x7fff5a50b0c0) at kernel/qapplication_x11.cpp:3518 #11 0x00007f7810501792 in x11EventSourceDispatch (s=0x1a50370, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #12 0x00007f780cba9593 in g_main_dispatch (context=0x1a50140) at gmain.c:2539 #13 g_main_context_dispatch (context=0x1a50140) at gmain.c:3075 #14 0x00007f780cba98e0 in g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x1a50140, self=<optimized out>) at gmain.c:3146 #15 g_main_context_iterate (context=0x1a50140, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3083 #16 0x00007f780cba99a4 in g_main_context_iteration (context=0x1a50140, may_block=1) at gmain.c:3207 #17 0x00007f78112f357f in QEventDispatcherGlib::processEvents (this=0x1a4d160, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #18 0x00007f781050142e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #19 0x00007f78112c3d92 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #20 0x00007f78112c3fe7 in QEventLoop::exec (this=0x7fff5a50b450, flags=...) at kernel/qeventloop.cpp:204 #21 0x00007f78112c8a65 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #22 0x00007f78012e9062 in kdemain (argc=1, argv=0x19dc340) at /var/tmp/portage/kde-base/konsole-4.8.3/work/konsole-4.8.3/src/main.cpp:88 #23 0x0000000000408a84 in launch (argc=1, _name=0x19edd88 "/usr/bin/konsole", args=<optimized out>, cwd=0x0, envc=<optimized out>, envs=<optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x19eddb4 "ThinkGemini;1336607149;269506;2185_TIME18689348") at /var/tmp/portage/kde-base/kdelibs-4.8.3/work/kdelibs-4.8.3/kinit/kinit.cpp:734 #24 0x0000000000409b66 in handle_launcher_request (sock=7, who=<optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.8.3/work/kdelibs-4.8.3/kinit/kinit.cpp:1226 #25 0x000000000040a0a3 in handle_requests (waitForPid=0) at /var/tmp/portage/kde-base/kdelibs-4.8.3/work/kdelibs-4.8.3/kinit/kinit.cpp:1419 #26 0x0000000000405a8e in main (argc=2, argv=0x7fff5a50c330, envp=0x7fff5a50c600) at /var/tmp/portage/kde-base/kdelibs-4.8.3/work/kdelibs-4.8.3/kinit/kinit.cpp:1907 Reported using DrKonqi
Are you using any input method? You might be interested with reading bug 252602 comment #9
I use fcitx but it's not active when the konsole crashed. I didn't use input method to type anything into konsole either.
Thanks, that is exactly the information I have expected. Actually, as long as your input method framework (fcitx in this case) is running, it makes difference. Then, what is your fcitx version? Did you compile fcitx from git shortly before you encounter this crash? I'm asking that information because I'm also using its git version, and I notice that some recent commits before May, 10th(the day you reported this crash) might be related with this crash.
I was using fcitx-4.2.3, after downgrading it to 4.2.2 the problem seems to be solved.
*** Bug 302715 has been marked as a duplicate of this bug. ***
I thought the problem is, fcitx use a eventloop inside process key, to avoid block whole program. But if that key event will trigger qwidget destroy.. in some case this might happens... There are some other way to implement x11EventFilter, one of them use waitForFinished for a dbus call, which looks not good, the other is to feed back XEvent to main eventloop, which is not thoroughly tested... But anyway you can close this bug at here.
*** Bug 314488 has been marked as a duplicate of this bug. ***
*** Bug 319784 has been marked as a duplicate of this bug. ***