Rhythmbox "blocks" pendrives from mounting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
Expired
|
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.
Changed in rhythmbox (Ubuntu): | |
status: | Incomplete → New |
Changed in rhythmbox (Ubuntu): | |
status: | Incomplete → New |
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