I think this is a report against Deja Dup - that string is an error
message we give if 'duplicity --version' doesn't actually give us a
parsable version string.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Interesting… that usually means that duplicity crashed on us or had some
other odd error when we asked it for its version.
But when you do it on the terminal, it’s fine…
Are you using the standard Ubuntu distro version of deja Dup (vs flatpak
or snap releases?)
--
You received this bug
Hmm, that's odd. That means... maybe there's a problem decrypting some
of your metadata, but you do have an unencrypted version of that
metadata in duplicity cache folders...?
But if you can restore stuff, that likely means you can decrypt the
latest actual data...
If you run "DEJA_DUP_DEBUG=1
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933717
Title:
Backup messages in wrong language
To manage notifications
** Changed in: deja-dup (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778638
Title:
duplicity stuck in splice() call on Bionic
To manage
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355
** Bug watch added: Debian Bug tracker #1011355
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355
** Also affects: deja-dup (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011355
Importance: Unknown
Looks like Debian stable is using 42.7 right now - should I file a bug
on the Debian side to track that too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973816
Title:
Deja Dup's Google support
OK, I've made a little wiki page about this issue for distro maintainers
(no real new information, but it does have links to patches at the
bottom). The patches should cover all affected versions that Ubuntu
supports (40.7, 42.8, and 42.9).
https://wiki.gnome.org/Apps/DejaDup/GoogleAuthChange2022
Public bug reported:
Hello! I'm the maintainer of Deja Dup. I was recently made aware that
Google is removing an oauth workflow that Deja Dup uses, in September.
Here's their blog post about it:
https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html
Here's the upstream bug
Deja Dup could maybe be smarter in the specific case of SMB mounts and
only try to mount the root folder...
If you switch your settings from:
Network Location: smb://1.2.3.4/backup/UbuntuBackup
Folder: MyMachineBackup
to:
Network Location: smb://1.2.3.4/backup
Folder:
I think that /tmp filename is a file that duplicity proceeds to throw
away. It copies files there, tries to unpack them, then cleans up after
itself (regardless of success). So that error message would be a lot
more useful if it indicated what the actual source file it had copied
from the storage
I tested this and it worked!
- Made an initial backup, not saving password.
- Backed up again, changing the password.
With the old version, I got an error at "verify the backup" step. But
the backup files did end up being written with the wrong password.
With the new version, it did not accept
It escaped my attention at the time, but Ubuntu 18.04 released with both
a version of duplicity that shows the new incremental-backups-also-have-
this-issue behavior (see my comment 22) and a release of deja-dup that
wasn't yet fixed to avoid it.
Which means that deja-dup in Ubuntu 18.04 is still
*** This bug is a duplicate of bug 1933717 ***
https://bugs.launchpad.net/bugs/1933717
Hello and thank you for the report! Oddly enough, this is an Ubuntu
translation issue, where some German ended up sneaking into the English
translation. It’s fixed for the next release, but I guess they
Interesting. Jesse, that might be due to
https://gitlab.com/duplicity/duplicity/-/merge_requests/31 which
rejiggered how `--exclude-if-present` checks files in order to avoid a
fatal error that occurred in some edge cases. That change was released
in 0.8.17.
Maybe we would need a smarter fix to
This looks to be an Ubuntu translation error. The current package of
language-pack-gnome-en-base has some German phrases in its en_GB
translations for deja-dup!
Looks like they were fixed in May in the Ubuntu translation sources:
This looks like a transient error, some issue with python3 on your
install?
But regardless, more recent releases of Ubuntu have deja-dup depend
directly on duplicity and gvfs-backends
** Project changed: deja-dup => deja-dup (Ubuntu)
** Changed in: deja-dup (Ubuntu)
Status: New => Fix
Sorry you were hit by this issue! But good news is that a fix is
available. It was caused by an interaction between Deja Dup and
duplicity when a single quote was followed by a space.
This was fixed upstream in duplicity 0.8.17 (and worked around in deja-
dup 42.5). Both those fixes are in Ubuntu
** Changed in: deja-dup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915161
Title:
deja dup won't restore a folder where name contains apostrophe and
Robin, do you mind filing a new bug? Will be easier for me to dig into
what's not working for you, rather than adding on to this 2013 issue.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think the English word used is Utilities
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873238
Title:
Deja-dup icon is missing only runs from terminal
To manage notifications about this bug go
Oh that’s interesting yes. I’ll have to see how to get the quota info
from gvfs and apply it to our calculations. Thank you for the report!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906304
Oh and I should have mentioned workarounds:
- give everyone execute permission on the offending folder
- install the snap version of duplicity
- install the snap (or flatpak) version of deja-dup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
(Any one of those should work by itself)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905170
Title:
Impossible to create a full backup due to permission error on
/home/lost+found folder
To
This is a bug in a possible interaction between Deja Dup >= 42.1 and
Duplicity < 0.8.16.
Which means as of this writing it definitely affects 20.10, and may
affect 21.04 if Duplicity doesn't get bumped before release.
This was fixed in Duplicity by the following patch:
Were you using the snap package? There was a bug briefly in duplicity
that would have caused this error, but it is fixed now. Do you still see
this?
I don’t believe the bug was ever present in Ubuntu 20.04 itself.
** Changed in: deja-dup (Ubuntu)
Status: New => Incomplete
--
You
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027514
Title:
Restore dialog becomes too huge when restoring too many files
To
** Changed in: deja-dup (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953194
Title:
deja-dup attempts to backup "lost+found"
To manage
Latest versions show a notification that will bring the dialog open as
needed. (Or starting the app from the application launcher will also
show it.)
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
That UI has been redesigned and is a lot better now.
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1281675
Title:
The scheduling
Nikita, your issue actually looks a lot like something fixed in duplicity
0.8.16:
https://gitlab.com/duplicity/duplicity/-/commit/f6809e8a4e09b70138a0902434d8c88d3c4c8ccb
Try installing the snap version of deja-dup or duplicity, both of which
have the fix for this.
--
You received this bug
Yeah an sru should be fine — no dramatic changes in there, but plenty of
nice fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901340
Title:
Backup doesn't automatically start when drive is
Ah, OK. Maybe the previous problem with the snap was because the old
session monitor was still active? Odd.
But glad it worked now!
So yeah, looks like the fixes in 42.3 work for your case, and it's
possible the patches around encrypted & removable drives from 42.3 and
42.4 should be backported
Version 42.3 did fix an error with scheduled backups to encrypted
drives! I suspect that might be what you're hitting? Can you try the
snap and see if that fixes things? Might want to make a manual backup
first just to confirm everything is working.
snap install deja-dup --classic
sudo apt remove
Huh... That first message, I'm not sure I've seen before.
This might be a dup of https://bugs.launchpad.net/duplicity/+bug/1828869
?
You could test that by installing the snap version of duplicity and
uninstalling the distro version:
snap install duplicity --classic
sudo apt remove duplicity
I have some further details about this bug! Not super positive, but
still.
First, I'm going to mark bug #676767 a duplicate of this. That's a
slightly older bug with the same symptom, and a workaround (of deleting
the cache) that doesn't seem to work in all cases. But ultimately, it's
Public bug reported:
httplib2 0.16 changed how 308 redirects are handled. This broke some
existing python packages that weren't expecting that change when talking
to Google servers that use 308 redirects. Like PyDrive.
= Reproducing =
Reproducing is a little difficult. I'm not entirely sure
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953194
Title:
deja-dup attempts to backup "lost+found"
To manage notifications
*** This bug is a duplicate of bug 1360734 ***
https://bugs.launchpad.net/bugs/1360734
Hmm, I'm sorry this is happening! I've seen reports of duplicity giving
this error before. I'll mark this bug as a duplicate of one of them.
Practically, until this gets fixed, I'd say try deleting
I think this should be fixed with 42.2, which now looks at /etc/fatal
and mounts the target drive if necessary.
** Changed in: deja-dup
Status: New => Fix Released
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
I’m moving all the suggestions for more advanced include/exclude support
to a single ticket on Gitlab
https://gitlab.gnome.org/World/deja-dup/-/issues/112
** Bug watch added: gitlab.gnome.org/World/deja-dup/-/issues #112
https://gitlab.gnome.org/World/deja-dup/-/issues/112
** Changed in:
** Changed in: deja-dup (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814238
Title:
deja-dup saves passphrase in /tmp
To manage notifications
** Changed in: deja-dup (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815056
Title:
deja-dup is asking for the admin password
To manage
** Changed in: deja-dup
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761216
Title:
Backup fails if backup destination is not mounted
To manage
A browse and restore interface was released with 42.0.
** Changed in: deja-dup
Status: Confirmed => Fix Released
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
OK, I *finally* got around to fixing this.
Fix should be released with version 42.3.
https://gitlab.gnome.org/World/deja-dup/-/commit/791acc6fdbe42d6851ecf64ad29ee41ce6ed0d58
** Changed in: deja-dup
Status: Confirmed => Fix Committed
--
You received this bug notification because you are
Is there an error message that is visible or the window just never
appears?
** Project changed: deja-dup => deja-dup (Ubuntu)
** Changed in: deja-dup (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Project changed: deja-dup => 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/1866620
Title:
deja-dup-monitor startup invalid path
To manage notifications about this bug go to:
The flatpak and snap releases of Deja Dup now include this duplicity
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268182
Title:
Computer name changed
To manage notifications about this bug
To Vej's points:
> Fix the problem, that accepting the changed hostname is not persistent
It *should* already be persistent. In the sense that each time duplicity
backs up, it writes the current hostname to the manifest and checks
against that going forward.
I think it just looks like it's not
Huh, that's odd. Looks like a permission error when downloading a
metadata file from the SMB server. I'm not sure if it couldn't read or
couldn't write, from that error message.
But I guess if it's transient... it's all good. If you see this again,
please re-open or file a new ticket.
Thanks for
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
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'm going to close this ticket, as it should be solved in Ubuntu 20.04
and on and it was never really something that deja-dup itself could fix.
The workaround of mounting via fstab should work for folks stuck on
Ubuntu 18.04 and earlier though.
** Changed in: deja-dup
Status: Confirmed =>
--auto is how we launch the background backups.
I think this bug has been fixed in recent releases by a more concerted
effort to keep the progress windows on top of the rest of the interface.
But if folks can still reproduce using a recent Deja Dup (40+ I’d say),
please reopen and I can try to
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815056
Title:
deja-dup is asking for the admin password
To manage notifications
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814238
Title:
deja-dup saves passphrase in /tmp
To manage notifications about
** Changed in: deja-dup
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814238
Title:
deja-dup saves passphrase in /tmp
To manage notifications about this
** Also affects: deja-dup
Importance: Undecided
Status: New
** Changed in: deja-dup
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815056
Title:
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863506
Title:
mate-session[1159]: WARNING: Could not parse desktop file
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
I'm proposing this bug for an SRU to focal via an update to deja-dup
40.7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883254
Title:
No google authorization when doing a clean restore
To manage
I believe this is fixed in 20.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876057
Title:
deja-dup-monitor running even if backups are disabled
To manage notifications about this bug go to:
Hmm. Version 1.1 is definitely a valid version:
https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#idm45070351179248
But specifying a version is optional altogether, and I don't think it's
helpful in any particular way. I can just drop the version numbers.
Oh I see this has a task for MATE.
** Also affects: deja-dup
Importance: Undecided
Status: New
** Changed in: deja-dup
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tim, your issue in comment 26 is confusing to me. It looks like it's
caused by my patch in comment 6?
Specifically, it looks like subprocess.Popen returns a unicode string as
stdout for you. I can't reproduce locally, in either python2.7 or
python3.7:
>>> import subprocess
>>>
Ahh... yes. Deja Dup just checks to see if anything is outside your
home folder and then prompts if so.
Looks like the /tmp/ directory for CACHE_HOME is confusing it (because
we do backup a little canary file we put in your home cache which we use
to verify that the backup is functional and can
I think this patch should fix the duplicity error you're seeing.
But deja-dup doesn't work well under root so much - it'll ask for root
permissions as appropriate when restoring anyway?
** Patch added: "decode.patch"
(Oh, sorry, I thought this was a deja-dup bug.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842124
Title:
Making Backup HD NTFS
To manage notifications about this bug go to:
Though it does look like you got bit by a unicode issue that should be
fixed in the snap version of deja-dup. Try installing the latest version
this way:
snap install deja-dup --classic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1852069 ***
https://bugs.launchpad.net/bugs/1852069
I’m glad the pip thing works, and if you have no problems that way, no
need to change.
But if you do see any issues, try the snap version of deja-dup, just
because I also fixed a separate issue with
For our own passphrases, etc, we just use libsecrets, which is not tied
to a specific desktop.
But for network server access, we do rely on gvfs, which is not likely
to change. And that might have some wonkiness in other desktop envs
(though hopefully that’s better in 2019 than in past, assuming
This looks like some issue with the old deja-dup-backend-gvfs package.
That’s no longer a separate package.
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The error “ install new version: Structure needs cleaning” seems like
some ext4 error, from a quick internet search. Maybe from copying data
from inside Windows? I’m going to close as not a Deja Dup bug.
** Changed in: deja-dup (Ubuntu)
Status: New => Invalid
--
You received this bug
Has anyone seen this in recent years?
** Changed in: deja-dup (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1019293
Title:
"gpg: can't handle text lines
The brainstorm link is dead now and we don’t have any code left for
inhibiting a shutdown (Deja Dup will just resume next time). I’m going
to close, but please open a new bug if you’re still experiencing a bug
around this.
** Changed in: deja-dup (Ubuntu)
Status: New => Invalid
--
You
I don’t think there’s enough information here for me to guess what our
2012 code was trying to do. I’m going to close this, but please reopen
if you still see it.
** Changed in: deja-dup (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
We use a notification for that these days
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942743
Title:
add an update-manager like
Closing this because we took out the memory cap.
** Changed in: deja-dup
Status: Confirmed => Fix Released
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Has this been seen on 18.04+?
** Changed in: deja-dup (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740238
Title:
'operation already pending' error
Should be fixed in 19.10 or by using the snap.
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737535
Title:
Falha ao executar
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940782
Title:
deja-dup crashed with SIGSEGV in
This was fixed in 39.1 (and Ubuntu 19.10)
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450429
Title:
Backups
Closing this, as Deja Dup no longer links with WebKit
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: webkit2gtk (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712757
Title:
/usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-
I’m going to assume this is fixed on recent releases? At the least,
compiz isn’t used by default anymore.
If you still see this, please reopen.
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
That UI option is gone now.
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233799
Title:
"Skip Backup" didn't skip the backup.
Should be fixed in 19.10
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766258
Title:
Duplicity fails to install
To manage
Should be fixed in 19.10 by having Deja Dup depend on duplicity again.
Or you could use the snap version.
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Alright, the switch to our own keys seems to have fixed this. I’ll close
the remaining tasks on this bug.
Ubuntu 19.10 uses the new key but has a separate issue with Google
Drive: bug 1852069
** Changed in: deja-dup (Ubuntu)
Status: Triaged => Fix Released
** Changed in: duplicity
Should be fixed in 19.10 by hard depending on the packages.
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831368
Title:
The missing dependency issue should be fixed in 19.10
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810665
Title:
Ubuntu 19.04
*** This bug is a duplicate of bug 1852069 ***
https://bugs.launchpad.net/bugs/1852069
** This bug has been marked a duplicate of bug 1852069
Failed to backup to google drive on ubuntu 19.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is fixed in 19.10 by using the python3 version of duplicity.
You can get the fix on 18.04 by using the snap version of Deja Dup:
snap install deja-dup --classic
** Project changed: deja-dup => deja-dup (Ubuntu)
** Changed in: deja-dup (Ubuntu)
Status: New => Fix Released
--
You
This is a packaging bug in Debian & Ubuntu only. It's not an upstream
deja-dup issue.
They have not yet packaged pydrive, which deja-dup and duplicity need to
talk to Google Drive (we can no longer use the previous method of
talking to Google Drive - which was through gvfs).
To work around this
** Also affects: deja-dup
Importance: Undecided
Status: New
** Changed in: deja-dup
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852069
Title:
Failed to
Yes correct - ideally Ubuntu is able to package up pydrive. But in the
meantime, you can use the snap which should work.
Instructions here: https://wiki.gnome.org/Apps/DejaDup/Download
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Commenters that have errors which talk about Unicode or ascii or codecs:
Is be interested to hear if trying the latest Deja Dup snap (which
bundles duplicity 0.8 which claims to fix that) helps:
snap install deja-dup --classic --candidate
The original OP report was actually for a different issue
To add on to Aaron's comment, if you are coming here because you hit
this bug while using deja-dup, you can install a version of deja-dup
that bundles in duplicity 0.8.0, which has the fix:
snap install deja-dup --classic --candidate
--
You received this bug notification because you are a
** No longer affects: deja-dup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767122
Title:
duplicity Errors 199 at end backup
To manage notifications about this bug go to:
1 - 100 of 8591 matches
Mail list logo
