*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Tested with kernel 3.11.1-200.fc19.x86_64. This bug is still there.

Also 3.11.6-200.fc19.x86_64

But there are huge problems everywhere, so I'm not sure that this is the right bug to comment on. I can no longer access a digital camera as "mass storage" to copy photos. (The only way that seems to work is to open the camera with caja, view the pictures one by one, and save each one, using eom.)

I cannot access an android (4.3.3) tablet either through mtpfs or simple-mtpfs or go-mtpfs, or, after converting the tablet to mass storage, through anything else. On the latter, /var/log/messages shows the following, repeatedly, over and over, changing the number each time. I used to be able to use simple-mtpfs reliably.

Oct 29 06:10:14 barber kernel: [33079.692105] hub 2-0:1.0: unable to enumerate USB device on port 8
Oct 29 06:10:14 barber kernel: [33079.921975] usb 8-2: new full-speed USB device number 2 using uhci_hcd
Oct 29 06:10:14 barber kernel: [33080.451681] usb 8-2: new full-speed USB device number 3 using uhci_hcd
Oct 29 06:10:15 barber kernel: [33080.987384] usb 8-2: new full-speed USB device number 4 using uhci_hcd
Oct 29 06:10:15 barber kernel: [33081.340190] usb 8-2: new full-speed USB device number 5 using uhci_hcd
Oct 29 06:10:16 barber kernel: [33081.592065] hub 8-0:1.0: unable to enumerate USB device on port 2
Oct 29 06:10:16 barber kernel: [33081.714982] usb 8-2: new full-speed USB device number 6 using uhci_hcd
Oct 29 06:10:16 barber kernel: [33082.248706] usb 8-2: new full-speed USB device number 7 using uhci_hcd
Oct 29 06:10:17 barber kernel: [33082.779323] usb 8-2: new full-speed USB device number 8 using uhci_hcd
Oct 29 06:10:17 barber kernel: [33083.132200] usb 8-2: new full-speed USB device number 9 using uhci_hcd

Ad your tablet: Please, check, if your vendor and product ID are present in libmtp header file music-players.h. If not, none of mentioned FUSE drivers will work.

(In reply to Peter Hatina from comment #4)
> Ad your tablet: Please, check, if your vendor and product ID are present in
> libmtp header file music-players.h. If not, none of mentioned FUSE drivers
> will work.

music-players.h does not list any vendors or IDs. However, 69-libmtp-rules does list them, and it seems that my tablet (Nexus 10) is listed there:

# Google Inc (for LG Electronics/Samsung) Nexus 4/10 (MTP)
ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee1", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
# Google Inc (for LG Electronics/Samsung) Nexus 4/10 (MTP+ADB)
ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"

music-players.h *do* list vendor and product ID's (see [1]) and your device needs to be included in that file in order to make libmtp work with your tablet.

Follow instructions stated in chapter "New Device?" at [2].

[1] http://sourceforge.net/p/libmtp/code/ci/HEAD/tree/src/music-players.h
[2] http://libmtp.sourceforge.net/

Now I'm really confused. I thought that I had looked at music-players.h, but apparently I don't have it. I don't know what I looked at. It seems to be part of the source, which is not kept once libmtp is compiled. But the version of libmtp that I have has a listing on sourceforge, and it contains exactly the same information that I found in 69-libmtp-rules. Perhaps 69-libmtp-rules is compiled from music-players.h.

Anyway, just for fun, I upgraded the tablet to version 4.4 of Android and tried it again, with simple-mtpfs. I got the usual error message:

Device 0 (VID=18d1 and PID=4ee1) is a Google Inc (for LG Electronics/Samsung) Nexus 4/10 (MTP).
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device

But then I didn't do anything for a few seconds, and it actually succeeded in connecting. It has worked before like this, and then stopped working after some time, but perhaps it won't stop this time. We'll see.

Ah, I am glad, it works for you, now. I also see that kind of error messages, when mounting my Galaxy Nexus or Nexus 7 (libmtp stuff).

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.12.6-200.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.

I have upgraded to Fedora 20.  Testing with latest kernel 3.12.6-300.fc20.x86_64 my camera is mounted successfully.

Hi Craig,

thanks for confirming. Am closing this BZ.

regards,
Michele

Works for me too on Fedora 19.

However, I still cannot connect to my Nexus 10 tablet with simple-mtpfs. I guess I'll either give up on that - even though it used to work - since I can now connect with ssh-server. I thought this was the same bug, but it isn't.