gio backend crashes trying to ensure_dbus

Bug #1851167 reported by Aspen Barnes on 2019-11-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When the dbus session isn't set in the environment (which appears to happen when run via deja-dup), the call to the ensure_dbus() in the gio backend fails. This happens when using duplicity on Python 3.0+ as subprocess.Popen.communicate() returns a tuple of bytes objects rather than strings.

Duplicity: 0.8.06
Python: 3.7.5rc1
OS: Ubuntu 19.10
Targetting: local mount of SMB share

EDIT: tested on 0.8.06 as well

Aspen Barnes (linuxdaemon) wrote :
Changed in duplicity:
importance: Undecided → Medium
milestone: none → 0.8.07
status: New → In Progress

Please upgrade to the current version of duplicity, 0.8.06. This will assure that any bugs fixed since your release are available and may fix your issue.

NOTE: This applies especially to duplicity versions between 0.7.03 and 0.7.14 inclusive. There was a fix in 0.7.15 that reduced memory usage drastically, and will help with memory errors and inability to start new threads.

There are four options:

* Release tarball Install -
* Daily duplicity builds -
* Stable duplicity builds -
* Stable snap builds - “sudo snap install duplicity —classic"

NOTE: UNinstall duplicity first if it was installed via the distribution repository. For Ubuntu, that would be "sudo apt-get purge duplicity".

Changed in duplicity:
importance: Medium → Undecided
milestone: 0.8.07 → none
status: In Progress → Invalid
Changed in duplicity:
status: Invalid → New
Aspen Barnes (linuxdaemon) wrote :

This definitely is still an issue on version 0.8.06, tested by installing from the tar.

description: updated

It still works from the command-line for me on 18.04 and MacOS. Deja-dup must be doing some odd stuff.

Changed in duplicity:
importance: Undecided → Medium
milestone: none → 0.8.07
status: New → Fix Committed
Changed in duplicity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments