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 627698 - MTP device cannot be safely used in banshee with the gphoto backend enabled
MTP device cannot be safely used in banshee with the gphoto backend enabled
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: gphoto backend
1.6.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
: 627770 642320 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-08-23 09:21 UTC by Alan McGovern
Modified: 2018-09-21 17:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alan McGovern 2010-08-23 09:21:43 UTC 
For more detailed history on the bug you should read this report:

https://bugzilla.novell.com/show_bug.cgi?id=614657

The short of it is this: When an MTP device (for example a creative Zen mp3 player) is attached, the gphoto backend will automount it as a PTP device. Unfortunately if banshee is running, banshee will also attempt to mount the device, but as an MTP device using libmtp so that it can be used as a media device.

However there's no safe way to unmount the gvfs volume in order to allow banshee to access the device via libmtp. If I just call Unmount on the volume automatically in banshee I typically end up with an mp3 player which cannot be mounted by gphoto or libmtp until I detach and reattach it.

Let me know if any more information is required
Comment 1 Alan McGovern 2010-09-07 09:29:53 UTC 
*** Bug 627770 has been marked as a duplicate of this bug. ***
Comment 2 Coudy 2010-09-16 10:42:56 UTC 
I can confirm this behavior too.
Comment 3 Hubert Figuiere (:hub) 2011-01-29 09:35:48 UTC 
Isn't that a dupe for Bug 610261 ? Exactly the same problem where gvfs holds the device lock.
Comment 4 David Nielsen 2011-11-04 18:44:36 UTC 
*** Bug 642320 has been marked as a duplicate of this bug. ***
Comment 5 GNOME Infrastructure Team 2018-09-21 17:06:16 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/157.