Possibly, but I also notice that the gio backend doesn't implement
_retry_cleanup(). Since re-running the same duplicity command can
continue successfully without needing to re-start goa-daemon, I suspect
there's something that could be done there to re-authenticate the
connection.
Unfortunately,
The bit about a possibly locked file can safely be ignored. For whatever
reason, the PDF in question had mode 260.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1747646
Title:
The same error happens with Duplicity on the command line, but it sucks
less because resuming works.
$ duplicity --exclude=/home//{.cache,kolab,box.iu,Download/releases}
--encrypt-key /home//
gio+google-drive://@gmail.com/
Local and Remote metadata are synchronized, no sync needed.
Last full
Actually, slightly different. Probably not meaningfully so, but here it
is just in case:
Giving up after 5 attempts. Error: Authentication required: {
"error": {
"errors": [
{
"domain": "global",
"reason": "authError",
"message": "Invalid Credentials",
"locationType":
I'm seeing exactly the same thing today on Fedora 29. It works fine on a
new laptop with very little to back up, but a few gigs in to backing up
my desktop I get the same error reported by the last two commenters.
--
You received this bug notification because you are a member of Desktop
5 matches
Mail list logo
