I had some extra time, so I released 40.7 with this fix.
https://gitlab.gnome.org/World/deja-dup/-/releases/40.7
** Changed in: deja-dup
Status: Fix Committed => Fix Released
** Also affects: deja-dup (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- I started a clean restore on a Virtual Machine without setting up a
- backup job first. The restore is from Google drive. When I click
- through it gets to the "Checking for backups" screen and just sits
- there. Eventually, I just canceled it. I think it's doing this because
- it doesn't yet have credentials to access the google drive, but also
- doesn't notice this fact or ask for them.
+ [ Impact ]
+ Users with a backup on Google Drive may be confused when trying to restore
from that backup on a fresh install.
+
+ With 40.6, they have to attempt a backup first to properly connect their
+ Google account. But there's no suggestion that that is the right path.
+
+ Instead, a restore simply hangs with no feedback.
+
+ [ Test Case ]
+ On a fresh install, open Deja Dup, click the restore button, and notice that
the progress bar never finishes.
+
+ [ Regression Possibility ]
+ The patch is pretty small, but technically does affect both restore and
backup paths.
+
+ [ Original Report ]
+ I started a clean restore on a Virtual Machine without setting up a backup
job first. The restore is from Google drive. When I click through it gets to
the "Checking for backups" screen and just sits there. Eventually, I just
canceled it. I think it's doing this because it doesn't yet have credentials to
access the google drive, but also doesn't notice this fact or ask for them.
The bug can easily be solved by first starting a backup with google
drive. Now it does notice that it needs credentials and starts that
process. If I do that first, cancel the backup and then go back to the
restore, things go better. The restore gets further along (although
there's another bug we're discussing here that might be related to the
VM).
The expected behavior for me at least is that even if you haven't set up
a backup yet, if you try to do a restore from a Google drive Deja Dup
should start the process of getting credentials to access the drive.
OS: Ubuntu 20.04
Deja-Dup: 40.6-1ubuntu2
Duplicity: 0.8.11.1612-1
** Also affects: deja-dup (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/1883254
Title:
No google authorization when doing a clean restore
Status in Déjà Dup:
Fix Released
Status in deja-dup package in Ubuntu:
New
Status in deja-dup source package in Focal:
New
Bug description:
[ Impact ]
Users with a backup on Google Drive may be confused when trying to restore
from that backup on a fresh install.
With 40.6, they have to attempt a backup first to properly connect
their Google account. But there's no suggestion that that is the right
path.
Instead, a restore simply hangs with no feedback.
[ Test Case ]
On a fresh install, open Deja Dup, click the restore button, and notice that
the progress bar never finishes.
[ Regression Possibility ]
The patch is pretty small, but technically does affect both restore and
backup paths.
[ Original Report ]
I started a clean restore on a Virtual Machine without setting up a backup
job first. The restore is from Google drive. When I click through it gets to
the "Checking for backups" screen and just sits there. Eventually, I just
canceled it. I think it's doing this because it doesn't yet have credentials to
access the google drive, but also doesn't notice this fact or ask for them.
The bug can easily be solved by first starting a backup with google
drive. Now it does notice that it needs credentials and starts that
process. If I do that first, cancel the backup and then go back to
the restore, things go better. The restore gets further along
(although there's another bug we're discussing here that might be
related to the VM).
The expected behavior for me at least is that even if you haven't set
up a backup yet, if you try to do a restore from a Google drive Deja
Dup should start the process of getting credentials to access the
drive.
OS: Ubuntu 20.04
Deja-Dup: 40.6-1ubuntu2
Duplicity: 0.8.11.1612-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1883254/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
