GNOME Bugzilla – Bug 75617
files don't disappear after move [fam issue?] -> file accidentally deleted
Last modified: 2004-12-22 21:47:04 UTC
i had some files on my desktop ($HOME) and dragged them to another nautilus window, and dropped them on a directory. they still appeared on the desktop, and were also in the directory i dropped them on. ls in a terminal does not show the files being in $HOME. if i go to 'show properties' it says it is in the folder i dropped it on, and not in $HOME. if i delete the file from my desktop, it deletes the file in the place where i dropped it! the icon still is on my desktop! if i go to $HOME in the other nautilus window, the icon on the desktop goes to a plain text one with the no read / no write emblems. if i go to 'show properies' everything in there is "unknown"
Yargh. I just saw a duplicate of this but I can't find it now. Grr.
*** Bug 78063 has been marked as a duplicate of this bug. ***
I see this relatively often, but I can't accurately reproduce it. It happens more often with multiple files than a single file, and most of the time right after starting Nautilus. The files _are_ actually moved / deleted, but the directory they moved from isn't updated. Pressing Ctrl+R to reload fixes the problem.
Havoc's thoughts on this: puntable if it turns out to be unreproduceable bogon Mine, for the record: not at all puntable; it happens to me nearly every time I delete a folder and can lead to major data issues. So leaving as high and marking as 2.0.0.
Are we sure this isn't a fam bug. Alex has commented on and closed other bugs that seem similar stating that upgrading fam is the fix. Just an idea.
*** Bug 75078 has been marked as a duplicate of this bug. ***
is there a new fam available?
Apparently in redhat rawhide...
Created attachment 8375 [details] [review] Removes unready files from the directory view
I was able to reproduce this more or less at will, with the fam from rawhide. The attached patch fixes it.
Created attachment 8377 [details] [review] a slightly better patch
The patch looks good. But can you update to the comment above the loop. Please commit.
I checked this in. I believe the bug should be fixed now.
*** Bug 81255 has been marked as a duplicate of this bug. ***