I was in the process of creating this bug report when I got a popup that said that 2.11.3 was no longer supported. My Fedora 19 system is as up to date as RedHat makes this release. Here's the complete file that would have been reported by the KDE bug reporting software: cat konsole-20140501-010559.kcrash.txt Application: konsole (2.11.3) KDE Platform Version: 4.11.5 Qt Version: 4.8.5 Operating System: Linux 3.13.9-100.fc19.x86_64 x86_64 Distribution: "Fedora release 19 (Schrödinger’s Cat)" -- Information about the crash: - What I was doing when the application crashed: Closing tabs with ctrrl-d. - Unusual behavior I noticed: Just the crash and subsequent disappearance of the other konsoles, also with multiple tabs - Custom settings of the application: Nothing special comes to mind. Different font, color, scroll bar on left, lines in scroll buffer. The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/usr/lib64/libthread_db.so.1". 81 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f98ec5068c0 (LWP 3516))] Thread 2 (Thread 0x7f98dbfff700 (LWP 3300)): #0 0x000000316feeb7fd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x0000003c096480b4 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f98d4002bb0, timeout=-1, context=0x7f98d40009a0) at gmain.c:3995 #2 g_main_context_iterate (context=context@entry=0x7f98d40009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3696 #3 0x0000003c096481bc in g_main_context_iteration (context=0x7f98d40009a0, may_block=1) at gmain.c:3762 #4 0x0000003c0c3a6d56 in QEventDispatcherGlib::processEvents (this=0x7f98d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #5 0x0000003c0c378b2f in QEventLoop::processEvents (this=this@entry=0x7f98dbffece0, flags=...) at kernel/qeventloop.cpp:149 #6 0x0000003c0c378e25 in QEventLoop::exec (this=this@entry=0x7f98dbffece0, flags=...) at kernel/qeventloop.cpp:204 #7 0x0000003c0c278a1f in QThread::exec (this=this@entry=0x25de390) at thread/qthread.cpp:536 #8 0x0000003c0c35a3e3 in QInotifyFileSystemWatcherEngine::run (this=0x25de390) at io/qfilesystemwatcher_inotify.cpp:265 #9 0x0000003c0c27b0bf in QThreadPrivate::start (arg=0x25de390) at thread/qthread_unix.cpp:338 #10 0x0000003170a07c53 in start_thread (arg=0x7f98dbfff700) at pthread_create.c:308 #11 0x000000316fef5dbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7f98ec5068c0 (LWP 3516)): [KCrash Handler] #6 0x0000000002b2f7d0 in ?? () #7 0x0000003c0dc3df10 in QApplication::x11ProcessEvent (this=0x7fff3a9401a0, event=event@entry=0x7fff3a93fc90) at kernel/qapplication_x11.cpp:3441 #8 0x0000003c0dc64d34 in x11EventSourceDispatch (s=s@entry=0x2559ac0, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148 #9 0x0000003c09647dc6 in g_main_dispatch (context=0x2558ae0) at gmain.c:3054 #10 g_main_context_dispatch (context=context@entry=0x2558ae0) at gmain.c:3630 #11 0x0000003c09648118 in g_main_context_iterate (context=context@entry=0x2558ae0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3701 #12 0x0000003c096481bc in g_main_context_iteration (context=0x2558ae0, may_block=1) at gmain.c:3762 #13 0x0000003c0c3a6d35 in QEventDispatcherGlib::processEvents (this=0x247fe70, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #14 0x0000003c0dc64ea6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207 #15 0x0000003c0c378b2f in QEventLoop::processEvents (this=this@entry=0x7fff3a940070, flags=...) at kernel/qeventloop.cpp:149 #16 0x0000003c0c378e25 in QEventLoop::exec (this=this@entry=0x7fff3a940070, flags=...) at kernel/qeventloop.cpp:204 #17 0x0000003c0c37e0a9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221 #18 0x0000003c0dbc6c9c in QApplication::exec () at kernel/qapplication.cpp:3823 #19 0x00000032cda16cf7 in kdemain (argc=3, argv=0x7fff3a9402d8) at /usr/src/debug/konsole-4.11.5/src/main.cpp:86 #20 0x000000316fe21b45 in __libc_start_main (main=0x400840 <main(int, char**)>, argc=3, ubp_av=0x7fff3a9402d8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff3a9402c8) at libc-start.c:274 #21 0x0000000000400871 in _start () The reporter indicates this bug may be a duplicate of or related to bug 326805. Possible duplicates by query: bug 333662, bug 333610, bug 332095, bug 332023, bug 329197. Reproducible: Sometimes Steps to Reproduce: 1.Make Konsole and a bunch of tabs 2.use ctrl-d to close the tabs 3. Actual Results: ALL konsole instances in the virtual desktop were destroyed including the browser that I had started. Expected Results: I was in the process of making the bug report when I get the popup which appears to be saying "2.11.3" is no longer supported. This version is the latest that the Fedora project provides.
Could you please check if you have some "input method" tools such as ibus or fcitx installed? If yes, does removing them help to resolve the issue?
Looks like some crash in qt glib event loop processing. fun. Could possibly be a side-effect of a downstream qt patch touching some of the same code: https://bugreports.qt-project.org/browse/QTBUG-21900
Rex, we are also seeing this on Ubuntu, e.g. bug 333607. Some reporters indicate they are using input methods, but many other reporters did not respond.
Christoph/Rex, I am willing to provide other info if needed or to test patches. This bug is a royal pain in the you know where. Thanks, George...
Christoph, I tried removing ibus from my system by typing rpm -qa | grep ibus > removethese. I added a "yum erase" command and tried this script. I got several pages of dependencies to be removed... perl, coreutils, libreoffice among a LOT of others. Any other thoughts on this problem? Regards, George...
That's odd, because on my system (openSUSE 13.1), I do not need to have ibus installed for those critical applications. It is only dragged in by kdeplasma-addons, but there I have forced to install it without ibus. Can you find out which package drags it in on your system? Or can you uninstall ibus without uninstalling the stuff that apparently needs it? Or maybe Kurt can offer some patches for testing.
Created attachment 86415 [details] Gzip'd output of a "script -c ./removethese removethese.script" command. I did a "rpm -qa | grep ibus > removethese" command then massaged the file into a "yum erase" command + args. This attachment is the output of a "script -c ./removethese removethese.script" command.
Ah, your problem is that you try to remove everything that contains the letters "ibus", including "libusb" and many other crucial packages. Please try using a graphical package manager, where you can see which packages you have marked for deinstallation.
Or use `yum erase ibus*` (this will only match packages whose names start with ibus), of course cancel the operation if it proposes to install half the system.
Christoph, You are the master. Thank you. DO you recommend one? Kyum used to work but I haven't been able to get it to compile. Regards, George...
Ahmad, Thank you for this suggestion. Regards, George...
Hi, I had to do some cleanup with yum-complete-transaction but yum erase ibus worked great. I'll report the results relating to this bug within a couple of days. Thanks for all your help, George...
George, can you confirm that without ibus installed Konsole does no longer crash?
Christoph I can and will confirm that I have NOT experienced this problem since removing ibus. rpm -q ibus\* package ibus* is not installed Is this enough for your purposes? Thanks, George...
Yes, thanks for the confirmation, so not using input helpers works. The hard part will be to find out if Konsole, the input helpers, or Qt itself are responsible. I guess a valgrind log would reveal more insights.
Christoph I would be willing to try to gather the info you need. I have a "released" version and a "beta" version of valgrind on my FC19 x86_64 system and a "released" version on a Virtual FC20 x86_64 system. I would need fairly detailed instructions on how to set things up though. Interested? Regards, George...
I'm able to reproduce this crash by hitting ctrl+f and ctrl+d at the same time.
Hi guys may be it's the same issue Application: konsole (2.13.2) KDE Platform Version: 4.13.3 Qt Version: 4.8.6 Operating System: Linux 3.13.0-44-lowlatency x86_64 Distribution: Ubuntu 14.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: much of tabs opened ctrl+d pressed in one of them -- 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 0x7fa7725607c0 (LWP 4838))] Thread 2 (Thread 0x7fa75be66700 (LWP 4839)): #0 0x00007fa76b24ad20 in g_private_get () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007fa76b22e3a0 in g_thread_self () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fa76b2090dd in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007fa7705a37be in QEventDispatcherGlib::processEvents (this=0x7fa7540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x00007fa7705750af in QEventLoop::processEvents (this=this@entry=0x7fa75be65de0, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007fa7705753a5 in QEventLoop::exec (this=this@entry=0x7fa75be65de0, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007fa770471c5f in QThread::exec (this=this@entry=0x27c2e90) at thread/qthread.cpp:537 #7 0x00007fa770556823 in QInotifyFileSystemWatcherEngine::run (this=0x27c2e90) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x00007fa77047432f in QThreadPrivate::start (arg=0x27c2e90) at thread/qthread_unix.cpp:349 #9 0x00007fa76baef182 in start_thread (arg=0x7fa75be66700) at pthread_create.c:312 #10 0x00007fa771ea147d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7fa7725607c0 (LWP 4838)): [KCrash Handler] #6 0x0000000004afa940 in ?? () #7 0x00007fa76f989090 in QApplication::x11ProcessEvent (this=0x7fff4659abd0, event=event@entry=0x7fff4659a6d0) at kernel/qapplication_x11.cpp:3529 #8 0x00007fa76f9b1b02 in x11EventSourceDispatch (s=0x2338c00, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #9 0x00007fa76b208e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x00007fa76b209048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x00007fa76b2090ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x00007fa7705a37a1 in QEventDispatcherGlib::processEvents (this=0x227faf0, flags=...) at kernel/qeventdispatcher_glib.cpp:434 #13 0x00007fa76f9b1bb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #14 0x00007fa7705750af in QEventLoop::processEvents (this=this@entry=0x7fff4659aaa0, flags=...) at kernel/qeventloop.cpp:149 #15 0x00007fa7705753a5 in QEventLoop::exec (this=this@entry=0x7fff4659aaa0, flags=...) at kernel/qeventloop.cpp:204 #16 0x00007fa77057ab79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #17 0x00007fa76f90e37c in QApplication::exec () at kernel/qapplication.cpp:3828 #18 0x00007fa7721846f7 in kdemain (argc=1, argv=0x7fff4659ad18) at ../../src/main.cpp:86 #19 0x00007fa771dc8ec5 in __libc_start_main (main=0x4006d0 <main(int, char**)>, argc=1, argv=0x7fff4659ad18, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff4659ad08) at libc-start.c:287 #20 0x00000000004006fe in _start ()
I recently updated to Konsole 3.0.1 with KDE Frameworks 5.9.0 and ibus + konsole no longer crash on my system with the ctrl+f and ctrl+d combination.
KDE4/konsole4 is no longer maintained, and per comment 19 the issue doesn't seem to happen with KF5. Closing (Fixed, as in it was fixed in some unknown way).