You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the GNOME file manager to copy a ~150mb file to Onedrive on a slow connection, the file manager generally reports success in a few seconds, but the file isn't actually copied. Using onedriver to unmount and remount will show the file's not on Onedrive. However, the file continues to upload in the background, and if you wait long enough then it will make it to the destination.
It would be better for GNOME to only report success when the file has actually been copied to Onedrive. Is this something in GNOME's domain, or can Onedriver do something to help ensure this? Happy to take a look if you'd like to point me in roughly the right direction!
The text was updated successfully, but these errors were encountered:
I think this is Nautilus' flaw in handling time-consuming operations in general. They do the same when extracting tarballs, which caught me off-guard a few times, until I realized it and switched to using Nemo.
Seen on Ubuntu.
When using the GNOME file manager to copy a ~150mb file to Onedrive on a slow connection, the file manager generally reports success in a few seconds, but the file isn't actually copied. Using onedriver to unmount and remount will show the file's not on Onedrive. However, the file continues to upload in the background, and if you wait long enough then it will make it to the destination.
It would be better for GNOME to only report success when the file has actually been copied to Onedrive. Is this something in GNOME's domain, or can Onedriver do something to help ensure this? Happy to take a look if you'd like to point me in roughly the right direction!
The text was updated successfully, but these errors were encountered: