This bug was fixed in the package deja-dup - 42.2-1ubuntu1
---
deja-dup (42.2-1ubuntu1) groovy; urgency=medium
* Resynchronize on Debian, remaining change
* debian/control.in, debian/rules:
- Suggests python3-pydrive, ideally that would be a recommends but
the package
** Changed in: deja-dup
Status: Incomplete => Fix Released
--
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/1761216
Title:
Backup fails if backup destination is not mounted
Yes, since 20.04, I have not had the problem, but I thought it was due
to using a linux server and smb which solved the problem.
The original problem was localized to my desktop machine and a local
drive, which would fail after bootup because the dedicated backup
drrive/partition was not
The upstream commit seems to be https://gitlab.gnome.org/World/deja-
dup/-/commit/e349a1c7 , if it fixes the issue we should probably
backport that one to the LTS
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
OK, then yah, I suspect the change I recently made should fix this:
deja-dup now checks fstab and mounts the target location before a backup
starts.
You should be able to test it by installing the latest edge snap:
snap install deja-dup --classic --edge
--
You received this bug notification
Yes, it is listed in fstab and yes, I entered the path as a local
storage device.
All drives are SSD's connected to the computer's internal SSD ports and
seen as local. The server is running XIGMANAS with SMB shares for each
of the SSD's. I am not running SAMBA server.
The local OS is Unbuntu
How is this other drive configured? Is it an entry in fstab? And you
were entering its path as a Local Folder storage location?
If so, we didn't previously do anything special about mounting fstab
entries for you. But I just added some code to try that.
Could you give a beta build a try and see
I have not found the bug you describe to be true.
Work-a-round. If you mount the backup destination before the scheduled
backup begins, everything is fine and the backup runs without error.
If you don't mount the backup destination before the scheduled backup,
it will fail, with destination
Hello everyone.
This is related to bug #804170 but goes even further. instead of
preventing to run backups only if the "hard-to-detect sometimes-
directories" are available it requests to make them available.
This would be a new feature.
** Also affects: deja-dup
Importance: Undecided
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: deja-dup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
** Package changed: ubuntu => deja-dup (Ubuntu)
--
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/1761216
Title:
Backup fails if backup destination is not mounted
Status in deja-dup
11 matches
Mail list logo
