Version: unspecified (using KDE 4.6.1) OS: Linux The firest 3 devices aren't seen as long as I did not plug in them directly into my ThinkPad T400 (which is docked). foerste@n22 ~ $ /usr/sbin/lsusb Bus 001 Device 012: ID 046d:c062 Logitech, Inc. Bus 001 Device 010: ID 043d:0078 Lexmark International, Inc. InkJet Color Printer Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard Bus 001 Device 003: ID 04b3:4485 IBM Corp. Serial Converter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0a5c:2145 Broadcom Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Reproducible: Didn't try OS: Linux (i686) release 2.6.37.3-rc1 Compiler: i686-pc-linux-gnu-gcc
not solved here in 4.6.4
4.8.2 : tfoerste@n22 ~ $ /usr/bin/lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 04b3:4485 IBM Corp. Serial Converter Bus 002 Device 002: ID 1bcf:0c31 Sunplus Innovation Technology Inc. SPIF30x Serial-ATA bridge Bus 004 Device 002: ID 0a5c:2145 Broadcom Corp. Bluetooth with Enhanced Data Rate II Bus 001 Device 004: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard Bus 001 Device 005: ID 043d:0078 Lexmark International, Inc. InkJet Color Printer Bus 001 Device 006: ID 046d:c062 Logitech, Inc. LS1 Laser Mouse, corded
solved in 4.8.4 (or was it a side effect of a completely different system ?)
Well, it seems, that with the new llinux kernel 3.4.4-rc1 sometimes (but not always) the issue seems to went away - /me confused.
Very odd.. I shall keep it open for now. Can you take a lsusb when it works and when it does not for me. Thanks
Created attachment 72244 [details] lsusb-v output of "sudo lsusb -v 1> lsusb-v 2>&1" when it is visisble
Created attachment 72245 [details] screen shot of KInfocentre
Created attachment 72246 [details] screen shot of KInfocentre (2#2) vendor id and so on
Created attachment 72247 [details] lsusb-v (not ok) and here , when the devices aren't displayed.
And what makes me really wondering is , that if I plugin an external USB drive directly onto the ThinkPad (while docked), then the entry of the keyboard is replaced with the entry of the new external hard disk (instead that th enew hard disk wpould be added) . The appropriate lsusb outputs are : n22 ~ # lsusb | sort Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 04b3:4485 IBM Corp. Serial Converter Bus 001 Device 003: ID 043d:0078 Lexmark International, Inc. InkJet Color Printer Bus 001 Device 004: ID 046d:c062 Logitech, Inc. LS1 Laser Mouse, corded Bus 001 Device 005: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard Bus 001 Device 009: ID 04b4:6830 Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 1bcf:0c31 Sunplus Innovation Technology Inc. SPIF30x Serial-ATA bridge Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0a5c:2145 Broadcom Corp. Bluetooth with Enhanced Data Rate II Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub n22 ~ # n22 ~ # n22 ~ # n22 ~ # lsusb | sort Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 04b3:4485 IBM Corp. Serial Converter Bus 001 Device 003: ID 043d:0078 Lexmark International, Inc. InkJet Color Printer Bus 001 Device 004: ID 046d:c062 Logitech, Inc. LS1 Laser Mouse, corded Bus 001 Device 005: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 1bcf:0c31 Sunplus Innovation Technology Inc. SPIF30x Serial-ATA bridge Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0a5c:2145 Broadcom Corp. Bluetooth with Enhanced Data Rate II Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Created attachment 73305 [details] screen shot of KInfocenter ANother example where (after 3 days of uptime) and a lot of s2ram/s2disk/(un)plugin of USB drives and/or DVB-T sticks suddenly KInfoCenter displays the docked devices. _ I'm pretty sure it won't work after boot 3 days ago .... FWIW I'm currently on kernel 3.5.2, lsusb -v follows
Created attachment 73306 [details] lsusb -v n22 ~ # grep -B 2 missing /tmp/lsusb-v Usage Type Data wMaxPacketSize 0x0020 1x 32 bytes bIntervCouldn't open device, some information will be missing -- bcdDevice 3.05 iManufacturer 3 Couldn't get configuration descriptor 0, some information will be missing Couldn't get configuration descriptor 0, some information will be missing
Is this still a problem on newer systems?
system is gone
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!