Comment 0 for bug 1560454

This happens only if a user have appropriate rights on the folder where the maps are stored. So it is not valid for a normal widelands installation (at least on linux, on windows i couldn't check this)
Also only when saving with the same name.

Steps to reproduce:
Make sure not to have saved maps in ~/.widelands/maps , especially maps named like shipped maps
Start widelands from one of your bzr branches (where you have read/write permissions)
Start editor and load a shipped map (i used "Glacier_Lake")
Open Save window and give the map the exact same filename
Press "Save"

Result:
1. A Window pops up "The File already exists" -> This is strange, because normally the folder ~/.widelands/maps is used and not the maps folder of the branch where you started widelands
2. If you save nevertheless, the map from your branch/data/maps folder gets removed and the new map is stored in ~/.widelands/maps

If you use the --datadir option the file from that map folder get removed.

I have tested this with a normal installation on linux and here all is fine. I believe because a normal user haven't the rights to delete a file outsite his home folder.

I mark it as "High", feel free to set it to medium because it affects only folders where read/write permission is given.