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 755335 - Restoring from Trash doesn't work
Restoring from Trash doesn't work
Status: RESOLVED DUPLICATE of bug 749314
Product: nautilus
Classification: Core
Component: Trash
3.17.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-09-21 09:53 UTC by Piotr Drąg
Modified: 2015-09-29 14:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Piotr Drąg 2015-09-21 09:53:31 UTC
This message appears:

"Could not determine original location of “my file.txt” 
The item cannot be restored from trash"


nautilus-3.17.91-1.fc23.x86_64
gvfs-1.25.92-3.fc23.x86_64
Comment 1 Allison Karlitskaya (desrt) 2015-09-28 23:52:26 UTC
Here's some 100% noise:

Someone suggested to me that this problem started appearing when the changes to file monitors landed.

The biggest effect of those changes is that events are now reported immediately instead of waiting for 1 second.  It may be that the info file is not yet (fully) on disk at the point that the event is noticed.  The old code added a 1-second delay to everything, giving more time for the info file to make it to disk.

... or it could be totally and completely unrelated.
Comment 2 Carlos Soriano 2015-09-29 07:43:22 UTC
(In reply to Ryan Lortie (desrt) from comment #1)
> Here's some 100% noise:
> 
> Someone suggested to me that this problem started appearing when the changes
> to file monitors landed.
> 
> The biggest effect of those changes is that events are now reported
> immediately instead of waiting for 1 second.  It may be that the info file
> is not yet (fully) on disk at the point that the event is noticed.  The old
> code added a 1-second delay to everything, giving more time for the info
> file to make it to disk.
> 
> ... or it could be totally and completely unrelated.

Aha, thanks Ryan for the pointer, makes sense. What is the way to deal with it? Doing a timeout in the client side?
Comment 3 Allison Karlitskaya (desrt) 2015-09-29 14:09:50 UTC

*** This bug has been marked as a duplicate of bug 749314 ***