Bug 284877

Summary: Dolphin crashed after editing file name using inline editor (invoked using F2 keyboard shortcut)
Product: [Applications] dolphin Reporter: Michał D. (Emdek) <emdeck>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: crash CC: adaptee, post5000, roman.karlstetter
Priority: NOR    
Version: 1.7   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi
New crash information added by DrKonqi

Description Michał D. (Emdek) 2011-10-24 15:45:13 UTC
Application: dolphin (1.7)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-13-generic i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:
Dolphin crashed after opening inline file name editor (using F2 keyboard shortcut) and switching to another window without closing editor.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 1 (Thread 0xb77cf710 (LWP 22315))]

Thread 3 (Thread 0xb6848b70 (LWP 22316)):
#0  0x00930416 in __kernel_vsyscall ()
#1  0x001ea40e in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x02b3d34b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x02b2e896 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x02b2ec2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x0579fb37 in QEventDispatcherGlib::processEvents (this=0x8852b48, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x057701dd in QEventLoop::processEvents (this=0xb68482b0, flags=...) at kernel/qeventloop.cpp:149
#7  0x05770421 in QEventLoop::exec (this=0xb68482b0, flags=...) at kernel/qeventloop.cpp:201
#8  0x0567390b in QThread::exec (this=0x8850a50) at thread/qthread.cpp:498
#9  0x05750e2d in QInotifyFileSystemWatcherEngine::run (this=0x8850a50) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x056767b3 in QThreadPrivate::start (arg=0x8850a50) at thread/qthread_unix.cpp:331
#11 0x0090ed31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0x001f90ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 2 (Thread 0xb4863b70 (LWP 22319)):
#0  0x056cd7f5 in qt_gettime () at tools/qelapsedtimer_unix.cpp:146
#1  0x057a04b6 in QTimerInfoList::updateCurrentTime (this=0x8a1dc3c) at kernel/qeventdispatcher_unix.cpp:339
#2  0x057a080a in QTimerInfoList::timerWait (this=0x8a1dc3c, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#3  0x0579f053 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb486312c) at kernel/qeventdispatcher_glib.cpp:136
#4  0x0579f0ed in timerSourcePrepare (source=0x8a1dc08, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#5  0x02b2d88c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0x02b2e637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x02b2ec2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0x0579fb37 in QEventDispatcherGlib::processEvents (this=0x89464b8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#9  0x057701dd in QEventLoop::processEvents (this=0xb48632b0, flags=...) at kernel/qeventloop.cpp:149
#10 0x05770421 in QEventLoop::exec (this=0xb48632b0, flags=...) at kernel/qeventloop.cpp:201
#11 0x0567390b in QThread::exec (this=0x8a1a8f0) at thread/qthread.cpp:498
#12 0x05750e2d in QInotifyFileSystemWatcherEngine::run (this=0x8a1a8f0) at io/qfilesystemwatcher_inotify.cpp:248
#13 0x056767b3 in QThreadPrivate::start (arg=0x8a1a8f0) at thread/qthread_unix.cpp:331
#14 0x0090ed31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#15 0x001f90ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb77cf710 (LWP 22315)):
[KCrash Handler]
#7  QCoreApplication::notifyInternal (this=0xbfe75ac4, receiver=0x90fd858, event=0xbfe753dc) at kernel/qcoreapplication.cpp:774
#8  0x0197261b in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#9  QApplicationPrivate::dispatchEnterLeave (enter=0x90fd858, leave=0x22dccbc) at kernel/qapplication.cpp:2810
#10 0x019fdc65 in QApplication::x11ProcessEvent (this=0xbfe75ac4, event=0xbfe7572c) at kernel/qapplication_x11.cpp:3763
#11 0x01a2a24c in x11EventSourceDispatch (s=0x86e2048, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#12 0x02b2e25f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#13 0x02b2e990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#14 0x02b2ec2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#15 0x0579fada in QEventDispatcherGlib::processEvents (this=0x86c6bb0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#16 0x01a29e3a in QGuiEventDispatcherGlib::processEvents (this=0x86c6bb0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#17 0x057701dd in QEventLoop::processEvents (this=0xbfe75a34, flags=...) at kernel/qeventloop.cpp:149
#18 0x05770421 in QEventLoop::exec (this=0xbfe75a34, flags=...) at kernel/qeventloop.cpp:201
#19 0x0577519d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#20 0x0196f8f4 in QApplication::exec () at kernel/qapplication.cpp:3760
#21 0x00762433 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_dolphin.so
#22 0x0804850b in ?? ()
#23 0x00140113 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
#24 0x08048531 in _start ()

Possible duplicates by query: bug 284624, bug 283332, bug 282257, bug 282067, bug 280972.

Reported using DrKonqi
Comment 1 Roman K. 2011-10-27 15:25:30 UTC
Created attachment 64943 [details]
New crash information added by DrKonqi

dolphin (1.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4

- What I was doing when the application crashed: renamed a file (F2) and then dolphin crashed

-- Backtrace (Reduced):
#6  QCoreApplication::notifyInternal (this=0x7fffc67d3ea0, receiver=0xe5f210, event=0x7fffc67d33b0) at kernel/qcoreapplication.cpp:774
#7  0x00007f5c24649b76 in sendEvent (enter=0xe5f210, leave=<value optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:215
#8  QApplicationPrivate::dispatchEnterLeave (enter=0xe5f210, leave=<value optimized out>) at kernel/qapplication.cpp:2805
#9  0x00007f5c246c75db in QApplication::x11ProcessEvent (this=0x7fffc67d3760, event=0x7fffc67d3ad0) at kernel/qapplication_x11.cpp:3660
#10 0x00007f5c246ef512 in x11EventSourceDispatch (s=0x6cf8e0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
Comment 2 Michał D. (Emdek) 2011-10-29 16:57:56 UTC
This bug is extremely annoying, especially if you have opened multiple tabs (it would be less if it would finally have ability to restore them...).
Comment 3 Jekyll Wu 2011-11-24 02:08:40 UTC

*** This bug has been marked as a duplicate of bug 279526 ***
Comment 4 post5000 2012-01-03 16:50:40 UTC
Created attachment 67401 [details]
New crash information added by DrKonqi

dolphin (1.7) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4

- What I was doing when the application crashed:
inline rename a file by pressing F2
- Custom settings of the application:

inline rename active

-- Backtrace (Reduced):
#6  QCoreApplication::notifyInternal (this=0x7fffbc745910, receiver=0x2be81b0, event=0x7fffbc744f30) at kernel/qcoreapplication.cpp:774
#7  0x00007f55018e0cab in sendEvent (event=0x7fffbc744f30, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#8  QApplicationPrivate::dispatchEnterLeave (enter=0x2be81b0, leave=<optimized out>) at kernel/qapplication.cpp:2810
#9  0x00007f550195f701 in QApplication::x11ProcessEvent (this=0x7fffbc745910, event=0x7fffbc7454d0) at kernel/qapplication_x11.cpp:3763
#10 0x00007f5501988412 in x11EventSourceDispatch (s=0x1ff1cf0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146