Rhythmbox "blocks" pendrives from mounting

Bug #555262 reported by Emilio on 2010-04-04
46
This bug affects 10 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: rhythmbox

* If Rhythmbox is running and you plug a pendrive on a USB port, the pendrive doesn't get automounted, nor is available for mounting manually (it doesn't even get a device in /dev/)
This shows up in dmesg:

[ 2744.150330] usb 2-4: new high speed USB device using ehci_hcd and address 16
[ 2744.400413] usb 2-4: configuration #1 chosen from 1 choice
[ 2744.411834] scsi14 : SCSI emulation for USB Mass Storage devices
[ 2744.412153] usb-storage: device found at 16
[ 2744.412158] usb-storage: waiting for device to settle before scanning
[ 2745.680157] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 2749.429232] usb-storage: device scan complete
[ 2749.430074] hub 2-0:1.0: port 4 disabled by hub (EMI?), re-enabling...
[ 2749.430086] usb 2-4: USB disconnect, address 16

Despite the message in 2749.430086, the pendrive is still plugged on the USB port.

If you close Rhythmbox and then plug the pendrive, it works just fine.
This shows up in dmesg:

[ 2872.110319] usb 2-4: new high speed USB device using ehci_hcd and address 17
[ 2872.360419] usb 2-4: configuration #1 chosen from 1 choice
[ 2872.371812] scsi15 : SCSI emulation for USB Mass Storage devices
[ 2872.374091] usb-storage: device found at 17
[ 2872.374098] usb-storage: waiting for device to settle before scanning
[ 2877.383994] usb-storage: device scan complete
[ 2877.384848] scsi 15:0:0:0: Direct-Access Kingston DataTraveler 2.0 6.00 PQ: 0 ANSI: 2
[ 2877.385891] sd 15:0:0:0: Attached scsi generic sg3 type 0
[ 2877.395338] sd 15:0:0:0: [sdc] 1001472 512-byte logical blocks: (512 MB/489 MiB)
[ 2877.396059] sd 15:0:0:0: [sdc] Write Protect is off
[ 2877.396067] sd 15:0:0:0: [sdc] Mode Sense: 0b 00 00 08
[ 2877.396073] sd 15:0:0:0: [sdc] Assuming drive cache: write through
[ 2877.405308] sd 15:0:0:0: [sdc] Assuming drive cache: write through
[ 2877.405320] sdc: sdc1
[ 2877.415549] sd 15:0:0:0: [sdc] Assuming drive cache: write through
[ 2877.415561] sd 15:0:0:0: [sdc] Attached SCSI removable disk

* If you open Rhythmbox with the pendrive plugged and correctly mounted, it takes a lot to start.
This shows up in dmesg:

[ 2949.410200] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 2950.690194] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 2951.720168] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 2952.990199] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 2954.270190] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 2955.540181] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 2956.820186] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 2957.850188] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 2958.890182] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 2960.170189] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 2961.450190] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 2962.720198] usb 2-4: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110

I'm using Ubuntu Lucid Lynx, rhythmbox 0.12.8-0ubuntu1. I'm sure the problem is not the pendrive, as I tried with 2 different brands and sizes and the same thing happened. If you need any other information do not hesitate to ask.

Sebastien Bacher (seb128) wrote :

thank you for your bug report. Do you get the issue if you disable the mtp plugin in gconf-editor, apps, rhythmbox? could you open a bug using "ubuntu-bug storage" too? it will give details about the hardware used and logs about what is happening

Changed in rhythmbox (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Emilio (turl) wrote :

Disabling the mtp plugin allows the pendrives to be detected and mounted correctly when Rhythmbox is running. However, disabling it is a workaround and not a fix.

Here is the bug reported with "ubuntu-bug storage": https://bugs.launchpad.net/ubuntu/+source/linux/+bug/557551

Sebastien Bacher (seb128) wrote :

could you run mtp-detect with the device connected and add the log to the bug?

Emilio (turl) wrote :

Here is the log you requested. Note that the device is *not* a MTP device, it's just a pendrive. For the test, I had rhythmbox closed and did it with both the device mounted and unmounted:

emilio@laptop:~$ mtp-detect
libmtp version: 1.0.2

Listing raw device(s)
   No raw devices found.

You might find this useful too, it's part of the rhythmbox log produced by running "rhythmbox -d". The device does not appear on the list of mountable devices after plugging in, nor there is a /dev/ entry for it.

(17:19:05) [0xb1c040] [uevent_cb] rb-removable-media-manager.c:591: add event for /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-4 (bd8a)
(17:19:05) [0xb1c040] [create_source_device_cb] rb-mtp-plugin.c:368: trying to match device bd8a (usb device 11) against detected mtp devices
(17:19:06) [0xb1c040] [create_source_device_cb] rb-mtp-plugin.c:392: device didn't match anything
(17:19:06) [0xb1c040] [uevent_cb] rb-removable-media-manager.c:591: add event for /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-4/2-4:1.0 (0)
(17:19:06) [0xb1c040] [create_source_device_cb] rb-mtp-plugin.c:354: can't get udev device number for device 2-4:1.0
(17:19:10) [0xb1c040] [uevent_cb] rb-removable-media-manager.c:591: remove event for /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-4/2-4:1.0 (0)
(17:19:10) [0xb1c040] [uevent_cb] rb-removable-media-manager.c:591: remove event for /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-4 (bd8a)

Sebastien Bacher (seb128) wrote :

could you run rhythmbox -D mtp with the device connected?

Emilio (turl) wrote :

Here is the log you requested with the device plugged in and mounted

Changed in rhythmbox (Ubuntu):
status: Incomplete → New

I noticed there isn't the same behavoir for all the USB pendrives. For example a Kingston 512 MB (from lsusb -> Bus 001 Device 019: ID 0930:6533 Toshiba Corp. 512M Stick) has this problem, while a Sandisc 8GB (Bus 001 Device 020: ID 0781:5406 SanDisk Corp. Cruzer Micro 1/2/4GB Flash Drive) doesn't. Unfortunately the pen with the problem isn't mine so I'll try to provide more informations as possible about this device

From dmesg:
[16176.401035] usb 1-6: new high speed USB device using ehci_hcd and address 16
[16176.617614] usb 1-6: configuration #1 chosen from 1 choice
[16176.630617] scsi12 : SCSI emulation for USB Mass Storage devices
[16176.635082] usb-storage: device found at 16
[16176.635091] usb-storage: waiting for device to settle before scanning
[16177.760096] usb 1-6: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[16181.659446] usb-storage: device scan complete
[16181.660423] hub 1-0:1.0: port 6 disabled by hub (EMI?), re-enabling...
[16181.660433] usb 1-6: USB disconnect, address 16

mtp-detect (both with the pendrive mounted and unmounted)
michele@lucid-desktop:~$ mtp-detect
libmtp version: 1.0.2

Listing raw device(s)
   No raw devices found.

I have the same pblema with a Kensington wireless keyboard

[524.373682] input: Kensington Kensington Ci70 Wireless Desktop Set as / devices/pci0000: 00/0000: 00:1 d.1/usb7/7-1/7-1: 1.1/input/input93
[524.373868] generic-usb 0003:047 D: 2033.0050: input, hidraw1: USB HID v1.10 Mouse [Kensington Kensington Ci70 Wireless Desktop Set] on usb-0000: 00:1 d.1-1/input1
[524.792997] usb 7-1: usbfs: cmd failed rhythmbox USBDEVFS_CONTROL RQT 128 rq 6 len 1024 ret -84
[524.972233] usb 7-1: USB disconnect, address 40
[525.280156] usb 7-1: new low speed USB device using uhci_hcd and address 41
[530.396149] usb 7-1: device descriptor read/64, error -71
[530.620184] usb 7-1: device descriptor read/64, error -71
[530.836154] usb 7-1: new low speed USB device using uhci_hcd and address 42
[530.956156] usb 7-1: device descriptor read/64, error -71
[531.184165] usb 7-1: device descriptor read/64, error -71
[531.401168] usb 7-1: new low speed USB device using uhci_hcd and address 43
[531.808161] usb 7-1: device not accepting address 43, error -71
[531.920150] usb 7-1: new low speed USB device using uhci_hcd and address 44
[532.328153] usb 7-1: device not accepting address 44, error -71
[532.328182] hub 7-0:1.0: Unable to enumerate USB device on port 1
[616.497147] usb 7-1: new low speed USB device using uhci_hcd and address 45
[616.620082] usb 7-1: device descriptor read/64, error -71
[616.848141] usb 7-1: device descriptor read/64, error -71
[617.064190] usb 7-1: new low speed USB device using uhci_hcd and address 46
[617.188192] usb 7-1: device descriptor read/64, error -71
[617.416153] usb 7-1: device descriptor read/64, error -71
[617.632155] usb 7-1: new low speed USB device using uhci_hcd and address 47
[618.048155] usb 7-1: device not accepting address 47, error -71
[618.160187] usb 7-1: new low speed USB device using uhci_hcd and address 48
[618.576126] usb 7-1: device not accepting address 48, error -71
[618.576156] hub 7-0:1.0: Unable to enumerate USB device on port 1
[740.240134] usb 7-1: new low speed USB device using uhci_hcd and address 49
[740.423461] usb 7-1: configuration # 1 CHOSEN from 1 choice
[740.439799] input: Kensington Kensington Ci70 Wireless Desktop Set as / devices/pci0000: 00/0000: 00:1 d.1/usb7/7-1/7-1: 1.0/input/input94

but I did what I mentioned Sebastes Bacher and solved.

Scott Taylor (staylor) wrote :

I've got the same issue with a Kensington Expert Mouse trackball.

Here's my dmesg output:

[ 6924.870020] usb 7-1: new low speed USB device using uhci_hcd and address 47
[ 6925.055109] usb 7-1: configuration #1 chosen from 1 choice
[ 6925.071237] input: Kensington Kensington Expert Mouse as /devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/input/input588
[ 6925.071340] generic-usb 0003:047D:1020.0247: input,hidraw2: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-0000:00:1d.1-1/input0
[ 6925.099028] usb 7-1: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -84

I'm running Rhythmbox 0.12.8 and Lucid Lynx 10.04 x86_64.

Disabling MTP (or closing Rhythmbox altogether) brings the trackball back to life; with MTP-enabled Rhythmbox running, the trackball is completely nonfunctional.

I've got the same issue with my Philips AMBX set. (Ubuntu Lucid, 2.6.32-24-generic)

[566420.513041] usb 2-3: USB disconnect, address 29
[566423.024017] usb 2-3: new full speed USB device using ohci_hcd and address 30
[566423.245236] usb 2-3: configuration #1 chosen from 1 choice
[566423.259271] usb 2-3: USB disconnect, address 30
[566423.260296] usb 2-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -108

And it keeps connecting/disconnecting in a loop. Disabling the Rhythmbox MTP plugin solved the issue.

Tremaine Lea (tremaine) wrote :

This issue crops up for me quite often, and I hadn't tied it to Rhythmbox previously - but after closing it, I was able to mount my Canon 7D with no problem at all.

[1361005.116030] usb 7-2: new full speed USB device using uhci_hcd and address 126
[1361005.236030] usb 7-2: device descriptor read/64, error -71
[1361005.460021] usb 7-2: device descriptor read/64, error -71
[1361005.676022] usb 7-2: new full speed USB device using uhci_hcd and address 127
[1361005.796023] usb 7-2: device descriptor read/64, error -71
[1361006.020033] usb 7-2: device descriptor read/64, error -71
[1361006.236026] usb 7-2: new full speed USB device using uhci_hcd and address 2
[1361006.644023] usb 7-2: device not accepting address 2, error -71
[1361006.756024] usb 7-2: new full speed USB device using uhci_hcd and address 3
[1361007.164023] usb 7-2: device not accepting address 3, error -71
[1361007.164043] hub 7-0:1.0: unable to enumerate USB device on port 2
[1361013.668526] usb 2-6: reset high speed USB device using ehci_hcd and address 25

Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of Rhythmbox is available on Maverick and we are wondering if this bug is still an issue for you with that version? Could you please test and comment back? Thanks in advance.

Changed in rhythmbox (Ubuntu):
status: New → Incomplete
Sam Liddicott (sam-liddicott) wrote :
Download full text (6.8 KiB)

I can plug in a USB drive and it works fine.

I start rhythmbox and it causes the drive to be ejected.

Here is the output of dmesg:

[ 571.432202] usb 2-3.1: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 572.440474] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -110
[ 572.456679] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -71
[ 573.852167] usb 2-3.1: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 573.880126] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -71
[ 573.896248] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -71
[ 574.321447] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -71
[ 574.337826] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -71
[ 575.732672] usb 2-3.1: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -110
[ 575.761766] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -71
[ 575.778390] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -71
[ 576.203465] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -71
[ 576.220859] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -71
[ 576.636416] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -71
[ 576.652544] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -71
[ 578.040145] usb 2-3.1: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -110
[ 578.069002] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -71
[ 578.085232] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -71
[ 578.501560] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -71
[ 578.517679] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -71
[ 579.900902] usb 2-3.1: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -110
[ 579.930501] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -71
[ 579.946625] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -71
[ 580.374449] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -71
[ 580.390574] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -71
[ 580.806528] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -71
[ 580.822647] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -71
[ 581.239205] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 ret -71
[ 581.255330] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -71
[ 582.644692] usb 2-3.1: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 1024 ret -110
[ 582.672791] usb 1-3: usbfs: USBDEVFS_CONTROL failed cmd rhythmbox rqt 128 rq 6 len 255 r...

Read more...

Sam Liddicott (sam-liddicott) wrote :

The problem occurs with a
ID 0204:6025 Chipsbank Microelectronics Co., Ltd CBM2080 Flash drive controller

but not with my Sandisk Cruzr

I'm using Maverick, with Rhythmbox 0.13.1

Disabling MTP plugin stops it breaking

Changed in rhythmbox (Ubuntu):
status: Incomplete → New
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Oneiric Ocelot. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Changed in rhythmbox (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]

Changed in rhythmbox (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers