[Nut-upsdev] Bug/Patch for NUT 2.6.0 ; usbhid-ups (libhid.c)

Arjen de Korte nut+devel at de-korte.org
Fri Feb 11 09:21:05 UTC 2011


Citeren Richard Gerth <r.gerth.phd op gmail.com>:

> I'm using openSUSE 11.2
> My usblibs are thus:
>
> bach:/usr/lib # ls -l libusb*
> lrwxrwxrwx 1 root root    19 Jan 11  2010 libusb-0.1.so.4 ->
> libusb-0.1.so.4.4.4*
> -rwxr-xr-x 1 root root 17940 Oct 23  2009 libusb-0.1.so.4.4.4*
> lrwxrwxrwx 1 root root    19 Jan 11  2010 libusb-1.0.so ->  
> libusb-1.0.so.0.0.0*
> lrwxrwxrwx 1 root root    19 Jan 11  2010 libusb-1.0.so.0 ->
> libusb-1.0.so.0.0.0*
> -rwxr-xr-x 1 root root 50884 Oct 23  2009 libusb-1.0.so.0.0.0*
> lrwxrwxrwx 1 root root    19 Jan 11  2010 libusb.so -> libusb-0.1.so.4.4.4*
>
> My computer's package manager says I have installed:  libusb 1.0  and
> a compatibility layer libusb-1_1-4

I've used openSUSE 11.2 in the past too (using 11.3 now) and have  
never seen such a problem with any of the USB connected UPS'es I  
tried, so this pretty much rules out a libusb issue. It must be  
vendor/device specific, probably the reason why the developers don't  
see this. Since we're not able to do anything with reports that are  
*longer* than expected anyway, we can safely assume that anything in  
excess of the number of bytes that we calculated from the report  
descriptor can be discarded. Therefor I have restored the nut-2.4.1  
behavior of only reading the number of bytes expected.

Thanks for reporting this.

Best regards, Arjen
-- 
Please keep list traffic on the list (off-list replies will be rejected)




More information about the Nut-upsdev mailing list