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 545695 - gphoto2 backend is causing nautilus to mount any new volume twice
gphoto2 backend is causing nautilus to mount any new volume twice
Status: RESOLVED FIXED
Product: gvfs
Classification: Core
Component: gphoto backend
0.99.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2008-07-31 14:24 UTC by Frederic Crozat
Modified: 2009-08-06 00:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Frederic Crozat 2008-07-31 14:24:52 UTC
with gvfs 0.99.3, when gphoto2 support is enabled, inserting a CD or plugging any kind of storage media is causing nautilus to try to mount the volume twice, with two error popups :

-DBus error org.gtk.Private.RemoteVolumeMonitor.NotFound: The given volume was not found
-unable to mount "foobar"

Disabling gphoto2 backend fixes this issue.
Comment 1 David Zeuthen (not reading bugmail) 2008-07-31 15:57:38 UTC
Fixed in trunk already; relevant diff includes these additions

http://svn.gnome.org/viewvc/gvfs/trunk/monitor/proxy/gproxyvolumemonitor.c?annotate=1845#l443
http://svn.gnome.org/viewvc/gvfs/trunk/monitor/proxy/gvfsproxyvolumemonitordaemon.c?r1=1842&r2=1845

The problem was that we processed signals from _every_ remote volume monitor; including the dbus name of the remote volume monitor and keying off that fixed it.

Disabling the gphoto2 backend just means there's only one remote volume monitor so the bug became moot.
Comment 2 Sean Cleary 2009-08-06 00:11:53 UTC
I found this error:
DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered
on 3 lines, when trying to mount a winxp share.

I tried to disable the gvfs and or gphoto backends. The list of things that woujld be disconnected/removed included the file system and the desktop. 

I do not think this bug is totally dead, and removing the filesystem does not look like a workaround to me. 

I am using 9.04. And I am having trouble to see the shared folders and drives on the winxp system. System connections: 'Gamer', the ubuntu machine, the linksys router (via cables), the winxp machine SEANSLAPTOP. I really would like a ready for prime time OS, but one that does not have a simple way to link, and whose helpful people can not get step by step instructions right is frustrating.

Noob,
Sean