Bug 206386 - Dolphin crashing while dragging a file to a folder in order to copy it
Summary: Dolphin crashing while dragging a file to a folder in order to copy it
Status: RESOLVED DUPLICATE of bug 203887
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-05 16:33 UTC by Andreas Stangl
Modified: 2009-12-18 19:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Stangl 2009-09-05 16:33:55 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-gentoo-r5 x86_64

What I was doing when the application crashed:
1. I had two columns visible
2. I tried to move a file from the right column to a folder from the left column via drag and drop
3. <crash>

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 0 (LWP 5505)]

Thread 2 (Thread 0x7fa34f57b910 (LWP 5747)):
#0  0x00007fa35a67123d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fa34e3fe882 in ?? () from /usr/lib64/libxine.so.1
#2  0x00007fa35a66c614 in start_thread () from /lib64/libpthread.so.0
#3  0x00007fa3591d556d in clone () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa35dcc4750 (LWP 5505)):
[KCrash Handler]
#5  0x00007fa35a8d79da in QMutex::lock (this=0x8adc10) at thread/qmutex.cpp:152
#6  0x00007fa35a99df58 in QCoreApplication::postEvent (receiver=0xc5f0d0, event=0xe8bce0, priority=0) at kernel/qcoreapplication.cpp:1020
#7  0x00007fa359dfddb7 in QX11Data::xdndHandleFinished (this=<value optimized out>, xe=<value optimized out>, passive=<value optimized out>) at kernel/qdnd_x11.cpp:1244
#8  0x00007fa359de0e16 in QApplication::x11ClientMessage (this=<value optimized out>, w=0x878dc0, event=0x0, passive_only=208) at kernel/qapplication_x11.cpp:3126
#9  0x00007fa359dedccd in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fff2f715540) at kernel/qapplication_x11.cpp:3677
#10 0x00007fa359e0fe92 in x11EventSourceDispatch (s=<value optimized out>, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146
#11 0x00007fa3564ff3dd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#12 0x00007fa356502519 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0x00007fa356502678 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#14 0x00007fa35a9bed8d in QEventDispatcherGlib::processEvents (this=0x681790, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#15 0x00007fa359e0f832 in QGuiEventDispatcherGlib::processEvents (this=0x8adc10, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#16 0x00007fa35a99cf42 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#17 0x00007fa35a99d0cc in QEventLoop::exec (this=0x7fff2f715860, flags=) at kernel/qeventloop.cpp:197
#18 0x00007fa35a0f299a in QMenu::exec (this=<value optimized out>, p=@0xdddaa8, action=0x0) at widgets/qmenu.cpp:1993
#19 0x00007fa35cf474f0 in KonqOperations::doDropFileCopy () from /usr/lib64/libkonq.so.5
#20 0x00007fa35cf47fe5 in KonqOperations::asyncDrop () from /usr/lib64/libkonq.so.5
#21 0x00007fa35cf48651 in KonqOperations::qt_metacall () from /usr/lib64/libkonq.so.5
#22 0x00007fa35a9aacf0 in QObject::event (this=0xed8080, e=0x1067690) at kernel/qobject.cpp:1099
#23 0x00007fa359d96cf5 in QApplicationPrivate::notify_helper (this=0x6b0af0, receiver=0xed8080, e=0x1067690) at kernel/qapplication.cpp:4056
#24 0x00007fa359d9ccc4 in QApplication::notify (this=0x7fff2f716af0, receiver=0xed8080, e=0x1067690) at kernel/qapplication.cpp:4021
#25 0x00007fa35b787cf8 in KApplication::notify () from /usr/lib64/libkdeui.so.5
#26 0x00007fa35a99e20c in QCoreApplication::notifyInternal (this=0x7fff2f716af0, receiver=0xed8080, event=0x1067690) at kernel/qcoreapplication.cpp:606
#27 0x00007fa35a99e918 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x681f80) at kernel/qcoreapplication.h:213
#28 0x00007fa35a9bf08f in postEventSourceDispatch (s=<value optimized out>) at kernel/qcoreapplication.h:218
#29 0x00007fa3564ff3dd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0x00007fa356502519 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0x00007fa356502678 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0x00007fa35a9bed8d in QEventDispatcherGlib::processEvents (this=0x681790, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#33 0x00007fa359e0f832 in QGuiEventDispatcherGlib::processEvents (this=0x8adc10, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#34 0x00007fa35a99cf42 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#35 0x00007fa35a99d0cc in QEventLoop::exec (this=0x7fff2f716a40, flags=) at kernel/qeventloop.cpp:197
#36 0x00007fa35a99eb29 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0x0000000000438879 in _start ()

This bug may be a duplicate of or related to bug 203384

Reported using DrKonqi
Comment 1 Dario Andres 2009-09-05 16:58:28 UTC
- "Two columns" <- is that a split view or the Column view showing the same folder herarchy ?
- Which were the folders you were showing ? how they are related? (example: "folder on the right side is a subfolder of the one being shown in the left side") 
- Do you have desktop compositing/effects ?
- Can you reproduce the crash at will ?

The backtrace looks like bug 203384 indeed

Thanks
Comment 2 Andreas Stangl 2009-09-05 17:10:21 UTC
(In reply to comment #1)
> - "Two columns" <- is that a split view or the Column view showing the same
> folder herarchy ?

This is not a split view. I selected a folder in the left column and the right column showed me the content of the selected folder

> - Which were the folders you were showing ? how they are related? (example:
> "folder on the right side is a subfolder of the one being shown in the left
> side")

* <folder 1>
* <folder 2> <-- this is the selected folder
*      <file 1>
*      <file 2>   <-- the files are shown in the right column

I tried to move <file 1> to <folder 1>

> - Do you have desktop compositing/effects ?

Yes, compositing is enabled

> - Can you reproduce the crash at will ?

Unfortunately not, I was moving a couple of files from <folder 2> to <folder 1> without any problems, but suddenly dolphin crashed. After the crash I continued moving files from <folder 2> to <folder 1> without any problems.
Comment 3 Andreas Stangl 2009-09-05 17:12:57 UTC
Maybe I should also notice this: Dolphin crashed before the popup dialog ("Move File", "Copy File", "Create Link", "Cancel") was shown.
Comment 4 Peter Penz 2009-12-18 19:03:57 UTC

*** This bug has been marked as a duplicate of bug 203887 ***