"usb_id: unable to access" - Terminal warnings on boot

[Gunnar Steinn]

See the messages in the attachment

ProblemType: Bug
Architecture: i386
Date: Tue Oct 6 09:33:13 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia wl
Package: linux-image-2.6.31-11-generic 2.6.31-11.38
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: linux
Uname: Linux 2.6.31-11-generic i686

[Gunnar Steinn (gunnarsteinn)]

Machine: Dell Latitude E6400.
Upgraded from 9.04 to alpha 3 and up from there.
The message has been there (and few others which are gone) since alpha 3

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

apport-collect 444399

This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Gunnar Steinn (gunnarsteinn)]

Architecture: i386
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl nvidia
Package: linux (not installed)
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
Uname: Linux 2.6.31-11-generic i686
UserGroups:

[Gunnar Steinn (gunnarsteinn)]

AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: BETWARE\gunnarsteinn 2944 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6fdc000 irq 21'
   Mixer name : 'IDT 92HD71B7X'
   Components : 'HDA:111d76b2,10280233,00100302'
   Controls : 28
   Simple ctrls : 18
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=80f23f09-c561-43e2-805b-49e117ae7c27
MachineType: Dell Inc. Latitude E6400
NonfreeKernelModules: wl nvidia
Package: linux (not installed)
ProcCmdLine: root=UUID=48735b54-a4bf-4613-b1c7-5d1411d1bd46 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-11-generic N/A
 linux-firmware 1.20
Uname: Linux 2.6.31-11-generic i686
UserGroups:

WpaSupplicantLog:

dmi.bios.date: 05/11/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0U695R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/11/2009:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0U695R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6400
dmi.sys.vendor: Dell Inc.

[Gunnar Steinn (gunnarsteinn)]

Sorry about the duplicates, first ran apport-collect without sudo :)

Please ask for more information if that helps

Gunnar Steinn

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 439648, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.