Bugzilla – Bug 343725
gnome-main-menu - rename or remove items does not work
Last modified: 2011-04-02 16:47:21 UTC
Renaming or removing (move to trash) items from Documents or Places Tab in the gnome-main-menu does not word.
s/word/work/
If I remove a document or place in gnome-main-menu (assuming sufficient perms), it's moved to trash, but it still shows up in gnome-main-menu and at least appears not to work. If I rename a document or place in gnome-main-menu (assuming sufficient perms), the file/directory name is changed, and the basename that appears at first glance in gnome-main-menu is correct, but gnome-main-menu apparently doesn't recognize the change internally. The full-path hover tip still specifies the old name, and if I try to open the document/place, the operation fails, since the file it's trying to open no longer exists. Subsequent attempts to remove the document/place fail similarly.
Just to add my observations... 1) Renaming the document via Slab will rename the document on disk and the name in Slab, but not the pointer to the file itself. 2) When you monitor a file with GNOME VFS, it wont report anything back when the parent directory name changes. 3) When you monitor a file with GNOME VFS, and you rename the file via nautilus, it will report back that the file was deleted. Should be easy to fix 1 above, but not sure what a proper solution would be for 2 and 3.
The whole rename/delete/move to trash thing in the main menu seems really confusing to me. It allows you to accidentally remove files. Besides when you are renaming a file you can't be sure which one it is without looking at the the tooltip. In my opinion the rename/delete/move to trash are file manager actions so it would be best to leave it up to the file manager to do these, so we could instead add a "Reveal in file manager" action which would be more useful.
Still present in 11.0 Factory. Moving.
The version with which you had the bug is now obsolete. I'll close this as NORESPONSE. If you can still reproduce it in current 11.4, please reopen the bug and move it to the appropriate version. Thanks!