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 755701 - Document changes its name after in-fs copy/move
Document changes its name after in-fs copy/move
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: google backend
1.26.x
Other All
: Normal normal
: ---
Assigned To: Debarshi Ray
gvfs-maint
: 769358 790593 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-09-27 17:12 UTC by Serge Matveenko
Modified: 2018-06-14 06:57 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
google: Fail in-fs copy/move if it leads to display name loss (2.09 KB, patch)
2015-10-19 12:33 UTC, Ondrej Holy 		committed Details | Review

Description Serge Matveenko 2015-09-27 17:12:35 UTC 
1. Connect google account via gnome online accounts
2. Open Drive in nautilus.
3. Select any file created in Google Docs.
4. Press Ctrl+X.
5. Open any folder inside Google drive.
6. Press Ctrl+V.

ER: File moved into folder keeping its original name.

AR: File moved into folder changing its name to the long sequence of random looking latin characters.
Comment 1 Debarshi Ray 2015-09-30 17:51:23 UTC 
Yes, this is a known limitation at this point arising out of the issues described in https://debarshiray.wordpress.com/2015/09/13/google-drive-and-gnome-what-is-a-volatile-path/

We are exploring various options to fix this.
Comment 2 Ondrej Holy 2015-10-19 12:28:34 UTC 
Also some development related info can be found in Bug 739008.
Comment 3 Ondrej Holy 2015-10-19 12:33:09 UTC 
Created attachment 313658 [details] [review]
google: Fail in-fs copy/move if it leads to display name loss

Proper solution of this requires larger platform changes and therefore I doubt we are able to fix it for GNOME 3.18.x properly.

So I propose this patch for stable release to fail the copy/move operation if it leads to display name loss...
Comment 4 Debarshi Ray 2015-10-21 16:03:56 UTC 
Review of attachment 313658 [details] [review]:

Looks good to me, Ondrej.

I tested it with both nautilus and gvfs-copy, and it worked as expected. It failed the nautilus operation, and if I used gvfs-copy with a human readable title then the operation succeeded.
Comment 5 Ondrej Holy 2015-10-23 07:14:30 UTC 
Comment on attachment 313658 [details] [review]
google: Fail in-fs copy/move if it leads to display name loss

Thanks for review, pushed as commit d236257.
Comment 6 Ondrej Holy 2017-07-25 10:28:06 UTC 
*** Bug 769358 has been marked as a duplicate of this bug. ***
Comment 7 Ondrej Holy 2017-11-20 08:56:20 UTC 
*** Bug 790593 has been marked as a duplicate of this bug. ***
Comment 8 Ondrej Holy 2018-06-14 06:57:32 UTC 
Let's close this as obsolete and use the following for tracking: https://gitlab.gnome.org/GNOME/gvfs/issues/8.