** Changed in: deja-dup (Ubuntu)
Status: Triaged => 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/1778638
Title:
duplicity stuck in splice() call on Bionic
** Changed in: duplicity
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/1778638
Title:
duplicity stuck in splice() call on Bionic
Status
For what it is worth, Duplicity 0.8.11.1612-1 on Ubuntu 20.10 works
fine.
--
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/1778638
Title:
duplicity stuck in splice() call on Bionic
** Changed in: duplicity
Importance: Medium => Undecided
--
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/1778638
Title:
duplicity stuck in splice() call on Bionic
Status in
** Changed in: duplicity
Status: Confirmed => Incomplete
--
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/1778638
Title:
duplicity stuck in splice() call on Bionic
Status in
** Changed in: deja-dup (Ubuntu)
Importance: Undecided => High
** Changed in: deja-dup (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
** Changed in: duplicity
Status: New => Confirmed
--
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/1778638
Title:
duplicity stuck in splice() call on Bionic
Status in
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.
It looks like this is not just me who is having this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1582654
** Bug watch added: Red Hat Bugzilla #1582654
https://bugzilla.redhat.com/show_bug.cgi?id=1582654
--
You received this bug notification because you are a member of Desktop
Further debugging with `strace` shows it literally creates the pipe
right before it tries to write into it:
write(1, "Registering (mktemp) temporary f"..., 82) = 82
write(13, "DEBUG 1\n. Registering (mktemp) t"..., 93) = 93
lstat("/tmp/duplicity-iMtvLG-tempdir/mktemp-Z8PNlG-2", 0x7ffd210b6cc0) =
I have even tried without encryption. The `--no-use-agent` option is
there even:
DUPLICITY: . Args: /usr/bin/duplicity
--exclude=/var/backups/wilx/backup.amber2
--exclude=/home/wilx/snap/*/*/.cache --include=/home/wilx/.cache/deja-
dup/metadata --exclude=/home/wilx/Private
Have you tried
https://bugs.launchpad.net/duplicity/+bug/1778638/comments/6 yet??
Please let me know if it worked.
** Changed in: duplicity
Milestone: 0.7.18 => None
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
** Changed in: duplicity
Is that true? Haven't I set up the pass phrase during initial backup in
Deja Dup? It does not make sense for automatic backup to as for
passhrase each time it runs. Is this Deja Dup issue then?
** Also affects: deja-dup (Ubuntu)
Importance: Undecided
Status: New
--
You received this
13 matches
Mail list logo
