No progress information while uploading to google drive mounted folder

[Dipun]

When attempting to upload a large file (a compressed 7z file ~300mb) the program showed a transfer speed of 0 bytes/s and showed no progress throughout. I cancelled a few times, but one last time, I decided to wait more than just a few minutes. The job completed, but there was not visual feedback.

This is my first bug report, but I assume that seeing as this is an edge version of Ubuntu, this is where I should report this type of thing.

Description: Ubuntu 19.10
Release: 19.10

nautilus:
  Installed: 1:3.34.1-1ubuntu1
  Candidate: 1:3.34.1-1ubuntu1
  Version table:
 *** 1:3.34.1-1ubuntu1 500
        500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 23 17:23:29 2020
GsettingsChanges:
 b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'221'
InstallationDate: Installed on 2020-03-23 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/usr/bin/zsh
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

[Sebastien Bacher (seb128)]

Thank you for your bug report. Do you get the issue every time you do a copy to a google drive location or was it a one time problem ?

How did you mount the destination?

Could you add your 'journalctl -b 0' log after getting the issue?

[Dipun (dipunm)]

Hey, it's every time. I just tried again.
I used the Ubuntu cloud accounts feature and it auto-mounted my google drive folder.
I am going to close all my programs and restart and then I'll try again to get a clean (as clean as possible) journalctl file.

[Dipun (dipunm)]

Here's the logs. I started the transfer just after 3:30.

[Sebastien Bacher (seb128)]

Thanks, I've reported it upstream now
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1442

In fact I can confirm the bug on a new installation but don't get those warnings

[Sebastien Bacher (seb128)]

The libgdata library used for gdrive integration doesn't provide the needed informations, reassigning there

[Sebastien Bacher (seb128)]

Upstream fixed it in gvfs git now