Bug 402675

Summary: Synchronization Directories: No menu item to remove files on the right panel
Product: [Applications] krusader Reporter: Dmitry <dmitry.ashkadov>
Component: synchronizeAssignee: Krusader Bugs Distribution List <krusader-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: krusader-bugs-null
Priority: NOR    
Version: 2.6.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Dmitry 2018-12-29 08:38:14 UTC
SUMMARY

When I use "Synchronize Directories" tool in symmetric mode (i.e. no target directory, bidirectional synchronization) and there are files on the right panel (right directory) that do not exist on the left panel (left directory), it is not possible to remove these files from the right panel (right directory).

This looks like krusader still treats removal of files as in target/source mode (unidirectional synchronization). It is possible to remove files on the left panel but not on the right.

STEPS TO REPRODUCE

1. Make two directories "left" and "right"
2. Add file "example" to "right" directory
3. One Synchronize Directories tool with "left" and "right" directories in symmetric mode
4. Compare
5. You should see that krusader suggests copying file "example" from "right" to "left" directory
6. Right click on file "example" and you will see "Remove left file" in popup menu (I don't know exact text in English for this menu item).
7. There is nothing to remove on the left panel since the file "example" is on the right panel, there is no menu item to remove the file on the right panel.

OBSERVED RESULT

No menu item to remove file on the right panel, but there is broken menu item to remove the file on the left panel

EXPECTED RESULT

Correct menu item for removing file on the right panel, no need for menu item "remove file on the left panel"

SOFTWARE/OS VERSIONS

Linux: openSUSE Leap 15
KDE Frameworks 5.45.0
Qt 5.9.4

ADDITIONAL INFORMATION
Comment 1 Dmitry 2018-12-29 20:01:53 UTC
*** This bug has been marked as a duplicate of bug 158154 ***