GNOME Bugzilla – Bug 582066
Creative Zen mounts incorrectly through gvfs/gphoto/Gnome
Last modified: 2009-05-21 19:46:29 UTC
Please describe the problem: When Zen (Vision M) is plugged into the system, the device identifies briefly and then is mounted and docked by gvfs. At this point, Gnomad2, Rhythmbox, etc cannot use this device. If I go to the desktop and unmount it, I can use it and it works normally. Creative devices do NOT mount like Apple devices, in that they should not dock to the system, rather they should stay on the bus and be available for the programs that use them to mount/unmount as needed. While the workaround of unmounting from the desktop makes the device usable, this is new behavior in the newer versions of gnome/gvfs/gphoto. The gphoto developer says that it is an issue with gvfs, and possibly a distro error. Using Ubuntu Jaunty Steps to reproduce: 1.Plug in my Zen to USB 2. Unplug and plug in again 3. Actual results: It 'docks' to the system and is unavailable to the programs that use it. Expected results: It should ID itself on the USB bus and then stay in an unmounted state Does this happen every time? YES Other information:
No, it's supposed to work this way so more than one app can use the device. Apps like Rhythmbbox need to either unmount the device or use the GIO library to access it. Closing as NOTABUG.
Is this then a gnome change, which is not yet incorporated into gnomad2, rhythmbox, etc...? Do they know that they need to change the behavior due to gvfs?
(In reply to comment #2) > Is this then a gnome change, which is not yet incorporated into gnomad2, > rhythmbox, etc...? Do they know that they need to change the behavior due to > gvfs? Yes, this has been mentioned multiple times in multiple places.
Who is actually using this backend? Is it worth the confusion? Using the gphoto backend instead of libgphoto2 gains you nothing, and you lose important capabilities like extracting a thumbnail before transferring the whole file. It's confusing users and annoying developers. The gphoto developers don't like it either [1]. I don't suppose you would consider removing this backend? - Mike [1] http://sourceforge.net/mailarchive/message.php?msg_name=4A15A4FD.3050501%40figuiere.net
(In reply to comment #4) > Who is actually using this backend? The file manager and this lots of people who like to access their photos / files that way. > and you lose important > capabilities like extracting a thumbnail before transferring the whole file. Not true. The functionality to extract the thumbnail was added in Oct 2008. It's actually very fast, see the gvfs-list archives for details. > It's confusing users and annoying developers. The gphoto developers don't like > it either [1]. > > I don't suppose you would consider removing this backend? Listen, we are not going to remove this backend just because it's inconvenient for some developers/distros who are too lazy or something to a) either unmount the GIO gphoto2:// mount from the app or a launcher app (hint: 'gvfs-mount -s gphoto2' will do the trick); or b) use GIO itself to access the device Notably, if the app is using GIO then, hey, *other* GIO using apps can access the device instead of this crazy situation where you have a single app hogging the device. That is one of the main reasons this backend exists. David