Application: konsole (2.8.1) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.3.0-4.fc16.x86_64 x86_64 Distribution: "Fedora release 16 (Verne)" -- Information about the crash: - What I was doing when the application crashed: I just closed a python CLI script, and BOW!! It was also crashed sometime ago when I quiting from gdb process. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f0d0f08d840 (LWP 11033))] Thread 2 (Thread 0x7f0d03f92700 (LWP 11035)): #0 0x00007ffffd7ff8de in ?? () #1 0x0000003c8a6041f1 in __GI_clock_gettime (clock_id=1, tp=0x7f0d03f91a80) at ../sysdeps/unix/clock_gettime.c:100 #2 0x0000003d97ad22e4 in do_gettime (frac=0x7f0d03f91a98, sec=0x7f0d03f91a90) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x0000003d97ba84cd in QTimerInfoList::updateCurrentTime (this=0x7f0cfc0020d0) at kernel/qeventdispatcher_unix.cpp:343 #5 0x0000003d97ba8803 in QTimerInfoList::timerWait (this=0x7f0cfc0020d0, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #6 0x0000003d97ba729c in timerSourcePrepareHelper (src=<optimized out>, timeout=0x7f0d03f91b7c) at kernel/qeventdispatcher_glib.cpp:136 #7 0x0000003d97ba7345 in timerSourcePrepare (source=<optimized out>, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169 #8 0x0000003c8b644062 in g_main_context_prepare (context=0x7f0cfc0009a0, priority=0x7f0d03f91be8) at gmain.c:2762 #9 0x0000003c8b644e6d in g_main_context_iterate (context=0x7f0cfc0009a0, block=1, dispatch=1, self=<optimized out>) at gmain.c:3069 #10 0x0000003c8b64549c in g_main_context_iteration (context=0x7f0cfc0009a0, may_block=1) at gmain.c:3152 #11 0x0000003d97ba7dc6 in QEventDispatcherGlib::processEvents (this=0x7f0cfc0008c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426 #12 0x0000003d97b78182 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #13 0x0000003d97b783d7 in QEventLoop::exec (this=0x7f0d03f91d10, flags=...) at kernel/qeventloop.cpp:204 #14 0x0000003d97a78b27 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501 #15 0x0000003d97b57e7f in QInotifyFileSystemWatcherEngine::run (this=0x1abd8c0) at io/qfilesystemwatcher_inotify.cpp:248 #16 0x0000003d97a7bb6b in QThreadPrivate::start (arg=0x1abd8c0) at thread/qthread_unix.cpp:298 #17 0x0000003c89a07d90 in start_thread (arg=0x7f0d03f92700) at pthread_create.c:309 #18 0x0000003c896f0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f0d0f08d840 (LWP 11033)): [KCrash Handler] #6 0x0000000000000000 in ?? () #7 0x0000003d9a044877 in QApplication::x11ProcessEvent (this=0x7ffffd735a00, event=0x7ffffd7355c0) at kernel/qapplication_x11.cpp:3421 #8 0x0000003d9a06c97c in x11EventSourceDispatch (s=0x17bbd90, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148 #9 0x0000003c8b644acd in g_main_dispatch (context=0x17bb800) at gmain.c:2441 #10 g_main_context_dispatch (context=0x17bb800) at gmain.c:3011 #11 0x0000003c8b6452c8 in g_main_context_iterate (context=0x17bb800, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3089 #12 0x0000003c8b64549c in g_main_context_iteration (context=0x17bb800, may_block=1) at gmain.c:3152 #13 0x0000003d97ba7d5f in QEventDispatcherGlib::processEvents (this=0x1780ee0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424 #14 0x0000003d9a06c66e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:207 #15 0x0000003d97b78182 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #16 0x0000003d97b783d7 in QEventLoop::exec (this=0x7ffffd735990, flags=...) at kernel/qeventloop.cpp:204 #17 0x0000003d97b7cdd5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148 #18 0x0000003d9fa13fd2 in kdemain (argc=3, argv=0x7ffffd735c58) at /usr/src/debug/konsole-4.8.1/src/main.cpp:89 #19 0x0000003c8962169d in __libc_start_main (main=0x400780 <main(int, char**)>, argc=3, ubp_av=0x7ffffd735c58, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffffd735c48) at libc-start.c:226 #20 0x00000000004007b1 in _start () This bug may be a duplicate of or related to bug 277484. Possible duplicates by query: bug 296622, bug 292369, bug 292141, bug 292140, bug 292139. Reported using DrKonqi
Thanks for reporting. It would be more helpful if you can provide more detailed information. 1). Is the Python script or the gdb process the initial command running in the tab? I mean after quiting it the tab is also closed. 2). If 1) is true, how did you exactly quit that gdb process? Use the "Close Tab" action in the menu or tell gdb itself to quit (Ctrl+D) ? 3). Do you use and run input method, such as ibus? You might be interested with reading bug 252602
Hi Jekyll, reply inline, Thanks,FKtPp --- On Mon, 3/26/12, Jekyll Wu <adaptee@gmail.com> wrote: From: Jekyll Wu <adaptee@gmail.com> Subject: [Bug 296758] Crash when exiting from python application To: m_pupil@yahoo.com.cn Date: Monday, March 26, 2012, 1:40 AM https://bugs.kde.org/show_bug.cgi?id=296758 Jekyll Wu <adaptee@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adaptee@gmail.com --- Comment #1 from Jekyll Wu <adaptee@gmail.com> --- Thanks for reporting. It would be more helpful if you can provide more detailed information. 1). Is the Python script or the gdb process the initial command running in the tab? I mean after quiting it the tab is also closed. Yes, the process is running in a tab. But the tab is the initial tab of my konsole, and it is the only tab kept open when crash happens. I used to open and close tabs before the crash. 2). If 1) is true, how did you exactly quit that gdb process? Use the "Close Tab" action in the menu or tell gdb itself to quit (Ctrl+D) ? I never use "close tab" menu. The python script is closed by Ctrl-C, gdb is quit by quit. 3). Do you use and run input method, such as ibus? Yes, I use ibus all the time. But I am not sure if my ibus-sunpinyin is active or not when crash happen. You might be interested with reading bug 252602
Thanks for your feedback. Now I'm quite sure it is the same problem as bug 252602. it does not matter whether your ibus-sunpinyin is active or not. As long as ibus-daemon is running in the background, the problem just might happen sometimes. *** This bug has been marked as a duplicate of bug 252602 ***