gio backend crashes trying to ensure_dbus
Bug #1851167 reported by
Aspen Barnes
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
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.
Versions:
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
Changed in duplicity: | |
importance: | Undecided → Medium |
milestone: | none → 0.8.07 |
status: | New → In Progress |
Changed in duplicity: | |
status: | Invalid → New |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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 - https:/ /launchpad. net/duplicity/ +download /launchpad. net/~duplicity- team/+archive/ ubuntu/ daily /launchpad. net/~duplicity- team/+archive/ ubuntu/ ppa
* Daily duplicity builds - https:/
* Stable duplicity builds - https:/
* 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".