Bug 389437 - Dolphin does not deal well with a file that is visible on two places via a hardlink and that is moved onto itself
Summary: Dolphin does not deal well with a file that is visible on two places via a ha...
Status: CONFIRMED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 17.12.1
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-25 22:35 UTC by David Tonhofer
Modified: 2018-07-15 13:08 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Tonhofer 2018-01-25 22:35:34 UTC
Suppose you have A/F1.txt and B/F1.txt

Both files are backed by the same inode.

If you move A/F1.txt into directory B, Dolphin pops up a dialog saying:

"The action will overwrite the destination".

Click on "Overwrite".

The dialog disappears then reappears immediately, nothing is "moved".

This goes on forever until you "Cancel".

It is unclear what Dolphin SHOULD do in this case.

Maybe unlink A/F1.txt. Or tell the user that A/F1.txt and B/F1.txt are actually the same file and it will skip moving the file.
Comment 1 Christoph Feck 2018-02-14 17:22:46 UTC
Trying the same with 'mv' from Konsole:

mv: 'A/F1.txt' and 'B/F1.txt' are the same file
Comment 2 Julian Steinmann 2018-07-15 13:08:45 UTC
So according to the output of mv, Dolphin should probably follow this way and display a message to the user. Because the behavior described in the original report is still present in Dolphin 18.04.3, I'll confirm the report.