Bug 245835

Summary: Dragging images from digikam album view to Nautilus removes the original
Product: [Applications] digikam Reporter: Michiel Wittkampf <michielwittkampf>
Component: Usability-Drag&DropAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles
Priority: NOR    
Version: 1.2.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 6.3.0

Description Michiel Wittkampf 2010-07-26 22:52:54 UTC
Version:           1.2.0 (using KDE 4.4.2) 
OS:                Linux

"When i wanted to copy some images to a thumbdrive to show someone, i
dragged the images there, and after half a dozen images, i noticed they
were being deleted from the album. i restored them, but had i not
noticed, this could have been unfortunate. i was surprised (to say the
least) that the drag and drop action from digikam album to nautilus was
a move rather than a copy. i tend to expect a drag and drop to any
removable media to be interpreted as a copy.
i do notice when dragging images from one album to another in digikam,
the app gives you the option to "move" or "copy" which is great. also,
when dragging from nautilus to digikam you get that choice."

I think digiKam, as photoalbum storage should protect its photos. Also when Gnome is the desktop environment. Can you please make this happen?


Text based on:
http://www.listware.net/201004/digikam-users/85543-digikam-users-dragging-images-from-digikam-album-view-to-nautilus-removes-the-original.html

Reproducible: Always

Steps to Reproduce:
Drag a photo from digikam to Gnome desktop (without using keyboard keys.)

Actual Results:  
Photo is moved to desktop

Expected Results:  
Photo is copied to desktop
Comment 1 caulier.gilles 2010-07-28 10:31:59 UTC
Marcel,

I think a similar report have been done for 1.2.0 release. right ?

Gilles Caulier
Comment 2 caulier.gilles 2010-07-28 10:48:58 UTC

*** This bug has been marked as a duplicate of bug 219908 ***
Comment 3 caulier.gilles 2019-08-14 18:59:08 UTC
Fixed with bug #219908