After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 690229 - move operation problems
move operation problems
Product: gnome-commander
Classification: Other
Component: application
Other Linux
: Normal enhancement
: 2.0
Assigned To: GNOME Commander maintainer(s)
Depends on: 589069
Reported: 2012-12-14 22:53 UTC by Aleksander (Andy) Rožman
Modified: 2018-08-03 18:05 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Aleksander (Andy) Rožman 2012-12-14 22:53:14 UTC
Hi !

I have been using GCMD for some time, and I found really "bugging" problem with move... I use GCMD a lot for moving files around and there are two error that happen regulary.

1. When I start move (also copy), move window is hidden by GCMD, so I have to use Tab (or unity) interface to select it in front of base GCMD. This is quite anoying.

2. Now this is the real bug. If I select several files and start move operation, at first files are copies and after ALL are copied, sources are deleted. Now problem with this operation is, that if operation is interrupted, I have files on both source and target drive, and I don't know which were correctly copied... How operation should work is, that when file 1 is correctly copied to target it should be deleted on source. This for each file in move list... So if operation for example failes on file 5, I would have 4 files on target drive, and (count of files in copy list - 4 files already copied).

Comment 1 André Klapper 2012-12-15 09:31:31 UTC
Which exact version is this about?
Comment 2 Aleksander (Andy) Rožman 2012-12-15 09:59:39 UTC
Sorry my mistake... I selected 2.x, but in reallity it is, the latest release on Ubuntu.
Comment 3 Uwe Scholz 2014-06-17 08:04:35 UTC
Thank you for reporting. 

1. The first issue is already resolved in branch 1.4. Just install that version of GCMD.

2. The second issue is not a real bug, it is rather the normal behavior of GCMD. Only after all objects have been successfully moved, the original objects are deleted. 

If the transfer stops for whatever reason, you should start to move the selected objects again. GCMD will ask for confirmation if an already existing file/folder in the target directory will be overwritten (given that this behavior is activated in Settings->Options->Confirmation).

If you change the directory while copying/moving files, the selection of the files for moving is lost. That's why you don't know which files still have to be copied/moved. 

Therefore, I understand you bug report rather as a feature request for deleting files step by step after each one was successfully moved. This might be implemented, but only after GCMD has migrated from gnome-vfs to gvfs.
Comment 4 GNOME Infrastructure Team 2018-08-03 18:05:29 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: