[Bug 1747646] Re: Authentication error with google drive [$10]

2018-12-16 Thread Vej
** Changed in: deja-dup Status: New => Triaged ** Changed in: deja-dup Importance: Undecided => High ** Changed in: deja-dup (Ubuntu) Status: Confirmed => Triaged ** Changed in: deja-dup (Ubuntu) Importance: Undecided => Medium ** Tags added: bionic ** Changed in: deja-dup

[Bug 1747646] Re: Authentication error with google drive [$10]

2018-11-15 Thread Paul White
** Package changed: ubuntu => deja-dup (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747646 Title: Authentication error with google drive [$10] To manage notifications about this bug go

[Bug 1747646] Re: Authentication error with google drive [$10]

2018-09-28 Thread Cody Hodges
Perhaps the OAuth token is expiring during long backup jobs and needs to be renewed? Not sure what it is based on because our times vary widely. https://developers.google.com/drive/api/v3/handle- errors#401_invalid_credentials This happens to me after first-time backup running for about 45

[Bug 1747646] Re: Authentication error with google drive [$10]

2018-09-10 Thread Usul_
This happens to me to. I am not using a personal google account but a corporate one. After 5 or 10 minutes I get an authentication error. I am on ubuntu 18.04 using deja-dup 37-1 and duplicity 0.7.17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1747646] Re: Authentication error with google drive [$10]

2018-07-28 Thread Johannes Choo
I would like to retract my report: my backups appear to not have completed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747646 Title: Authentication error with google drive [$10] To manage

[Bug 1747646] Re: Authentication error with google drive [$10]

2018-07-28 Thread Johannes Choo
I noticed that I encounter this error when I am connecting via a VPN service, and do not encounter this error when I am not. If the reason is that Google rejects authenticating from suspicious IPs with the kind of authentication deja-dup and GNOME's online accounts use, I don't know if the team