Bug 925919

Summary: [abrt] duplicity-0.6.18-2.fc18: giobackend.py:85:done_with_mount:GError: Message did not receive a reply (timeout by message bus)
Product: [Fedora] Fedora Reporter: Michael Catanzaro <mcatanzaro>
Component: duplicityAssignee: Rahul Sundaram <metherid>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: redhat-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:4c37cce957a8fdbdf346d6d9717d85dbd16d7b81
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-27 22:49:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description Michael Catanzaro 2013-03-23 01:17:09 UTC
Description of problem:
1) DejaDup began to do an automatic backup to an sftp location. My laptop fans began to run loudly (normal during backups).
2) The location was unavailable, so I clicked "Skip Backup" on the notification.
3) About 15-20s later my laptop was still working too hard, so I suspected that the "skip backup" button hadn't worked properly.
4) I close two gvfs processes in System Monitor. Both processes were reporting 90-100% CPU usage. I would have expected these processes to have been stopped when I clicked "skip backup".
5) abrt brings up this complaint and DejaDup displays an error screen saying it failed to connect to the destination. (Unfortuantely I failed to screenshot the error message, sorry.)

Version-Release number of selected component:
duplicity-0.6.18-2.fc18

Additional info:
cmdline:        /usr/bin/python /usr/bin/duplicity cleanup --force sftp://msc8cc.mst.edu/nethome/users/msc8cc/DejaDup --gio --no-encryption --verbosity=9 --gpg-options=--no-use-agent --archive-dir=/home/michael/.cache/deja-dup --log-fd=14
core_backtrace: ebe56dff7d848482504079c2ce988108621145fe 0x55 done_with_mount /usr/lib64/python2.7/site-packages/duplicity/backends/giobackend.py -
executable:     /usr/bin/duplicity
kernel:         3.8.2-206.fc18.x86_64
uid:            1000

Truncated backtrace:
giobackend.py:85:done_with_mount:GError: Message did not receive a reply (timeout by message bus)

Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/duplicity/backends/giobackend.py", line 85, in done_with_mount
    fileobj.mount_enclosing_volume_finish(result)
GError: Message did not receive a reply (timeout by message bus)

Local variables in innermost frame:
fileobj: <__main__.GDaemonFile at 0x11489b0: sftp://msc8cc.mst.edu/nethome/users/msc8cc/DejaDup>
self: <duplicity.backends.giobackend.GIOBackend instance at 0x114e950>
result: <gio.SimpleAsyncResult object at 0x1148a50 (GSimpleAsyncResult at 0x7f2004003740)>
loop: <glib.MainLoop object at 0x7f20181ceb50>

Comment 1 Michael Catanzaro 2013-03-23 01:17:12 UTC
Created attachment 714876 [details]
File: backtrace

Comment 2 Michael Catanzaro 2013-03-23 01:17:13 UTC
Created attachment 714877 [details]
File: environ

Comment 3 Fedora End Of Life 2013-12-21 12:24:31 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora Admin XMLRPC Client 2013-12-27 21:12:16 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.