lsusb lists nothing after upgrade to karmic (9.10)

Bug #459393 reported by Burt P. on 2009-10-23
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
usbutils (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: usbutils

After upgrading from jaunty to karmic, lsusb does not list any devices, although USB devices continue to work.

>lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

>apt-cache policy usbutils
usbutils:
  Installed: 0.82-0ubuntu1
  Candidate: 0.82-0ubuntu1
  Version table:
 *** 0.82-0ubuntu1 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
Architecture: i386
Date: Fri Oct 23 15:27:19 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: usbutils 0.82-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-15.52-generic
SourcePackage: usbutils
Uname: Linux 2.6.28-15-generic i686

Burt P. (pburt0) wrote :

- It appears you're still using the kernel from Jaunty
- Does this help?:
sudo update-usbids

Burt P. (pburt0) wrote :

Yes, I'm using 2.6.28 to avoid a different bug. `sudo update-usbids.sh` had no effect in 2.6.28. I've now tried it in 2.6.31 and it does work as expected there, but I have to use 2.6.28 for now. I guess it doesn't matter that lsusb is broken as long as USB devices are still working.

jb.maillet (jb-maillet) wrote :

Same problem here, and update-usbids.sh doesn't help either. Additional info:

lsusb -t
...report the device with correct vendor and product Id, but any over form of lsusb command does not go beyond the root hub.

gnome-device-manager report the devices correctly.
hardinfo report the devices correctly.
kde-hal-device-manager segfault (other problem).

jb.maillet (jb-maillet) wrote :

Additional info:

Provided /dev/bus/usb is mounted as /proc/bus/usb,
an hand built usbutils-0.11, very old, fetched from http://www.lrr.in.tum.de/Par/arch/usb/download/usbutils/, solved the problem. Note that this comes with its own libusb.
An hand built usbview-1.1 also behave correctly. It does not use libusb.

On the other hand, in spite of the mounting, all packaged I could fetch from http://sourceforge.net/projects/linux-usb/files/usbutils/ display the same faulty behavior. They all link against the installed libusb.

~$ apt-cache policy libusb-1.0-0
libusb-1.0-0:
  Installed: 2:1.0.1-1
  Candidate: 2:1.0.1-1
  Version table:
 *** 2:1.0.1-1 0
        500 http://fr.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
~$ apt-cache policy libusb-0.1-4
libusb-0.1-4:
  Installed: 2:0.1.12-13
  Candidate: 2:0.1.12-13
  Version table:
 *** 2:0.1.12-13 0
        500 http://fr.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

I don't know if this workaround will help anyone
else, but try unplugging the hub and plugging it
back in. I did this and all the devices connected
to the hub reappeared. I'm finding that I have to
do this occasionally after booting to the desktop.

This doesn't solve the problem, of course.

A.Lizard

At 06:51 AM 11/3/2009, you wrote:
>Same problem here, and update-usbids.sh doesn't help either. Additional
>info:
>
>lsusb -t
>...report the device with correct vendor and
>product Id, but any over form of lsusb command does not go beyond the root hub.
>
>gnome-device-manager report the devices correctly.
>hardinfo report the devices correctly.
>kde-hal-device-manager segfault (other problem).
>
>--
>lsusb lists nothing after upgrade to karmic (9.10)
>https://bugs.launchpad.net/bugs/459393
>You received this bug notification because you are a direct subscriber
>of the bug.
>
>Status in “usbutils” package in Ubuntu: New
>
>Bug description:
>Binary package hint: usbutils
>
>After upgrading from jaunty to karmic, lsusb
>does not list any devices, although USB devices continue to work.
>
> >lsb_release -rd
>Description: Ubuntu 9.10
>Release: 9.10
>
> >apt-cache policy usbutils
>usbutils:
> Installed: 0.82-0ubuntu1
> Candidate: 0.82-0ubuntu1
> Version table:
> *** 0.82-0ubuntu1 0
> 500 http://us.archive.ubuntu.com karmic/main Packages
> 100 /var/lib/dpkg/status
>
>ProblemType: Bug
>Architecture: i386
>Date: Fri Oct 23 15:27:19 2009
>DistroRelease: Ubuntu 9.10
>NonfreeKernelModules: nvidia
>Package: usbutils 0.82-0ubuntu1
>ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
>ProcVersionSignature: Ubuntu 2.6.28-15.52-generic
>SourcePackage: usbutils
>Uname: Linux 2.6.28-15-generic i686

member The Internet Society (ISOC), The HTML Writers Guild.
[new sig quote soon]
Personal Website http://www.ecis.com/~alizard
business Website http://www.reptilelabs.com
backup address (if ALL else fails) <email address hidden>
PGP 8.0 key available by request or keyserver. Download PGP from:
http://www.pgpi.org for e-mail privacy.
Disaster prep info: http://www.ecis.com/~alizard/y2k.html
***Looking for INTELLIGENT new technology public policy alternatives?***
http://www.ecis.com/~alizard/technology.html

jb.maillet (jb-maillet) wrote :

Alizar: there is no "hub". The root hub I refer to is built inside the host controler, and cannot be removed.

alizard (alizard) wrote :

At 12:42 AM 11/4/2009, you wrote:
>Alizar: there is no "hub". The root hub I refer to is built inside the
>host controler, and cannot be removed.

never mind, I appear to be posting to the wrong
bug. In my case, lsusb listed the built-in hubs
and *ONLY* the built-in hubs, I assume you mean
the "Linux Foundation 1.1 root hub"s... and after
replugging the devices (I've had to do this a
couple of times) everything shows up and is
connected. I'll look for the right bug, it's
obvious we have different problems.

Bus 004 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 001 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 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 006: ID 1020:030a Labtec
Bus 003 Device 005: ID 050d:0551 Belkin Components F6C550-AVR UPS
Bus 003 Device 004: ID 04a9:1094 Canon, Inc. PIXMA iP3000x Printer
Bus 003 Device 003: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30
Bus 003 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

>--
>lsusb lists nothing after upgrade to karmic (9.10)
>https://bugs.launchpad.net/bugs/459393
>You received this bug notification because you are a direct subscriber
>of the bug.
>
>Status in “usbutils” package in Ubuntu: New
>
>Bug description:
>Binary package hint: usbutils
>
>After upgrading from jaunty to karmic, lsusb
>does not list any devices, although USB devices continue to work.
>
> >lsb_release -rd
>Description: Ubuntu 9.10
>Release: 9.10
>
> >apt-cache policy usbutils
>usbutils:
> Installed: 0.82-0ubuntu1
> Candidate: 0.82-0ubuntu1
> Version table:
> *** 0.82-0ubuntu1 0
> 500 http://us.archive.ubuntu.com karmic/main Packages
> 100 /var/lib/dpkg/status
>
>ProblemType: Bug
>Architecture: i386
>Date: Fri Oct 23 15:27:19 2009
>DistroRelease: Ubuntu 9.10
>NonfreeKernelModules: nvidia
>Package: usbutils 0.82-0ubuntu1
>ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
>ProcVersionSignature: Ubuntu 2.6.28-15.52-generic
>SourcePackage: usbutils
>Uname: Linux 2.6.28-15-generic i686

member The Internet Society (ISOC), The HTML Writers Guild.
[new sig quote soon]
Personal Website http://www.ecis.com/~alizard
business Website http://www.reptilelabs.com
backup address (if ALL else fails) <email address hidden>
PGP 8.0 key available by request or keyserver. Download PGP from:
http://www.pgpi.org for e-mail privacy.
Disaster prep info: http://www.ecis.com/~alizard/y2k.html
***Looking for INTELLIGENT new technology public policy alternatives?***
http://www.ecis.com/~alizard/technology.html

After upgrading to Karmic 9.10, lsusb just hangs.

Oli (oli) wrote :

Is there any way to restart the USB subsystem?

Sometimes lsusb hangs and new devices are not initialised.

papukaija (papukaija) on 2009-11-28
Changed in usbutils (Ubuntu):
status: New → Confirmed

After upgrade to 9.10 I have the same bug with T61 laptop.

I find in more recent versions of Ubuntu (ie 10.4 up to 11.10) I no longer see this problem in 64 bit versions.

(I've been using only 64 bit versions)

Is this any longer reproduceable?

Marking Invalid since there has been no response on reproducing this error in modern Ubuntu versions.

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

Other bug subscribers