On Sat, 22 Dec 2012, Vincent Lefevre wrote:
> With mtpfs 1.1-2 and my Galaxy Note II (N7100):
>
> # mtpfs -o allow_other /media/mtp
> Listing raw device(s)
> Device 0 (VID=04e8 and PID=6860) is a Samsung GT
> P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y.
> Found 1 device(s):
> Samsung: GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab
> 7.7/10.1/S2/S3/Nexus/Note/Y (04e8:6860) @ bus 8, dev 8
> Attempting to connect device
> PTP_ERROR_IO: failed to open session, trying again after resetting USB
> interface
> LIBMTP libusb: Attempt to reset device
> LIBMTP PANIC: failed to open session on second attempt
> Unable to open raw device 0
>
> With mtpfs 0.9-3+b1, I don't have such an error, but trying to read
> /media freezes for about 3 minutes, then I get:
>
> ls: cannot access /media/mtp: Transport endpoint is not connected
I much better results with libmtp9 from experimental:
$ apt-cache policy libmtp9
libmtp9:
Installed: 1.1.5-1
Candidate: 1.1.5-1
Package pin: (not found)
Version table:
*** 1.1.5-1 999
500 http://ftp.se.debian.org/debian/ experimental/main i386 Packages
$ mtpfs ~/mtpfs
Error: Unable to open ~/.mtpz-data for reading.
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 6
Attempting to connect device
Listing File Information on Device with name: GT-I8160
The irritating message:
Error: Unable to open ~/.mtpz-data for reading.
(also, accidentaly? the very 1st line in /lib/udev/rules.d/69-libmtp.rules)
does not seem to be an error (info/warning? maybe), as it's just scary and
has no ill effects. Maybe this:
https://groups.google.com/a/chromium.org/group/chromium-os-reviews/browse_thread/thread/af4ef5613b335f83?noredirect=true
catch some interest.
Cheers,
--
Cristian
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
