Dolphin crashed when I repeat F2 and ESC. How many times - that is irregular, but within 10 times. Same thing happens when I use the menu with keystroke, i.e., Alt+F, R, and ESC, or when I click the menu. Curiously, F2-ESC takes much fewer tries than clicks. I tried repeating Delete / cancel but that was safe. Similarly, alternating Alt+Enter / ESC was safe. It seems that the bug is triggered when a text box was active when ESC was hit. Because opening Configure Dolphin, entering Location, then hitting ESC triggers the same kind of crash. So I suspected ibus and quit it. Then dolphin did not crash after 81 rounds of F2 and ESC. Then I turned it back on and the symptom reappeared. Fedora 16, ibus 1.4.1 with ibus-hangul. Reproducible: Always Steps to Reproduce: 1. open im-chooser and select ibus. 2. while ibus is running, open dolphin to any location. 3. select any file and repeat F2 and ESC a few times. 4. alternatively, repeat opening Configure Dolphin, clicking Location text box and hitting ESC a few times. Actual Results: dolphin immediately crashes. but other instances of dolphin are unaffected. Fedora 16, ibus 1.4.1 with ibus-hangul. Application: Dolphin (dolphin), 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 0x7f42a1897840 (LWP 20530))] Thread 4 (Thread 0x7f4295983700 (LWP 20537)): #0 0x0000003fafce85c3 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x0000003fb1c45448 in ?? () from /lib64/libglib-2.0.so.0 #2 0x0000003fb1c4590c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x0000003fba5a91df in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #4 0x0000003fba579312 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #5 0x0000003fba579567 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #6 0x0000003fba478b87 in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x0000003fba558f9f in ?? () from /usr/lib64/libQtCore.so.4 #8 0x0000003fba47bbcb in ?? () from /usr/lib64/libQtCore.so.4 #9 0x0000003fb0407d90 in start_thread (arg=0x7f4295983700) at pthread_create.c:309 #10 0x0000003fafcf0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f428ffff700 (LWP 20539)): #0 0x0000003fafce85c3 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x0000003fb1c45448 in ?? () from /lib64/libglib-2.0.so.0 #2 0x0000003fb1c4590c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x0000003fba5a91df in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #4 0x0000003fba579312 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #5 0x0000003fba579567 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #6 0x0000003fba478b87 in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x0000003fba558f9f in ?? () from /usr/lib64/libQtCore.so.4 #8 0x0000003fba47bbcb in ?? () from /usr/lib64/libQtCore.so.4 #9 0x0000003fb0407d90 in start_thread (arg=0x7f428ffff700) at pthread_create.c:309 #10 0x0000003fafcf0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f428f7fe700 (LWP 20541)): #0 0x0000003fafcea403 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x0000003fba5574ef in ?? () from /usr/lib64/libQtCore.so.4 #2 0x0000003fba47bbcb in ?? () from /usr/lib64/libQtCore.so.4 #3 0x0000003fb0407d90 in start_thread (arg=0x7f428f7fe700) at pthread_create.c:309 #4 0x0000003fafcf0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f42a1897840 (LWP 20530)): [KCrash Handler] #6 0x00000000024981d0 in ?? () #7 0x0000003fbc444877 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4 #8 0x0000003fbc46cb2c in ?? () from /usr/lib64/libQtGui.so.4 #9 0x0000003fb1c44f3d in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #10 0x0000003fb1c45738 in ?? () from /lib64/libglib-2.0.so.0 #11 0x0000003fb1c4590c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #12 0x0000003fba5a91df in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #13 0x0000003fbc46c81e in ?? () from /usr/lib64/libQtGui.so.4 #14 0x0000003fba579312 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #15 0x0000003fba579567 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #16 0x0000003fba57e225 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #17 0x0000003fc0248527 in kdemain () from /usr/lib64/libkdeinit4_dolphin.so #18 0x0000003fafc2169d in __libc_start_main (main=0x4007a0, argc=5, ubp_av=0x7fffbe7d69b8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffbe7d69a8) at libc-start.c:226 #19 0x00000000004007d1 in _start ()
Thanks for the report. I don't have ibus installed currently but the backtrace might indicate that the root-cause is in Qt and might be related to https://bugreports.qt-project.org/browse/QTBUG-19363
Hi, I have a similar bug. The only difference is that I use fcitx instead of ibus. When fcitx was running, dolphin would crash after I hit F2 followed by ESC for less than 50 times. (Sometimes it would take only one renaming/cancelling to crash dolphin. ) When fcitx was not running, dolphin would not crash even if I hit F2 followed by ESC for more than 100 times. As mskyeong@naver.com has pointed out, this bug seems to be related to text fields within a pop-up dialogue. I have little chance to discover this bug before using kde v4.8 because I used to rename inline, that is, without triggering a pop-up renaming dialog. As renaming inline is not supported in dolphin 2.0, this bug is readily exposed. By the way, I am using dolphin 2.0 on kde 4.8.4. The OS is debian wheezy/sid. The linux kernel is 3.2.0-2-amd64.
I can't reproduce the crash when using neither ibus nor fcitx. FYI, inline renaming is back in dolphin 2.1 (shipped in the upcoming KDE SC 4.9).
Resetting assignee to default as per bug #305719
Please reopen if you still see this crash in KDE 4.10 or later. Thanks.
Actually closing this bug now. Please reopen if you can still reproduce.