After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 526793 - unmount hangs with some backends
unmount hangs with some backends
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: daemon
0.2.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2008-04-07 19:12 UTC by David Zeuthen (not reading bugmail)
Modified: 2014-11-05 10:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Zeuthen (not reading bugmail) 2008-04-07 19:12:20 UTC
It's very easy to reproduce with the gphoto2 backend

 $ gvfs-mount gphoto2://[usb:001,014]
 $ gvfs-mount -u gphoto2://[usb:001,014]
 <hangs>

Sometimes it *doesn't* hang though. So maybe there's a race somewhere.

Notably this doesn't happen with the sftp backend or the cdda backend. 

I wonder if it's a gphoto2 specific problem; I looked at the source and it seems like we're doing the right thing (we only use exit(1) if the device goes away). Either way, the device gets unmounted fine and the gphoto2 mount daemon terminates. It's just that gvfs-mount hangs never getting a reply. So that's why I'm assigning this to the 'daemon' component instead of the 'gphoto2' component.
Comment 1 Matthias Clasen 2008-04-17 03:01:44 UTC
2008-04-16  Matthias Clasen  <mclasen@redhat.com>

        Bug 526793 – unmount hangs with some backends

        * daemon/gvfsbackendgphoto2.c: Set exit-on-disconnect to FALSE
        on the private dbus connection to prevent unexpected exit
        before the job is done.


This fixes the hang of the gphoto backend. Leaving this bug open to deal with the larger robustness issue that gvfsd should be  resilient against backends going away unexpectedly.
Comment 2 Ondrej Holy 2014-11-05 10:24:33 UTC
This is an old bug and this should be fixed properly now. If you still see it with current gvfs versions, please reopen with reproduction details.