Public bug reported:
I have a sandisk sansa clip 4gb media player. It is configured to
connect to the computer as a flash drive, not using mtp.
When connecting it to latest Hardy, nothing happens. Running lsusb
doesn't show anything, but somehow causes some trigger and after a
couple of seconds the device shows up again with a disk icon on the
desktop.
Here is the output of lsusb, first time, nothing connected:
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 003: ID 0a5c:2110 Broadcom Corp.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Then I connect the device, nothing happens. Running lsusb, second time,
yields the same output. However, after a few seconds the device is
suddenly recognized. Running lsusb the third time yields this output,
confirming the device's presence:
Bus 005 Device 006: ID 0781:7433 SanDisk Corp.
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 003: ID 0a5c:2110 Broadcom Corp.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
lshal behaves similarly. The output is identical in the first and second
times, before and after connecting the device (expect for minor battery
related differences). In the third time, after running lsusb and
recognizing the device, 7 more devices are dumped (I am attaching the
diff).
** Affects: ubuntu
Importance: Undecided
Status: New
--
lsusb required to recognize sandisk media player as usb drive
https://bugs.launchpad.net/bugs/242163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
