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 768594 - File manager gives "not authenticated" after idling for certain period of time
File manager gives "not authenticated" after idling for certain period of time
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: google backend
1.28.x
Other Linux
: Normal normal
: ---
Assigned To: Debarshi Ray
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2016-07-08 20:58 UTC by Armin K.
Modified: 2018-09-21 18:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Armin K. 2016-07-08 20:58:25 UTC
When copying large amount of files from Google Drive to my laptop, I received "not authenticated" error after transfering the files for some time. It appears that when not navigating through directories or refreshing the file list, gvfs-google deauthenticates current user and you have to at least refresh (hit F5) file list for the client to authenticate again and file transfer to continue.
Comment 1 Debarshi Ray 2016-07-09 12:10:45 UTC
Was your Google account marked as "needs attention" in Settings -> Online Accounts when/after this happened?
Comment 2 Armin K. 2016-07-10 11:23:57 UTC
I don't see such setting, so I'm guessing no, unless it's a default to yes.
Comment 3 Armin K. 2016-10-30 15:03:34 UTC
Still present with the latest GNOME 3.22 components.
Comment 4 Ondrej Holy 2016-11-01 15:51:04 UTC
Hmm, this is rather libgdata bug. It should call gdata_authorizer_refresh_authorization in such case, but it is not called for some reason...

What do you mean with copying? Do you mean uploading to drive, downloading from drive, or copying inside the drive?
Comment 5 Armin K. 2016-11-03 11:46:52 UTC
(In reply to Ondrej Holy from comment #4)
> What do you mean with copying? Do you mean uploading to drive, downloading
> from drive, or copying inside the drive?

In this case, I was uploading some pictures to the drive. After about half a hour (there were a lot of HD pictures), upload stopped and the error above appeared.

Sadly, now I can't even initiate an upload to the drive. It stays at "0 bytes" forever.
Comment 6 Ondrej Holy 2016-11-08 13:05:27 UTC
I saw the following recently, maybe it might be related (or might be another issue)...

$ gvfs-mount google-drive://ondrej.holy@gmail.com
Error mounting location: Permission denied

The debug log contains the following:

** (process:19037): WARNING **: Authentication required: {
 "error": {
  "errors": [
   {
    "domain": "usageLimits",
    "reason": "dailyLimitExceededUnreg",
    "message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup.",
    "extendedHelp": "https://code.google.com/apis/console"
   }
  ],
  "code": 403,
  "message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup."
 }
}

The following mount operation finished correctly...
Comment 7 Michael Terry 2017-08-07 19:35:58 UTC
I hit this today.  It was easy for me to reproduce in the console:

gio list google-drive://xxx@gmail.com/subdir

That command would give a "Permission denied" error if I waited a minute between invocations. But then it would immediately work if tried again.  Every time a minute passed, it would start giving an initial permission denied error again.

I then unmounted and remounted the drive and couldn't reproduce anymore.  Now when a minute passed and I would enter the above command there would simply be a long pause before returning the expected output (presumably authenticating in the background).

So... not as helpful a report as I would hope.  Except to say that if you enter this state, it's easy to reproduce and also perhaps easy to work around.
Comment 8 GNOME Infrastructure Team 2018-09-21 18:00:23 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/284.