Bug 412538

Summary:	Moving/copying files doesn't integrate well with Dolphin
Product:	[Applications] gwenview	Reporter:	Marcin Gurtowski <halftough29a>
Component:	general	Assignee:	Gwenview Bugs <gwenview-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	justin.zobel, mr-peipei
Priority:	NOR
Version First Reported In:	19.08.1
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Marcin Gurtowski 2019-10-02 17:34:16 UTC

SUMMARY
Moving and copying files by dragging them into directories in Dolphin is little buggy.

When dropping file from Gwenview into Dolphin while holding shift (to move it) it only copies. Even though dropping it without shift will result in showing menu, suggesting that holding shift is quick way to move file.

Sometimes when dropping file "move" won't appear as one of the options.

When dragging file into sub-directory, often it will be moved into parent directory instead.


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.16
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.3
Kernel Version: 5.0.0-29-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-4690K CPU @ 3.50GHz
Memory: 7,7 GiB

Comment 1 Felipe Peter 2019-10-03 15:05:10 UTC

I can confirm some of that behavior under Manjaro. 

The move option was always shown to me when dragging a file to Dolphin. The file was also never copied to a parent directory. But the files were indeed randomly copied or moved although I always pressing the shift key.

Comment 2 Marcin Gurtowski 2019-10-03 15:29:30 UTC

To clarify. By "parent" directory I mean currently opened directory and not its child, to which file wale dragged.

Comment 3 Justin Zobel 2020-11-29 23:49:16 UTC

I've just tested this on 20.08.3 gwenview and I can't replicate any of these issues.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.

Comment 4 Marcin Gurtowski 2020-11-30 18:17:47 UTC

I'm also no longer able to reproduce this bug.

Comment 5 Justin Zobel 2020-11-30 21:51:34 UTC

I'm changing this one to resolved then. If Felipe can reproduce it can be reopened.