Bug#752466: gvfs-backends: conflict between mtp and gphoto2 gvfs backends resulting in corrupted copied data
Miguel Telleria de Esteban
miguel at mtelleria.com
Mon Jun 23 18:09:20 UTC 2014
Package: gvfs-backends
Version: 1.20.2-1nomtp2
Severity: normal
Tags: upstream patch
Dear Maintainer,
Copying data from two different USB MTP devices[*] didn't work,
receiving the corrupted files in the local computer.
Further investigation, rebuilding gvfs without libmtp (see patch) and
trying other MTP library (go-mtpfs) improved the situation but still
got some corruption in the local copy.
Just by chance I rebooted the computer and then devices were visible
and transfer worked smoothly. I realised, to my surprise, that it
was the gphoto2 backend who was handling the transfers even though the
devices were clearly in MTP mode.
Looking at gphoto2 webpage shows that they have recently added MTP
support to their existing and well known PTP features.
So it may be time to drop out separate mtp handling altogether with
recent versions of gphoto2.
For info, my version of libgphoto2 is:
ii libgphoto2-6:amd64 2.5.4-1 amd64
The patch
---------
The patch I provide disables gvfs-mtp from the configure and install
phases. However an annoying window of "unable to handle device" is
still displayed whenever the MTP device is connected. This warning
can be safely ignored.
This is a coarse but good-enough approach for me. A better option
might be checking if gphoto2 is handling the mount before launching
the mtp backend, but this should be an upstream issue that goes beyond
my capabilities.
[*] Two Android4 phones: ZTE KisPro and Moto-G
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gvfs-backends depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.20.0-2
ii gvfs 1.20.2-1nomtp2
ii gvfs-common 1.20.2-1nomtp2
ii gvfs-daemons 1.20.2-1nomtp2
ii gvfs-libs 1.20.2-1nomtp2
ii libarchive13 3.1.2-8
ii libatk1.0-0 2.12.0-1
ii libavahi-client3 0.6.31-4
ii libavahi-common3 0.6.31-4
ii libavahi-glib1 0.6.31-4
ii libbluetooth3 4.101-4.1
ii libbluray1 2:0.6.0-dmo2
ii libc6 2.18-7
ii libcairo-gobject2 1.12.16-2
ii libcairo2 1.12.16-2
ii libcdio-cdda1 0.83-4.1
ii libcdio-paranoia1 0.83-4.1
ii libcdio13 0.83-4.1
ii libdbus-1-3 1.8.2-1
ii libdbus-glib-1-2 0.102-1
ii libexif12 0.6.21-1
ii libexpat1 2.1.0-5
ii libgcrypt11 1.5.3-4
ii libgdk-pixbuf2.0-0 2.30.7-1
ii libglib2.0-0 2.40.0-3
ii libgoa-1.0-0b 3.12.2-1
ii libgphoto2-6 2.5.4-1
ii libgphoto2-port10 2.5.4-1
ii libgtk-3-0 3.12.2-1
ii libgudev-1.0-0 204-10
ii libimobiledevice4 1.1.6+dfsg-2
ii libpango-1.0-0 1.36.3-1
ii libpangocairo-1.0-0 1.36.3-1
ii libplist2 1.11-3
ii libsecret-1-0 0.18-1
ii libsmbclient 2:4.1.8+dfsg-1
ii libsoup2.4-1 2.46.0-2
ii libxml2 2.9.1+dfsg1-3
ii psmisc 22.21-2
Versions of packages gvfs-backends recommends:
ii gnome-keyring 3.12.0-2
Versions of packages gvfs-backends suggests:
ii obex-data-server 0.4.5-1+b3
ii samba-common 2:4.1.8+dfsg-1
-- no debconf information
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Disabling-mtp-backend-since-it-conflicts-with-gphoto.patch
Type: text/x-diff
Size: 1279 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20140623/3cd368c5/attachment.patch>
More information about the pkg-gnome-maintainers
mailing list