Can't backup to Google Drive GSuite account

Bug #1787248 reported by Vladislav Shumkin
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Déjà Dup
Fix Released
Undecided
Unassigned

Bug Description

The folder has been created in Drive and has some 200+ files named *.vol*.difftar.gpg, so I assume initial backup was done at least partially. But subsequent backups are failing with this message:

Giving up after 5 attempts. Error: gdata-service-error-quark: Error code 500 when querying: {
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "internalError",
    "message": "Internal Error"
   }
  ],
  "code": 500,
  "message": "Internal Error"
 }
}
 (2)

And rarely failing with this message:

 Giving up after 5 attempts. Error: gdata-service-error-quark: Authentication required: {
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "authError",
    "message": "Invalid Credentials",
    "locationType": "header",
    "location": "Authorization"
   }
  ],
  "code": 401,
  "message": "Invalid Credentials"
 }
}
 (4)

My guess that it may be connected with the fact that I use corporate GSuite Drive for backup and it works somehow different in comparison with regular Google Drive.

1. lsb_release -d
Description: Ubuntu 18.04.1 LTS

2. dpkg-query -W deja-dup duplicity
deja-dup 37.1-2fakesync1
duplicity 0.7.17-0ubuntu1

3. gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic true
org.gnome.DejaDup periodic-period 1
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'goa'
org.gnome.DejaDup last-run ''
org.gnome.DejaDup nag-check ''
org.gnome.DejaDup prompt-check 'disabled'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['/home/spurlos']
org.gnome.DejaDup exclude-list ['/home/spurlos/.config/composer/cache', '/home/spurlos/snap/spotify/common/.cache/spotify/Data',
'/home/spurlos/.local/share/Trash']
org.gnome.DejaDup last-backup ''
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.Rackspace container 'spurlos-Aspire-E1-571'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'spurlos-Aspire-E1-571'
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.OpenStack container 'spurlos-Aspire-E1-571'
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS folder 'spurlos-Aspire-E1-571'
org.gnome.DejaDup.Local folder '/home/spurlos/deja-dup'
org.gnome.DejaDup.Remote uri ''
org.gnome.DejaDup.Remote folder 'spurlos-Aspire-E1-571'
org.gnome.DejaDup.Drive uuid ''
org.gnome.DejaDup.Drive icon ''
org.gnome.DejaDup.Drive folder '$HOSTNAME'
org.gnome.DejaDup.Drive name ''
org.gnome.DejaDup.GOA id 'account_1533719103_0'
org.gnome.DejaDup.GOA folder 'spurlos-Aspire-E1-571'
org.gnome.DejaDup.GOA type 'google'
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File migrated true
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File path 'file:///home/spurlos/deja-dup'
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.File relpath @ay []

4.1 internalError deja-dup.log https://pastebin.com/YALBLx0W
4.2 authError deja-dup.log https://pastebin.com/3MAPT0zW

Revision history for this message
Stephen Calnan (commerce-s) wrote :
Revision history for this message
Michael Terry (mterry) wrote :

I have prepared a new beta release that might fix this issue. The 39.x series has switched from GNOME's Google keys to our own keys. Which may aleviate some of these issues (on the presumption that part of it is that the GNOME key's quotas are being hit).

To test if the new 39.1 release helps, you can run:
snap install deja-dup --classic --beta

Or if you already had the snap installed:
snap refresh deja-dup --beta

When you next back up, you will be prompted to re-authorize deja-dup to access your Google account (with vastly diminished access than the GNOME keys, which is nice).

I will optimistically close this ticket. Please re-open and comment if the above release does not help matters.

Changed in deja-dup:
status: New → Fix Released
Revision history for this message
Vladislav Shumkin (spurlos) wrote :

I think we need Ubuntu repo release to use the fix properly and seamless. Snap package is not overriding the distro version of the executable.

spurlos@spurlos-ThinkPad-E580:~$ snap install deja-dup --classic --beta
deja-dup (beta) 39.1 from Michael Terry (mterry) installed
spurlos@spurlos-ThinkPad-E580:~$
spurlos@spurlos-ThinkPad-E580:~$ which deja-dup
/usr/bin/deja-dup
spurlos@spurlos-ThinkPad-E580:~$ deja-dup --version
deja-dup 37.1

Revision history for this message
Michael Terry (mterry) wrote :

For sure we want the fix to get into distros. But it’s currently only in a beta release.

As for the overriding - I believe that’s just because you are still in the same shell that was opened before you installed the snap. In a new shell, the snap will override I believe.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.