Bad handling of unknown usb/pci class codes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udev-discover |
Fix Released
|
Medium
|
J. Félix Ontañón | ||
0.2 |
Fix Released
|
Medium
|
J. Félix Ontañón |
Bug Description
12:21 root@puchatek:
/usr/lib/
return info.invoke(*args)
Traceback (most recent call last):
File "/usr/bin/
UDevDiscove
File "/usr/bin/
self.
File "/usr/bin/
self.
File "/usr/bin/
[device.path, device_icon, device.nice_label,
File "/usr/lib/
usb_type[1], usb_type[2])
File "/usr/lib/
value = self.func(*args)
File "/usr/lib/
return usb_class_
KeyError: (7, 1, -1)
Changed in udev-discover: | |
status: | Fix Committed → Fix Released |
Hi Marcin, thanks for your feedback.
Could you unplug your usb devices and then launch the udev-discover? It seems that one of the usb devices has or hasn't some property expected by the code, so it could be great if you could plug the devices one by one after the udev-discover be launched to identify it.
If you can't unplug all of them, at least try with what you can to reduce the options.
By the way, you don't need to be root or to use 'sudo' command to use udev-discover.
Thanks for your time :-)