This bug was reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/592699
The reporter said the following:
"A Samsung SGH-X830 is no longer recognized in Rhythmbox after an upgrade to Lucid from Karmic. It can see it in Nautilus but not in Rhythmbox, although when it is plugged in via USB there's a prompt asking whether to open it in Rhythmbox. This device is an MTP player.
Installing Karmic's libmtp8 library causes the device to be recognized."
Please note the the libmtp's version available in Karmic is 0.3.7
Anonymous
Please provide mtp-detect (as root) on both setups. Does it work on one and not the other?
Thanks for the reply!
Please take a look at the following logs:
(taken from the original LP report)
Looks like some fighting over the control of the device actually, doesn't seem to be related to libmtp really, it's a distro, packaging udevd etc issue AFAICT. hard for me to test this without the device, I'd recommend testing it with latest libmtp on some other distro like Fedora to see if that solves something.
Hi,
I'm still looking for a fix, it seems udev isn't the guilty:
1) mtp-detect
ubuntu@ubuntu:~$ mtp-detect
libmtp version: 1.1.0
Listing raw device(s)
Device 0 (VID=04e8 and PID=6702) is a Samsung X830 Mobile Phone.
Found 1 device(s):
Samsung: X830 Mobile Phone (04e8:6702) @ bus 1, dev 5
Attempting to connect device(s)
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
OK.
2) mtp-connect
ubuntu@ubuntu:~$ sudo mtp-connect
libmtp version: 1.1.0
Device 0 (VID=04e8 and PID=6702) is a Samsung X830 Mobile Phone.
LIBMTP PANIC: Unable to find interface & endpoints of device
No devices.
3) mtp-reset
ubuntu@ubuntu:~$ mtp-reset
libmtp version: 1.1.0
Device 0 (VID=04e8 and PID=6702) is a Samsung X830 Mobile Phone.
LIBMTP PANIC: Unable to find interface & endpoints of device
No devices.
I'm still puzzled by this bug, very much :-(
closed upstream