Bug #779512 “nut-2.6.0-1ubuntu3 behavior regression” : Bugs : nut package : Ubuntu

Revision history for this message

Mr. Muskrat (mr-muskrat) wrote on 2011-05-08:

#1

Dependencies.txt Edit (1.9 KiB, text/plain; charset="utf-8")
NutInstalledVersions.txt Edit (127 bytes, text/plain; charset="utf-8")
USBDevices.txt Edit (839 bytes, text/plain; charset="utf-8")

Revision history for this message

Arnaud Quette (aquette) wrote on 2011-05-09: Re: [Bug 779512] [NEW] nut-2.6.0-1ubuntu3 behavior regression

#2

2011/5/8 Mr. Muskrat <email address hidden>

> Public bug reported:
>
> Binary package hint: nut
>
> Prior to upgrading to Natty, I had the nut-2.4.3-1ubuntu5 package and it
> was working correctly.
>

right, but the fix made for the kind of devices you have (ie not fully
complying to USB standards) broke other devices / features.

the right fix would have to be in libusb, but since we're still on 0.1
(which is not maintained anymore), the solution may come from the port to
libusb 1.0.

After upgrading to Natty, I have the nut-2.6.0-1ubuntu3 package and it
> is not working correctly. Here's my release info:
>
> •[x4linux:~] mmusgrove $ lsb_release -rd
> Description: Ubuntu 11.04
> Release: 11.04
>
> The symptom is that it can't initialize data from HID UPS and so the
> driver fails to start.
>
> •[x4linux:~] mmusgrove $ sudo upsdrvctl start
> Network UPS Tools - UPS driver controller 2.6.0
> Network UPS Tools - Generic HID driver 0.35 (2.6.0)
> USB communication driver 0.31
> Using subdriver: CyberPower HID 0.3
> libusb_get_report: No error
> Can't initialize data from HID UPS
> Driver failed to start (exit status=1)
>
> (...)

could you please do the following test and send back the output:
- first, stop nut
- then "export USB_DEBUG=3"
- start the driver using "sudo /lib/nut/usbhid-ups -DDDD -a <upsname>"
where <upsname> is the one from ups.conf.

- the output of "dpkg -l '*libusb*'" would also be useful.

cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Revision history for this message

Mr. Muskrat (mr-muskrat) wrote on 2011-05-09:

#3

Download full text (15.1 KiB)

Arnaud,
Here is what you have asked for.

Matt

•[x4linux:~] mmusgrove $ sudo service nut stop
[sudo] password for mmusgrove:
* Stopping Network UPS Tools [ OK ]
•[x4linux:~] mmusgrove $ export USB_DEBUG=3
•[x4linux:~] mmusgrove $ sudo /lib/nut/usbhid-ups -DDDD -a cyberpower
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
   0.000000 debug level is '4'
   0.001247 upsdrv_initups...
   0.290879 Checking device (0764/0501) (007/004)
   0.302437 - VendorID: 0764
   0.302466 - ProductID: 0501
   0.302477 - Manufacturer: CPS
   0.302487 - Product: UPS CP1000AVRLCD
   0.302496 - Serial Number: unknown
   0.302506 - Bus: 007
   0.302515 Trying to match device
   0.302571 Device matches
   0.307441 HID descriptor, method 1: (9 bytes) => 09 21 10 01 21 01 22 83 01
   0.307472 i=0, extra[i]=09, extra[i+1]=21
   0.307489 HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 01 22 83 01
   0.307500 HID descriptor length 387
   0.333436 Report Descriptor size = 387
   0.333478 Report Descriptor: (387 bytes) => 05 84 09 04 a1 01 09 24 a1 00 85 01 09 fe
   0.333504 75 08 95 01 15 00 26 ff 00 b1 22 85 02 09 ff b1 22 85 03 05 85 09 89 b1 22
   0.333528 85 04 09 8f b1 22 85 05 09 8b b1 22 85 06 09 2c b1 22 85 07 75 08 95 06 25
   0.333551 78 09 83 09 8d 09 8e 09 8c 09 29 09 67 b1 22 85 08 75 08 95 01 65 00 09 66
   0.333574 81 a2 09 66 b1 a2 09 68 75 10 27 ff ff 00 00 66 01 10 81 a2 09 68 b1 a2 09
   0.333597 2a 26 58 02 81 a2 09 2a b1 a2 85 09 75 08 26 ff 00 05 84 09 40 67 21 d1 f0
   0.333621 00 55 06 b1 22 85 0a 09 30 b1 a2 65 00 55 00 09 02 a1 02 85 0b 75 01 95 06
   0.333644 25 01 05 85 09 d0 09 44 09 45 09 42 09 46 09 43 81 a2 09 d0 09 44 09 45 09
   0.333668 42 09 46 09 43 b1 a2 75 02 95 01 81 01 b1 01 c0 85 0c 05 84 09 5a 75 08 15
   0.333691 01 25 03 b1 a2 85 0d 09 fd 15 00 26 ff 00 b1 22 c0 05 84 09 1a a1 00 85 0e
   0.333714 05 84 09 40 75 08 67 21 d1 f0 00 55 07 b1 22 85 0f 09 30 b1 a2 85 10 09 53
   0.333737 15 5a 25 5a b1 22 09 54 16 8c 00 26 8c 00 b1 22 c0 09 1c a1 00 85 12 09 30
   0.333760 15 00 26 ff 00 b1 a2 65 00 55 00 85 13 09 35 b1 a2 85 14 09 58 25 06 b1 a2
   0.333783 85 15 09 57 75 10 15 ff 26 ff 7f 35 c4 47 c4 ff 1d 00 66 01 10 b1 a2 85 16
   0.333805 09 56 b1 a2 85 17 09 6e 75 01 15 00 25 01 35 00 45 00 65 00 b1 a2 09 65 b1
   0.333827 a2 75 06 b1 01 85 18 75 10 09 44 26 c2 01 66 21 d1 55 07 b1 a2 c0 c0
   0.333968 Using subdriver: CyberPower HID 0.3
   0.333986 Entering libusb_get_report
   0.336438 libusb_get_report: No error
   0.336501 Can't retrieve Report 01: Operation not permitted
   0.336529 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8
   0.336541 Entering libusb_get_report
   0.339438 libusb_get_report: No error
   0.339476 Can't retrieve Report 02: Operation not permitted
   0.339496 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x02, Offset: 0, Size: 8
   0.339508 Entering libusb_get_report
   0.341434 libusb_get_report: No error
   0.341469 Can't ...

Arnaud,
Here is what you have asked for.

Matt

•[x4linux:~] mmusgrove $ sudo service nut stop
[sudo] password for mmusgrove: 
 * Stopping Network UPS Tools                                                                                                                                                                            [ OK ] 
•[x4linux:~] mmusgrove $ export USB_DEBUG=3
•[x4linux:~] mmusgrove $ sudo /lib/nut/usbhid-ups -DDDD -a cyberpower
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
   0.000000	debug level is '4'
   0.001247	upsdrv_initups...
   0.290879	Checking device (0764/0501) (007/004)
   0.302437	- VendorID: 0764
   0.302466	- ProductID: 0501
   0.302477	- Manufacturer: CPS
   0.302487	- Product: UPS CP1000AVRLCD
   0.302496	- Serial Number: unknown
   0.302506	- Bus: 007
   0.302515	Trying to match device
   0.302571	Device matches
   0.307441	HID descriptor, method 1: (9 bytes) => 09 21 10 01 21 01 22 83 01
   0.307472	i=0, extra[i]=09, extra[i+1]=21
   0.307489	HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 01 22 83 01
   0.307500	HID descriptor length 387
   0.333436	Report Descriptor size = 387
   0.333478	Report Descriptor: (387 bytes) => 05 84 09 04 a1 01 09 24 a1 00 85 01 09 fe
   0.333504	 75 08 95 01 15 00 26 ff 00 b1 22 85 02 09 ff b1 22 85 03 05 85 09 89 b1 22
   0.333528	 85 04 09 8f b1 22 85 05 09 8b b1 22 85 06 09 2c b1 22 85 07 75 08 95 06 25
   0.333551	 78 09 83 09 8d 09 8e 09 8c 09 29 09 67 b1 22 85 08 75 08 95 01 65 00 09 66
   0.333574	 81 a2 09 66 b1 a2 09 68 75 10 27 ff ff 00 00 66 01 10 81 a2 09 68 b1 a2 09
   0.333597	 2a 26 58 02 81 a2 09 2a b1 a2 85 09 75 08 26 ff 00 05 84 09 40 67 21 d1 f0
   0.333621	 00 55 06 b1 22 85 0a 09 30 b1 a2 65 00 55 00 09 02 a1 02 85 0b 75 01 95 06
   0.333644	 25 01 05 85 09 d0 09 44 09 45 09 42 09 46 09 43 81 a2 09 d0 09 44 09 45 09
   0.333668	 42 09 46 09 43 b1 a2 75 02 95 01 81 01 b1 01 c0 85 0c 05 84 09 5a 75 08 15
   0.333691	 01 25 03 b1 a2 85 0d 09 fd 15 00 26 ff 00 b1 22 c0 05 84 09 1a a1 00 85 0e
   0.333714	 05 84 09 40 75 08 67 21 d1 f0 00 55 07 b1 22 85 0f 09 30 b1 a2 85 10 09 53
   0.333737	 15 5a 25 5a b1 22 09 54 16 8c 00 26 8c 00 b1 22 c0 09 1c a1 00 85 12 09 30
   0.333760	 15 00 26 ff 00 b1 a2 65 00 55 00 85 13 09 35 b1 a2 85 14 09 58 25 06 b1 a2
   0.333783	 85 15 09 57 75 10 15 ff 26 ff 7f 35 c4 47 c4 ff 1d 00 66 01 10 b1 a2 85 16
   0.333805	 09 56 b1 a2 85 17 09 6e 75 01 15 00 25 01 35 00 45 00 65 00 b1 a2 09 65 b1
   0.333827	 a2 75 06 b1 01 85 18 75 10 09 44 26 c2 01 66 21 d1 55 07 b1 a2 c0 c0
   0.333968	Using subdriver: CyberPower HID 0.3
   0.333986	Entering libusb_get_report
   0.336438	libusb_get_report: No error
   0.336501	Can't retrieve Report 01: Operation not permitted
   0.336529	Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8
   0.336541	Entering libusb_get_report
   0.339438	libusb_get_report: No error
   0.339476	Can't retrieve Report 02: Operation not permitted
   0.339496	Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x02, Offset: 0, Size: 8
   0.339508	Entering libusb_get_report
   0.341434	libusb_get_report: No error
   0.341469	Can't retrieve Report 03: Operation not permitted
   0.341487	Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x03, Offset: 0, Size: 8
   0.341499	Entering libusb_get_report
   0.343430	libusb_get_report: No error
   0.343462	Can't retrieve Report 04: Operation not permitted
   0.343479	Path: UPS.PowerSummary.iOEMInformation, Type: Feature, ReportID: 0x04, Offset: 0, Size: 8
   0.343491	Entering libusb_get_report
   0.345429	libusb_get_report: No error
   0.345461	Can't retrieve Report 05: Operation not permitted
   0.345479	Path: UPS.PowerSummary.Rechargeable, Type: Feature, ReportID: 0x05, Offset: 0, Size: 8
   0.345490	Entering libusb_get_report
   0.347429	libusb_get_report: No error
   0.347461	Can't retrieve Report 06: Operation not permitted
   0.347478	Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID: 0x06, Offset: 0, Size: 8
   0.347488	Entering libusb_get_report
   0.349429	libusb_get_report: No error
   0.349461	Can't retrieve Report 07: Operation not permitted
   0.349478	Path: UPS.PowerSummary.DesignCapacity, Type: Feature, ReportID: 0x07, Offset: 0, Size: 8
   0.349489	Entering libusb_get_report
   0.351415	libusb_get_report: No error
   0.351451	Can't retrieve Report 07: Operation not permitted
   0.351470	Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, ReportID: 0x07, Offset: 8, Size: 8
   0.351482	Entering libusb_get_report
   0.353429	libusb_get_report: No error
   0.353461	Can't retrieve Report 07: Operation not permitted
   0.353479	Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature, ReportID: 0x07, Offset: 16, Size: 8
   0.353490	Entering libusb_get_report
   0.355429	libusb_get_report: No error
   0.355461	Can't retrieve Report 07: Operation not permitted
   0.355478	Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature, ReportID: 0x07, Offset: 24, Size: 8
   0.355489	Entering libusb_get_report
   0.357428	libusb_get_report: No error
   0.357461	Can't retrieve Report 07: Operation not permitted
   0.357478	Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, ReportID: 0x07, Offset: 32, Size: 8
   0.357489	Entering libusb_get_report
   0.359428	libusb_get_report: No error
   0.359461	Can't retrieve Report 07: Operation not permitted
   0.359478	Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, ReportID: 0x07, Offset: 40, Size: 8
   0.359489	Entering libusb_get_report
   0.362431	libusb_get_report: No error
   0.362471	Can't retrieve Report 08: Operation not permitted
   0.362504	Path: UPS.PowerSummary.RemainingCapacity, Type: Input, ReportID: 0x08, Offset: 0, Size: 8
   0.362516	Entering libusb_get_report
   0.364420	libusb_get_report: No error
   0.364453	Can't retrieve Report 08: Operation not permitted
   0.364471	Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, ReportID: 0x08, Offset: 0, Size: 8
   0.364482	Entering libusb_get_report
   0.367426	libusb_get_report: No error
   0.367462	Can't retrieve Report 08: Operation not permitted
   0.367480	Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x08, Offset: 8, Size: 16
   0.367491	Entering libusb_get_report
   0.369432	libusb_get_report: No error
   0.369469	Can't retrieve Report 08: Operation not permitted
   0.369489	Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x08, Offset: 8, Size: 16
   0.369501	Entering libusb_get_report
   0.372409	libusb_get_report: No error
   0.372422	Can't retrieve Report 08: Operation not permitted
   0.372428	Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, ReportID: 0x08, Offset: 24, Size: 16
   0.372431	Entering libusb_get_report
   0.374406	libusb_get_report: No error
   0.374417	Can't retrieve Report 08: Operation not permitted
   0.374422	Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, ReportID: 0x08, Offset: 24, Size: 16
   0.374426	Entering libusb_get_report
   0.376407	libusb_get_report: No error
   0.376419	Can't retrieve Report 09: Operation not permitted
   0.376424	Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x09, Offset: 0, Size: 8
   0.376427	Entering libusb_get_report
   0.378405	libusb_get_report: No error
   0.378416	Can't retrieve Report 0a: Operation not permitted
   0.378421	Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 8
   0.378424	Entering libusb_get_report
   0.381407	libusb_get_report: No error
   0.381420	Can't retrieve Report 0b: Operation not permitted
   0.381425	Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x0b, Offset: 0, Size: 1
   0.381429	Entering libusb_get_report
   0.383405	libusb_get_report: No error
   0.383416	Can't retrieve Report 0b: Operation not permitted
   0.383421	Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x0b, Offset: 1, Size: 1
   0.383425	Entering libusb_get_report
   0.386400	libusb_get_report: No error
   0.386413	Can't retrieve Report 0b: Operation not permitted
   0.386418	Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x0b, Offset: 2, Size: 1
   0.386421	Entering libusb_get_report
   0.388404	libusb_get_report: No error
   0.388415	Can't retrieve Report 0b: Operation not permitted
   0.388420	Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x0b, Offset: 3, Size: 1
   0.388424	Entering libusb_get_report
   0.390404	libusb_get_report: No error
   0.390415	Can't retrieve Report 0b: Operation not permitted
   0.390420	Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input, ReportID: 0x0b, Offset: 4, Size: 1
   0.390423	Entering libusb_get_report
   0.393437	libusb_get_report: No error
   0.393475	Can't retrieve Report 0b: Operation not permitted
   0.393493	Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x0b, Offset: 5, Size: 1
   0.393504	Entering libusb_get_report
   0.395428	libusb_get_report: No error
   0.395460	Can't retrieve Report 0b: Operation not permitted
   0.395477	Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x0b, Offset: 0, Size: 1
   0.395489	Entering libusb_get_report
   0.398432	libusb_get_report: No error
   0.398468	Can't retrieve Report 0b: Operation not permitted
   0.398485	Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x0b, Offset: 1, Size: 1
   0.398496	Entering libusb_get_report
   0.400428	libusb_get_report: No error
   0.400460	Can't retrieve Report 0b: Operation not permitted
   0.400477	Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, ReportID: 0x0b, Offset: 2, Size: 1
   0.400488	Entering libusb_get_report
   0.402427	libusb_get_report: No error
   0.402459	Can't retrieve Report 0b: Operation not permitted
   0.402477	Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x0b, Offset: 3, Size: 1
   0.402488	Entering libusb_get_report
   0.404434	libusb_get_report: No error
   0.404473	Can't retrieve Report 0b: Operation not permitted
   0.404492	Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Feature, ReportID: 0x0b, Offset: 4, Size: 1
   0.404504	Entering libusb_get_report
   0.406427	libusb_get_report: No error
   0.406466	Can't retrieve Report 0b: Operation not permitted
   0.406485	Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Feature, ReportID: 0x0b, Offset: 5, Size: 1
   0.406498	Entering libusb_get_report
   0.408428	libusb_get_report: No error
   0.408460	Can't retrieve Report 0c: Operation not permitted
   0.408476	Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x0c, Offset: 0, Size: 8
   0.408488	Entering libusb_get_report
   0.410431	libusb_get_report: No error
   0.410466	Can't retrieve Report 0d: Operation not permitted
   0.410483	Path: UPS.PowerSummary.iManufacturer, Type: Feature, ReportID: 0x0d, Offset: 0, Size: 8
   0.410494	Entering libusb_get_report
   0.413431	libusb_get_report: No error
   0.413464	Can't retrieve Report 0e: Operation not permitted
   0.413481	Path: UPS.Input.ConfigVoltage, Type: Feature, ReportID: 0x0e, Offset: 0, Size: 8
   0.413492	Entering libusb_get_report
   0.416424	libusb_get_report: No error
   0.416459	Can't retrieve Report 0f: Operation not permitted
   0.416477	Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x0f, Offset: 0, Size: 8
   0.416488	Entering libusb_get_report
   0.419418	libusb_get_report: No error
   0.419451	Can't retrieve Report 10: Operation not permitted
   0.419468	Path: UPS.Input.LowVoltageTransfer, Type: Feature, ReportID: 0x10, Offset: 0, Size: 8
   0.419480	Entering libusb_get_report
   0.421424	libusb_get_report: No error
   0.421459	Can't retrieve Report 10: Operation not permitted
   0.421476	Path: UPS.Input.HighVoltageTransfer, Type: Feature, ReportID: 0x10, Offset: 8, Size: 8
   0.421487	Entering libusb_get_report
   0.423418	libusb_get_report: No error
   0.423450	Can't retrieve Report 12: Operation not permitted
   0.423466	Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x12, Offset: 0, Size: 8
   0.423477	Entering libusb_get_report
   0.425438	libusb_get_report: No error
   0.425476	Can't retrieve Report 13: Operation not permitted
   0.425495	Path: UPS.Output.PercentLoad, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8
   0.425506	Entering libusb_get_report
   0.427431	libusb_get_report: No error
   0.427467	Can't retrieve Report 14: Operation not permitted
   0.427484	Path: UPS.Output.Test, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8
   0.427495	Entering libusb_get_report
   0.430427	libusb_get_report: No error
   0.430459	Can't retrieve Report 15: Operation not permitted
   0.430476	Path: UPS.Output.DelayBeforeShutdown, Type: Feature, ReportID: 0x15, Offset: 0, Size: 16
   0.430487	Entering libusb_get_report
   0.432431	libusb_get_report: No error
   0.432464	Can't retrieve Report 16: Operation not permitted
   0.432481	Path: UPS.Output.DelayBeforeStartup, Type: Feature, ReportID: 0x16, Offset: 0, Size: 16
   0.432492	Entering libusb_get_report
   0.434434	libusb_get_report: No error
   0.434471	Can't retrieve Report 17: Operation not permitted
   0.434488	Path: UPS.Output.Boost, Type: Feature, ReportID: 0x17, Offset: 0, Size: 1
   0.434499	Entering libusb_get_report
   0.436431	libusb_get_report: No error
   0.436467	Can't retrieve Report 17: Operation not permitted
   0.436484	Path: UPS.Output.Overload, Type: Feature, ReportID: 0x17, Offset: 1, Size: 1
   0.436495	Entering libusb_get_report
   0.439431	libusb_get_report: No error
   0.439467	Can't retrieve Report 18: Operation not permitted
   0.439483	Path: UPS.Output.ConfigActivePower, Type: Feature, ReportID: 0x18, Offset: 0, Size: 16
   0.439546	Report descriptor retrieved (Reportlen = 387)
   0.439557	Found HID device
   0.439569	Detected a UPS: CPS/UPS CP1000AVRLCD
   0.439603	string_to_path: depth = 3
   0.439615	Entering libusb_get_report
   0.441431	libusb_get_report: No error
   0.441465	Can't retrieve Report 03: Operation not permitted
   0.441477	Can't initialize data from HID UPS

•[x4linux:~] mmusgrove $ dpkg -l '*libusb*' 
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                           Version                                        Description
+++-==============================================-==============================================-============================================================================================================
un  ia32-libusb-0.1-4                              <none>                                         (no description available)
ii  libusb-0.1-4                                   2:0.1.12-17                                    userspace USB programming library
ii  libusb-1.0-0                                   2:1.0.8-2                                      userspace USB programming library
un  libusb0                                        <none>                                         (no description available)
ii  libusbmuxd1                                    1.0.7-1                                        USB multiplexor daemon for iPhone and iPod Touch devices - library

Revision history for this message

Arnaud Quette (aquette) wrote on 2011-05-10: Re: [Bug 779512] Re: nut-2.6.0-1ubuntu3 behavior regression

#4

Hi Matt,

2011/5/10 Mr. Muskrat <email address hidden>

> Arnaud,
> Here is what you have asked for.
>
> Matt
>
>
> •[x4linux:~] mmusgrove $ sudo service nut stop
> [sudo] password for mmusgrove:
> * Stopping Network UPS Tools
>
> [ OK ]
> •[x4linux:~] mmusgrove $ export USB_DEBUG=3
> •[x4linux:~] mmusgrove $ sudo /lib/nut/usbhid-ups -DDDD -a cyberpower
>

can you please try again with:
$ sudo /lib/nut/usbhid-ups -u root -DDDD -a cyberpower

I was thinking about the report size issue, but you're there hitting a
permissions one...

cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Revision history for this message

Mr. Muskrat (mr-muskrat) wrote on 2011-05-11:

#5

usbhid-ups.txt Edit (1.0 MiB, text/plain)

Arnaud,
I hope that I captured enough of the information for you.

Matt

Revision history for this message

Arnaud Quette (aquette) wrote on 2011-05-11:

#6

2011/5/11 Mr. Muskrat <email address hidden>

> Arnaud,
> I hope that I captured enough of the information for you.
>

thanks Matt.

I'm still trying to find a solution that would satisfy everybody. not that
easy!
would you be able to test an svn version (just a checkout and minimum
compilation to run the driver in debug mode)?

cheers,
Arno

Revision history for this message

Mr. Muskrat (mr-muskrat) wrote on 2011-05-11:

#7

Certainly!

Revision history for this message

Arnaud Quette (aquette) wrote on 2011-05-12:

#8

2011/5/11 Mr. Muskrat <email address hidden>

> Certainly!
>

excellent, here we go:

$ svn co svn://svn.debian.org/nut/trunk
$ ./autogen.sh
$ ./configure --prefix=/usr \
            --exec-prefix=/ \
            --sysconfdir=/etc/nut \
            --mandir=/usr/share/man \
            --libdir=/lib \
            --includedir=/usr/include \$ sudo
            --without-all \
            --with-usb \
            --enable-static \
            --with-statepath=/var/run/nut \
            --with-altpidpath=/var/run/nut \
            --with-drvpath=/lib/nut \
            --with-pidpath=/var/run/nut \
            --datadir=/usr/share/nut \
            --with-user=nut --with-group=nut

$ sudo ./drivers/usbhid-ups -u root -DDDD -a cyberpower

@Fred: can you please do the same with Troy, and send (only to) me the
output.

We should have sufficient validation with that.
Note that a 2 mn run is sufficient...

cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Revision history for this message

Mr. Muskrat (mr-muskrat) wrote on 2011-05-13:

#9

usbhid-ups.txt Edit (182.1 KiB, text/plain; charset=US-ASCII; name="usbhid-ups.txt")

Download full text (21.2 KiB)

I thought I'd be able to just copy/paste the instructions one at a time
but I hit a few snags. I installed the missing prereqs and continued on.

•[x4linux:~/nut] mmusgrove $ ./autogen.sh
bash: ./autogen.sh: No such file or directory
•[x4linux:~/nut] mmusgrove $ ls
trunk
•[x4linux:~/nut] mmusgrove $ cd trunk/
/home/mmusgrove/nut/trunk
•[x4linux:~/nut/trunk] mmusgrove $ ./autogen.sh
Regenerating Augeas ups.conf lens...
/home/mmusgrove/nut/trunk/scripts/augeas
Regenerating the USB helper files...
/home/mmusgrove/nut/trunk/tools
Calling autoreconf...
./autogen.sh: 35: autoreconf: not found
•[x4linux:~/nut/trunk] mmusgrove $ sudo apt-get install autoconf
•[x4linux:~/nut/trunk] mmusgrove $ ./autogen.sh
Calling autoreconf...
Can't exec "libtoolize": No such file or directory at /usr/bin/autoreconf
line 196.
Use of uninitialized value in pattern match (m//) at /usr/bin/autoreconf
line 196.
configure.in:83: error: possibly undefined macro: AC_PROG_LIBTOOL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.in:496: error: possibly undefined macro: AC_DISABLE_STATIC
autoreconf: /usr/bin/autoconf failed with exit status: 1
•[x4linux:~/nut/trunk] mmusgrove $ sudo apt-get install libtool
•[x4linux:~/nut/trunk] mmusgrove $ ./autogen.sh
Calling autoreconf...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./config.guess'
libtoolize: copying file `./config.sub'
libtoolize: copying file `./install-sh'
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
configure.in:14: installing `./missing'
clients/Makefile.am: installing `./depcomp'
•[x4linux:~/nut/trunk] mmusgrove $ ./configure --prefix=/usr \
> --exec-prefix=/ \
> --sysconfdir=/etc/nut \
> --mandir=/usr/share/man \
> --libdir=/lib \
> --includedir=/usr/include \$ sudo
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: $
configure: WARNING: you should use --build, --host, --target
Network UPS Tools version 2.6.0
checking build system type... Invalid configuration `$': machine `$' not
recognized
configure: error: /bin/bash ./config.sub $ failed
•[x4linux:~/nut/trunk] mmusgrove $ --without-all \
> --with-usb \
> --enable-static \
> --with-statepath=/var/run/nut \
> --with-altpidpath=/var/run/nut \
> --with-drvpath=/lib/nut \
> --with-pidpath=/var/run/nut \
> --datadir=/usr/share/nut \
> --with-user=nut --with-group=nut
--without-all: command not found
•[x4linux:~/nut/trunk] mmusgrove $ ./configure --prefix=/usr \
> --exec-prefix=/ \
> --sysconfdir=/etc/nut \
> --mandir=/usr/share/man \
> --libdir=/lib \
> --includedir=/usr/include \
> --without-all \
> --with-usb \
> --enable-st...

I thought I'd be able to just copy/paste the instructions one at a time
but I hit a few snags. I installed the missing prereqs and continued on.

•[x4linux:~/nut] mmusgrove $ ./autogen.sh
bash: ./autogen.sh: No such file or directory
•[x4linux:~/nut] mmusgrove $ ls
trunk
•[x4linux:~/nut] mmusgrove $ cd trunk/
/home/mmusgrove/nut/trunk
•[x4linux:~/nut/trunk] mmusgrove $ ./autogen.sh
Regenerating Augeas ups.conf lens...
/home/mmusgrove/nut/trunk/scripts/augeas
Regenerating the USB helper files...
/home/mmusgrove/nut/trunk/tools
Calling autoreconf...
./autogen.sh: 35: autoreconf: not found
•[x4linux:~/nut/trunk] mmusgrove $ sudo apt-get install autoconf
•[x4linux:~/nut/trunk] mmusgrove $ ./autogen.sh
Calling autoreconf...
Can't exec "libtoolize": No such file or directory at /usr/bin/autoreconf
line 196.
Use of uninitialized value in pattern match (m//) at /usr/bin/autoreconf
line 196.
configure.in:83: error: possibly undefined macro: AC_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:496: error: possibly undefined macro: AC_DISABLE_STATIC
autoreconf: /usr/bin/autoconf failed with exit status: 1
•[x4linux:~/nut/trunk] mmusgrove $ sudo apt-get install libtool
•[x4linux:~/nut/trunk] mmusgrove $ ./autogen.sh
Calling autoreconf...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./config.guess'
libtoolize: copying file `./config.sub'
libtoolize: copying file `./install-sh'
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
configure.in:14: installing `./missing'
clients/Makefile.am: installing `./depcomp'
•[x4linux:~/nut/trunk] mmusgrove $ ./configure --prefix=/usr \
>            --exec-prefix=/ \
>            --sysconfdir=/etc/nut \
>            --mandir=/usr/share/man \
>            --libdir=/lib \
>            --includedir=/usr/include \$ sudo
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: $
configure: WARNING: you should use --build, --host, --target
Network UPS Tools version 2.6.0
checking build system type... Invalid configuration `$': machine `$' not
recognized
configure: error: /bin/bash ./config.sub $ failed
•[x4linux:~/nut/trunk] mmusgrove $            --without-all \
>            --with-usb \
>            --enable-static \
>            --with-statepath=/var/run/nut \
>            --with-altpidpath=/var/run/nut \
>            --with-drvpath=/lib/nut \
>            --with-pidpath=/var/run/nut \
>            --datadir=/usr/share/nut \
>            --with-user=nut --with-group=nut
--without-all: command not found
•[x4linux:~/nut/trunk] mmusgrove $ ./configure --prefix=/usr \
>            --exec-prefix=/ \
>            --sysconfdir=/etc/nut \
>            --mandir=/usr/share/man \
>            --libdir=/lib \
>            --includedir=/usr/include \
>            --without-all \
>            --with-usb \
>            --enable-static \
>            --with-statepath=/var/run/nut \
>            --with-altpidpath=/var/run/nut \
>            --with-drvpath=/lib/nut \
>            --with-pidpath=/var/run/nut \
>            --datadir=/usr/share/nut \
>            --with-user=nut --with-group=nut
Network UPS Tools version 2.6.0
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for host system name... ubuntu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for autoconf macro to enable system extensions... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking whether gcc and cc understand -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for egrep... (cached) /bin/grep -E
checking for ar... /usr/bin/ar
checking for ranlib... ranlib
checking whether byte ordering is bigendian... no
checking for inline... inline
checking for flexible array members... yes
checking for variable-length arrays... yes
checking for flock... yes
checking for lockf... yes
checking for fcvt... yes
checking for fcvtl... no
checking for cfsetispeed... yes
checking for tcsendbreak... yes
checking for seteuid... yes
checking for setsid... yes
checking for getpassphrase... no
checking for on_exit... yes
checking for strptime... yes
checking for setlogmask... yes
checking whether LOG_UPTO is declared... yes
checking for vsnprintf... yes
checking for snprintf... yes
checking for setenv... yes
checking for strerror... yes
checking for atexit... yes
checking whether optind is declared... yes
checking whether uu_lock is declared... no
checking whether __func__ is declared... yes
checking for library containing gethostbyname... none required
checking for library containing connect... none required
checking whether time.h and sys/time.h may both be included... yes
checking for sys/modem.h... no
checking for stdarg.h... yes
checking for varargs.h... no
checking for sys/termios.h... yes
checking for sys/time.h... yes
checking for socklen_t... yes
checking for --with-all... "no"
checking for Net-SNMP version via net-snmp-config... 5.4.3 found
checking for Net-SNMP cflags... -DNETSNMP_ENABLE_IPV6 -g -O2
-DNETSNMP_USE_INLINE -Ulinux -Dlinux=linux -D_REENTRANT -D_GNU_SOURCE
-DDEBIAN -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl/5.10/CORE
-I/usr/include
checking for Net-SNMP libs... -Wl,-Bsymbolic-functions -L/usr/lib -lnetsnmp
checking for net-snmp/net-snmp-config.h... no
checking for init_snmp... no
checking for libusb version via pkg-config... checking via libusb-config...
none found
checking for libusb cflags...
checking for libusb ldflags... -lusb
checking for usb.h... no
checking for usb_init... no
checking for libhal version via pkg-config (0.5.8 minimum required)... none
found
checking for libhal cflags... -DDBUS_API_SUBJECT_TO_CHANGE
-I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
checking for libhal ldflags... -lhal -ldbus-1 -lpthread
checking for libhal.h... no
checking for glib.h... no
checking for dbus/dbus-glib.h... no
checking for libhal_device_new_changeset... no
checking for libneon version via pkg-config (0.25.0 minimum required)...
none found
checking for libneon cflags...
checking for libneon ldflags...
checking for ne_xmlreq.h... no
checking for ne_xml_dispatch_request... no
checking for libpowerman cflags...
checking for libpowerman libs...
checking for libpowerman.h... no
checking for pm_connect... no
checking whether to build serial drivers... no
configure: error: "USB drivers requested, but libusb not found."
•[x4linux:~/nut/trunk] mmusgrove $ sudo apt-get install libusb-dev
•[x4linux:~/nut/trunk] mmusgrove $ ./configure --prefix=/usr \
>            --exec-prefix=/ \
>            --sysconfdir=/etc/nut \
>            --mandir=/usr/share/man \
>            --libdir=/lib \
>            --includedir=/usr/include \
>            --without-all \
>            --with-usb \
>            --enable-static \
>            --with-statepath=/var/run/nut \
>            --with-altpidpath=/var/run/nut \
>            --with-drvpath=/lib/nut \
>            --with-pidpath=/var/run/nut \
>            --datadir=/usr/share/nut \
>            --with-user=nut --with-group=nut
Network UPS Tools version 2.6.0
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for host system name... ubuntu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for autoconf macro to enable system extensions... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking whether gcc and cc understand -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for egrep... (cached) /bin/grep -E
checking for ar... /usr/bin/ar
checking for ranlib... ranlib
checking whether byte ordering is bigendian... no
checking for inline... inline
checking for flexible array members... yes
checking for variable-length arrays... yes
checking for flock... yes
checking for lockf... yes
checking for fcvt... yes
checking for fcvtl... no
checking for cfsetispeed... yes
checking for tcsendbreak... yes
checking for seteuid... yes
checking for setsid... yes
checking for getpassphrase... no
checking for on_exit... yes
checking for strptime... yes
checking for setlogmask... yes
checking whether LOG_UPTO is declared... yes
checking for vsnprintf... yes
checking for snprintf... yes
checking for setenv... yes
checking for strerror... yes
checking for atexit... yes
checking whether optind is declared... yes
checking whether uu_lock is declared... no
checking whether __func__ is declared... yes
checking for library containing gethostbyname... none required
checking for library containing connect... none required
checking whether time.h and sys/time.h may both be included... yes
checking for sys/modem.h... no
checking for stdarg.h... yes
checking for varargs.h... no
checking for sys/termios.h... yes
checking for sys/time.h... yes
checking for socklen_t... yes
checking for --with-all... "no"
checking for Net-SNMP version via net-snmp-config... 5.4.3 found
checking for Net-SNMP cflags... -DNETSNMP_ENABLE_IPV6 -g -O2
-DNETSNMP_USE_INLINE -Ulinux -Dlinux=linux -D_REENTRANT -D_GNU_SOURCE
-DDEBIAN -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl/5.10/CORE
-I/usr/include
checking for Net-SNMP libs... -Wl,-Bsymbolic-functions -L/usr/lib -lnetsnmp
checking for net-snmp/net-snmp-config.h... no
checking for init_snmp... no
checking for libusb version via pkg-config... 0.1.12 found
checking for libusb cflags...
checking for libusb ldflags... -lusb
checking for usb.h... yes
checking for usb_init... yes
checking for usb_detach_kernel_driver_np... yes
checking for libhal version via pkg-config (0.5.8 minimum required)... none
found
checking for libhal cflags... -DDBUS_API_SUBJECT_TO_CHANGE
-I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
checking for libhal ldflags... -lhal -ldbus-1 -lpthread
checking for libhal.h... no
checking for glib.h... no
checking for dbus/dbus-glib.h... no
checking for libhal_device_new_changeset... no
checking for libneon version via pkg-config (0.25.0 minimum required)...
none found
checking for libneon cflags...
checking for libneon ldflags...
checking for ne_xmlreq.h... no
checking for ne_xml_dispatch_request... no
checking for libpowerman cflags...
checking for libpowerman libs...
checking for libpowerman.h... no
checking for pm_connect... no
checking whether to build serial drivers... no
checking whether to build USB drivers... yes
checking whether to build SNMP drivers... no
checking whether to build neon based XML driver... no
checking whether to build Powerman PDU client driver... no
checking for openssl version via pkg-config... 0.9.8o found
checking for openssl cflags...
checking for openssl ldflags... -lssl -lcrypto
checking for openssl/ssl.h... yes
checking for SSL_library_init... yes
checking whether to enable SSL development code... yes
checking for tcpd.h... no
checking for library containing yp_get_default_domain... -lnsl
checking for library containing request_init... no
checking whether to enable libwrap (tcp-wrappers) support... no
checking whether to build CGI programs... no
checking whether to enable HAL support... no
checking for asciidoc... no
checking for a2x... no
checking for dblatex... no
checking if asciidoc version can build website (minimum required 8.6.3)...
no
checking if a2x version can build website (minimum required 8.6.3)... no
checking whether to build and install documentation... no
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... /usr/bin/ar
checking for strip... strip
checking for ranlib... (cached) ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether to build and install the development files... no
checking state path... /var/run/nut
checking alt pid path... /var/run/nut
checking driver path... /lib/nut
checking cgi path... ${exec_prefix}/cgi-bin
checking html path... ${prefix}/html
checking pidpath... /var/run/nut
checking network port number... 3493
checking user to run as... nut
checking group membership of user to run as... nut
checking facility for syslog... LOG_DAEMON
checking which drivers to build... all available
checking which driver man pages to install... all available
checking whether to strip debug symbols... no
checking whether to install pkg-config *.pc files... using
${libdir}/pkgconfig
checking whether to install hotplug rules... no
checking whether to install udev rules... using /lib/udev
checking for asciidoc... no
checking for a2x... no
configure: creating ./config.status
config.status: creating clients/Makefile
config.status: creating common/Makefile
config.status: creating conf/Makefile
config.status: creating conf/upssched.conf.sample
config.status: creating data/html/header.html
config.status: creating data/html/Makefile
config.status: creating data/Makefile
config.status: creating data/driver.list
config.status: creating docs/Makefile
config.status: creating docs/man/Makefile
config.status: creating docs/website/Makefile
config.status: creating drivers/Makefile
config.status: creating include/Makefile
config.status: creating lib/libupsclient-config
config.status: creating lib/libupsclient.pc
config.status: creating lib/Makefile
config.status: creating scripts/augeas/Makefile
config.status: creating scripts/augeas/nutnutconf.aug
config.status: creating scripts/augeas/nutupsconf.aug
config.status: creating scripts/augeas/nutupsdconf.aug
config.status: creating scripts/augeas/nutupsdusers.aug
config.status: creating scripts/augeas/nutupsmonconf.aug
config.status: creating scripts/augeas/nutupsschedconf.aug
config.status: creating scripts/augeas/nuthostsconf.aug
config.status: creating scripts/augeas/nutupssetconf.aug
config.status: creating scripts/hal/Makefile
config.status: creating scripts/hal/ups-nut-device.fdi
config.status: creating scripts/hotplug/Makefile
config.status: creating scripts/hotplug/libhidups
config.status: creating scripts/python/Makefile
config.status: creating scripts/udev/Makefile
config.status: creating scripts/udev/nut-usbups.rules
config.status: creating scripts/Makefile
config.status: creating server/Makefile
config.status: creating tools/Makefile
config.status: creating Makefile
config.status: creating include/config.h
config.status: executing depfiles commands
config.status: executing libtool commands

Configuration summary:
======================
build serial drivers: no
build USB drivers: yes
build SNMP drivers: no
build neon based XML driver: no
build Powerman PDU client driver: no
enable SSL development code: yes
enable libwrap (tcp-wrappers) support: no
build CGI programs: no
enable HAL support: no
build and install documentation: no
build and install the development files: no
•[x4linux:~/nut/trunk] mmusgrove $ make
•[x4linux:~/nut/trunk] mmusgrove $ sudo ./drivers/usbhid-ups -u root -DDDD
-a cyberpower 2>&1 | tee /tmp/usbhid-ups.txt

Matt

On Thu, May 12, 2011 at 2:17 PM, Arnaud Quette <aquette.dev@gmail.com>wrote:

> 2011/5/11 Mr. Muskrat <779512@bugs.launchpad.net>
>
> > Certainly!
> >
>
> excellent, here we go:
>
> $  svn co svn://svn.debian.org/nut/trunk
> $ ./autogen.sh
> $ ./configure --prefix=/usr \
>            --exec-prefix=/ \
>            --sysconfdir=/etc/nut \
>            --mandir=/usr/share/man \
>            --libdir=/lib \
>            --includedir=/usr/include \$ sudo
>            --without-all \
>            --with-usb \
>            --enable-static \
>            --with-statepath=/var/run/nut \
>            --with-altpidpath=/var/run/nut \
>            --with-drvpath=/lib/nut \
>            --with-pidpath=/var/run/nut \
>            --datadir=/usr/share/nut \
>            --with-user=nut --with-group=nut
>
> $ sudo ./drivers/usbhid-ups -u root -DDDD -a cyberpower
>
> @Fred: can you please do the same with Troy, and send (only to) me the
> output.
>
> We should have sufficient validation with that.
> Note that a 2 mn run is sufficient...
>
> cheers,
> Arnaud
> --
> Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
> Debian Developer - http://www.debian.org
> Free Software Developer - http://arnaud.quette.free.fr/
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/779512
>
> Title:
>  nut-2.6.0-1ubuntu3 behavior regression
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscribe
>

Revision history for this message

Mr. Muskrat (mr-muskrat) wrote on 2011-05-13:

#10

I thought I'd be able to just copy/paste the instructions one at a time but I hit a few snags. I installed the missing prereqs and continued on. (See config.txt.)

Revision history for this message

Mr. Muskrat (mr-muskrat) wrote on 2011-05-13:

#11

usbhid-ups.txt Edit (182.1 KiB, text/plain)

The output from the run is in usbhid-ups.txt.

Revision history for this message

Mr. Muskrat (mr-muskrat) wrote on 2011-05-13:

#12

config.txt Edit (19.5 KiB, text/plain)

(config.txt didn't get uploaded the first time)

Revision history for this message

Arnaud Quette (aquette) wrote on 2011-05-13:

#13

Hey Matt,

2011/5/13 Mr. Muskrat <email address hidden>

> I thought I'd be able to just copy/paste the instructions one at a time
> but I hit a few snags. I installed the missing prereqs and continued on.
> (...)
>

hem, sorry. I should have given you more info on build-deps and more
generally....
well, the point is that you found your way (congrats) and that everything
seems fixed on your side.
can you please confirm?

I'll do some more checking on my side, but 2.6.1 (soon to go out) will fix
your issue.
as a temporary solution, you may backup /lib/nut/usbhid-ups and replace it
with drivers/usbhid-ups, while waiting for an updated package.

cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Revision history for this message

Mr. Muskrat (mr-muskrat) wrote on 2011-05-13:

#14

Yes, I can confirm that this fixed the issue I reported. Arnaud, thank you
so much!

Matt

On Fri, May 13, 2011 at 3:18 PM, Arnaud Quette <email address hidden>wrote:

> Hey Matt,
>
> 2011/5/13 Mr. Muskrat <email address hidden>
>
> > I thought I'd be able to just copy/paste the instructions one at a time
> > but I hit a few snags. I installed the missing prereqs and continued on.
> > (...)
> >
>
> hem, sorry. I should have given you more info on build-deps and more
> generally....
> well, the point is that you found your way (congrats) and that everything
> seems fixed on your side.
> can you please confirm?
>
> I'll do some more checking on my side, but 2.6.1 (soon to go out) will fix
> your issue.
> as a temporary solution, you may backup /lib/nut/usbhid-ups and replace it
> with drivers/usbhid-ups, while waiting for an updated package.
>
> cheers,
> Arnaud
> --
> Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
> Debian Developer - http://www.debian.org
> Free Software Developer - http://arnaud.quette.free.fr/
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/779512
>
> Title:
> nut-2.6.0-1ubuntu3 behavior regression
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscribe
>

Revision history for this message

Arnaud Quette (aquette) wrote on 2011-05-14:

#15

2011/5/14 Mr. Muskrat <email address hidden>

> Yes, I can confirm that this fixed the issue I reported.

thanks for the confirmation

> Arnaud, thank you so much!
>

my pleasure Matt :)

Arnaud
--
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Chuck Short (zulcss) on 2011-05-16

Changed in nut (Ubuntu):
importance:	Undecided → Medium
status:	New → Triaged

Revision history for this message

Martin Ewing (martin-s-ewing) wrote on 2011-06-27:

#16

Download full text (4.2 KiB)

I have a very similar situation with my Belkin UPS on Natty (worked on previous release).

See

$ lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

martin@gimli:~$ aptitude show nut
Package: nut
State: installed
Automatically installed: no
Version: 2.6.0-1ubuntu3
...

sudo /lib/nut/usbhid-ups -DDDD -a mybelkin
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
   0.000000 debug level is '4'
   0.000583 upsdrv_initups...
   0.266176 Checking device (1D6B/0001) (008/001)
   0.266219 - VendorID: 1d6b
   0.266226 - ProductID: 0001
   0.266232 - Manufacturer: unknown
   0.266237 - Product: unknown
   0.266242 - Serial Number: unknown
   0.266247 - Bus: 008
   0.266252 Trying to match device
   0.266275 Device does not match - skipping
   0.266285 Checking device (1D6B/0001) (007/001)
   0.266303 - VendorID: 1d6b
   0.266309 - ProductID: 0001
   0.266315 - Manufacturer: unknown
   0.266320 - Product: unknown
   0.266325 - Serial Number: unknown
   0.266330 - Bus: 007
   0.266335 Trying to match device
   0.266341 Device does not match - skipping
   0.266349 Checking device (050D/1100) (006/002)
   0.291945 - VendorID: 050d
   0.291959 - ProductID: 1100
   0.291966 - Manufacturer: Belkin
   0.291972 - Product: Belkin UPS
   0.291977 - Serial Number: unknown
   0.291982 - Bus: 006
   0.291987 Trying to match device
   0.291995 Device matches
   0.301941 HID descriptor, method 1: (9 bytes) => 09 21 11 01 21 01 22 f2 01
   0.301962 i=0, extra[i]=09, extra[i+1]=21
   0.301972 HID descriptor, method 2: (9 bytes) => 09 21 11 01 21 01 22 f2 01
   0.301978 HID descriptor length 498
   0.372952 Report Descriptor size = 498
   0.372972 Report Descriptor: (498 bytes) => 05 84 09 04 a1 01 05 86 09 26 a1 02 85 01
   0.372985 75 08 95 01 15 00 26 ff 00 09 40 b1 02 85 02 09 42 b1 02 85 03 75 10 27 ff
   0.372996 ff 00 00 09 43 b1 02 85 04 09 44 b1 02 c0 05 86 09 29 a1 02 26 ff 00 85 0d
   0.373007 09 75 b1 02 85 0e 09 76 b1 02 85 0f 09 7c b1 02 c0 05 86 09 27 a1 02 85 10
   0.373018 75 08 95 01 26 ff 00 09 58 b1 02 85 11 09 5a b1 02 85 15 75 10 95 01 27 ff
   0.373029 ff 00 00 09 57 b1 02 85 16 09 56 b1 02 c0 05 86 09 2a a1 02 09 1a a1 02 85
   0.373040 18 75 10 95 01 27 ff ff 00 00 09 30 b1 02 85 19 09 32 b1 02 c0 09 1c a1 02
   0.373051 85 1b 75 10 95 01 27 ff ff 00 00 09 30 b1 02 85 1c 09 32 b1 02 85 1e 75 08
   0.373062 95 01 26 ff 00 09 35 b1 02 c0 c0 05 86 09 10 a1 02 05 86 85 20 75 10 95 01
   0.373074 27 ff ff 00 00 09 30 b1 02 85 21 75 08 95 01 26 ff 00 09 39 b1 02 c0 05 86
   0.373085 09 28 a1 02 85 22 75 10 95 01 27 ff ff 00 00 09 21 b1 02 85 23 75 08 95 01
   0.373096 26 ff 00 09 22 b1 02 c0 05 84 09 24 a1 00 85 28 09 fe 75 08 95 01 26 ff 00
   0.373107 b1 02 85 29 09 ff b1 02 05 85 85 2a 09 89 b1 02 85 2b 09 8f b1 02 85 2c 09
   0.373118 8b b1 02 85 2d 09 44 75 08 95 01 81 82 09 44 b1 82 85 2e 09 45 81 82 09 45
   0.373129 b1 82 05 84 85 30 09 40 75 10 95 01 27 fe ff 00 00 b1 02 85 31 09 30 b1 02
   0.373140 85 32 09 31 75 08 95 01 26 ff 00 b1 02 05 85 85 33 09 2c 75 08 95 01 26 ff
   0.373151 00 b1 02 85 34 09 66 81 82 09 66 b1 82 85 35 09 68 75 10 95 01 27 ff ff 00
...

I have a very similar situation with my Belkin UPS on Natty (worked on previous release).

See

$ lsb_release -rd
Description:	Ubuntu 11.04
Release:	11.04

martin@gimli:~$ aptitude show nut
Package: nut                             
State: installed
Automatically installed: no
Version: 2.6.0-1ubuntu3
...

sudo /lib/nut/usbhid-ups -DDDD -a mybelkin
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
   0.000000	debug level is '4'
   0.000583	upsdrv_initups...
   0.266176	Checking device (1D6B/0001) (008/001)
   0.266219	- VendorID: 1d6b
   0.266226	- ProductID: 0001
   0.266232	- Manufacturer: unknown
   0.266237	- Product: unknown
   0.266242	- Serial Number: unknown
   0.266247	- Bus: 008
   0.266252	Trying to match device
   0.266275	Device does not match - skipping
   0.266285	Checking device (1D6B/0001) (007/001)
   0.266303	- VendorID: 1d6b
   0.266309	- ProductID: 0001
   0.266315	- Manufacturer: unknown
   0.266320	- Product: unknown
   0.266325	- Serial Number: unknown
   0.266330	- Bus: 007
   0.266335	Trying to match device
   0.266341	Device does not match - skipping
   0.266349	Checking device (050D/1100) (006/002)
   0.291945	- VendorID: 050d
   0.291959	- ProductID: 1100
   0.291966	- Manufacturer: Belkin 
   0.291972	- Product: Belkin UPS
   0.291977	- Serial Number: unknown
   0.291982	- Bus: 006
   0.291987	Trying to match device
   0.291995	Device matches
   0.301941	HID descriptor, method 1: (9 bytes) => 09 21 11 01 21 01 22 f2 01
   0.301962	i=0, extra[i]=09, extra[i+1]=21
   0.301972	HID descriptor, method 2: (9 bytes) => 09 21 11 01 21 01 22 f2 01
   0.301978	HID descriptor length 498
   0.372952	Report Descriptor size = 498
   0.372972	Report Descriptor: (498 bytes) => 05 84 09 04 a1 01 05 86 09 26 a1 02 85 01
   0.372985	 75 08 95 01 15 00 26 ff 00 09 40 b1 02 85 02 09 42 b1 02 85 03 75 10 27 ff
   0.372996	 ff 00 00 09 43 b1 02 85 04 09 44 b1 02 c0 05 86 09 29 a1 02 26 ff 00 85 0d
   0.373007	 09 75 b1 02 85 0e 09 76 b1 02 85 0f 09 7c b1 02 c0 05 86 09 27 a1 02 85 10
   0.373018	 75 08 95 01 26 ff 00 09 58 b1 02 85 11 09 5a b1 02 85 15 75 10 95 01 27 ff
   0.373029	 ff 00 00 09 57 b1 02 85 16 09 56 b1 02 c0 05 86 09 2a a1 02 09 1a a1 02 85
   0.373040	 18 75 10 95 01 27 ff ff 00 00 09 30 b1 02 85 19 09 32 b1 02 c0 09 1c a1 02
   0.373051	 85 1b 75 10 95 01 27 ff ff 00 00 09 30 b1 02 85 1c 09 32 b1 02 85 1e 75 08
   0.373062	 95 01 26 ff 00 09 35 b1 02 c0 c0 05 86 09 10 a1 02 05 86 85 20 75 10 95 01
   0.373074	 27 ff ff 00 00 09 30 b1 02 85 21 75 08 95 01 26 ff 00 09 39 b1 02 c0 05 86
   0.373085	 09 28 a1 02 85 22 75 10 95 01 27 ff ff 00 00 09 21 b1 02 85 23 75 08 95 01
   0.373096	 26 ff 00 09 22 b1 02 c0 05 84 09 24 a1 00 85 28 09 fe 75 08 95 01 26 ff 00
   0.373107	 b1 02 85 29 09 ff b1 02 05 85 85 2a 09 89 b1 02 85 2b 09 8f b1 02 85 2c 09
   0.373118	 8b b1 02 85 2d 09 44 75 08 95 01 81 82 09 44 b1 82 85 2e 09 45 81 82 09 45
   0.373129	 b1 82 05 84 85 30 09 40 75 10 95 01 27 fe ff 00 00 b1 02 85 31 09 30 b1 02
   0.373140	 85 32 09 31 75 08 95 01 26 ff 00 b1 02 05 85 85 33 09 2c 75 08 95 01 26 ff
   0.373151	 00 b1 02 85 34 09 66 81 82 09 66 b1 82 85 35 09 68 75 10 95 01 27 ff ff 00
   0.373162	 00 81 82 09 68 b1 82 85 36 26 ff 00 75 08 95 01 09 83 b1 02 85 37 09 67 b1
   0.373173	 02 85 38 09 8c b1 02 85 39 09 8e b1 02 85 3a 09 29 b1 82 85 3b 09 8d b1 02
   0.373184	 85 3c 09 d0 b1 82 09 d0 81 82 85 3d 09 42 81 82 09 42 b1 82 85 3e 05 84 09
   0.373191	 69 81 82 09 69 b1 82 c0 c0
   0.373260	Using subdriver: Belkin HID 0.12
   0.373271	Entering libusb_get_report
   0.377944	libusb_get_report: error sending control message: Operation not permitted
   0.377965	Can't retrieve Report 01: Operation not permitted
   0.377984	Path: UPS.BELKINConfig.BELKINConfigVoltage, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8
   0.377991	Entering libusb_get_report
   0.383944	libusb_get_report: error sending control message: Operation not permitted
   0.383962	Can't retrieve Report 02: Operation not permitted
   0.383974	Path: UPS.BELKINConfig.BELKINConfigFrequency, Type: Feature, ReportID: 0x02, Offset: 0, Size: 8
   0.383981	Entering libusb_get_report
   0.388933	libusb_get_report: error sending control message: Operation not permitted
...

Is this the same bug?  Is there a fix?
Thanks!

Revision history for this message

TimMadden (timmadden) wrote on 2011-07-12:

#17

creating usbhid-ups from source did it for me. Thanks

Revision history for this message

Arnaud Quette (aquette) wrote on 2011-07-13:

#18

Hi Martin,

2011/6/27 Martin Ewing <email address hidden>

> I have a very similar situation with my Belkin UPS on Natty (worked on
> previous release).
>
> See
>
> $ lsb_release -rd
> Description: Ubuntu 11.04
> Release: 11.04
>
> martin@gimli:~$ aptitude show nut
> Package: nut
> State: installed
> Automatically installed: no
> Version: 2.6.0-1ubuntu3
> ...
>
> sudo /lib/nut/usbhid-ups -DDDD -a mybelkin
> Network UPS Tools - Generic HID driver 0.35 (2.6.0)
> USB communication driver 0.31
> 0.000000 debug level is '4'
> 0.000583 upsdrv_initups...
> 0.266176 Checking device (1D6B/0001) (008/001)
> 0.266219 - VendorID: 1d6b
> 0.266226 - ProductID: 0001
> 0.266232 - Manufacturer: unknown
> 0.266237 - Product: unknown
> 0.266242 - Serial Number: unknown
> 0.266247 - Bus: 008
> 0.266252 Trying to match device
> 0.266275 Device does not match - skipping
> 0.266285 Checking device (1D6B/0001) (007/001)
> 0.266303 - VendorID: 1d6b
> 0.266309 - ProductID: 0001
> 0.266315 - Manufacturer: unknown
> 0.266320 - Product: unknown
> 0.266325 - Serial Number: unknown
> 0.266330 - Bus: 007
> 0.266335 Trying to match device
> 0.266341 Device does not match - skipping
> 0.266349 Checking device (050D/1100) (006/002)
> 0.291945 - VendorID: 050d
> 0.291959 - ProductID: 1100
> 0.291966 - Manufacturer: Belkin
> 0.291972 - Product: Belkin UPS
> 0.291977 - Serial Number: unknown
> 0.291982 - Bus: 006
> 0.291987 Trying to match device
> 0.291995 Device matches
> (...)

0.383981 Entering libusb_get_report
> 0.388933 libusb_get_report: error sending control message: Operation
> not permitted
> ...
>
> Is this the same bug?

I don't think so.
the issue reported here was related to a code change, that resulted in a
regression.

yours seem to be with privileges.
to validate this, try launching the driver with root privs (note the "-u
root"):
$ sudo /lib/nut/usbhid-ups -u root -DDDD -a mybelkin

Is there a fix

it's related to udev, and since there seems to be quite some similar issues,
I'm wondering if there is a race condition between udev (started through
upstart native scripts) and nut (started through upstart sysV compat
script).

cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Hi Martin,

2011/6/27 Martin Ewing <martin.s.ewing@gmail.com>

> I have a very similar situation with my Belkin UPS on Natty (worked on
> previous release).
>
> See
>
> $ lsb_release -rd
> Description:    Ubuntu 11.04
> Release:        11.04
>
> martin@gimli:~$ aptitude show nut
> Package: nut
> State: installed
> Automatically installed: no
> Version: 2.6.0-1ubuntu3
> ...
>
> sudo /lib/nut/usbhid-ups -DDDD -a mybelkin
> Network UPS Tools - Generic HID driver 0.35 (2.6.0)
> USB communication driver 0.31
>    0.000000     debug level is '4'
>    0.000583     upsdrv_initups...
>   0.266176     Checking device (1D6B/0001) (008/001)
>   0.266219     - VendorID: 1d6b
>   0.266226     - ProductID: 0001
>   0.266232     - Manufacturer: unknown
>   0.266237     - Product: unknown
>   0.266242     - Serial Number: unknown
>   0.266247     - Bus: 008
>   0.266252     Trying to match device
>   0.266275     Device does not match - skipping
>   0.266285     Checking device (1D6B/0001) (007/001)
>   0.266303     - VendorID: 1d6b
>   0.266309     - ProductID: 0001
>   0.266315     - Manufacturer: unknown
>   0.266320     - Product: unknown
>   0.266325     - Serial Number: unknown
>   0.266330     - Bus: 007
>   0.266335     Trying to match device
>   0.266341     Device does not match - skipping
>   0.266349     Checking device (050D/1100) (006/002)
>   0.291945     - VendorID: 050d
>   0.291959     - ProductID: 1100
>   0.291966     - Manufacturer: Belkin
>   0.291972     - Product: Belkin UPS
>   0.291977     - Serial Number: unknown
>   0.291982     - Bus: 006
>   0.291987     Trying to match device
>   0.291995     Device matches
> (...)

0.383981     Entering libusb_get_report
>   0.388933     libusb_get_report: error sending control message: Operation
> not permitted
> ...
>
> Is this the same bug?

I don't think so.
the issue reported here was related to a code change, that resulted in a
regression.

yours seem to be with privileges.
to validate this, try launching the driver with root privs (note the "-u
root"):
$ sudo /lib/nut/usbhid-ups -u root -DDDD -a mybelkin

Is there a fix

it's related to udev, and since there seems to be quite some similar issues,
I'm wondering if there is a race condition between udev (started through
upstart native scripts) and nut (started through upstart sysV compat
script).

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Revision history for this message

Martin Ewing (martin-s-ewing) wrote on 2011-07-13:

#19

Download full text (25.3 KiB)

Arnaud,

Thanks for the reply! I imagine you are correct. I ran the command you
suggested (below). Apparently nut knows the device it should connect to,
but that device is "busy". And running as root doesn't overcome the
problem... (And I don't know why I should have to make /var/run/nut,
either.)

I am not well versed in Ubuntu bug reporting. Do you think I need to submit
this separately? Or should I just wait until the next release? (The lazy
way out.)

Thanks again,
Martin

martin@gimli:~$ sudo /lib/nut/usbhid-ups -u root -DDDD -a mybelkin
[sudo] password for martin:
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
   0.000000 debug level is '4'
   0.000580 Can't chdir to /var/run/nut: No such file or directory
martin@gimli:~$ sudo mkdir /var/run/nut
martin@gimli:~$ sudo /lib/nut/usbhid-ups -u root -DDDD -a mybelkin
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
   0.000000 debug level is '4'
   0.000546 upsdrv_initups...
   0.106579 Checking device (03F0/0317) (008/002)
   0.118917 - VendorID: 03f0
   0.118930 - ProductID: 0317
   0.118937 - Manufacturer: HewLett Packard
   0.118943 - Product: HP LaserJet 1200
   0.118948 - Serial Number: 00CNDL017843
   0.118953 - Bus: 008
   0.118958 Trying to match device
   0.118984 Device does not match - skipping
   0.118997 Checking device (1D6B/0001) (008/001)
   0.119031 - VendorID: 1d6b
   0.119038 - ProductID: 0001
   0.119043 - Manufacturer: Linux 2.6.38-8-generic uhci_hcd
   0.119048 - Product: UHCI Host Controller
   0.119053 - Serial Number: 0000:00:1d.2
   0.119059 - Bus: 008
   0.119063 Trying to match device
   0.119069 Device does not match - skipping
   0.119078 Checking device (0403/6001) (007/002)
   0.134688 - VendorID: 0403
   0.134702 - ProductID: 6001
   0.134709 - Manufacturer: ftdi
   0.134715 - Product: usb serial converter
   0.134721 - Serial Number: ftDWECKP
   0.134726 - Bus: 007
   0.134731 Trying to match device
   0.134738 Device does not match - skipping
   0.134748 Checking device (1D6B/0001) (007/001)
   0.134782 - VendorID: 1d6b
   0.134789 - ProductID: 0001
   0.134794 - Manufacturer: Linux 2.6.38-8-generic uhci_hcd
   0.134799 - Product: UHCI Host Controller
   0.134804 - Serial Number: 0000:00:1d.1
   0.134809 - Bus: 007
   0.134814 Trying to match device
   0.134820 Device does not match - skipping
   0.134828 Checking device (050D/1100) (006/002)
   0.160503 - VendorID: 050d
   0.160517 - ProductID: 1100
   0.160524 - Manufacturer: Belkin
   0.160530 - Product: Belkin UPS
   0.160536 - Serial Number: unknown
   0.160541 - Bus: 006
   0.160545 Trying to match device
   0.160553 Device matches
   0.160579 failed to claim USB device: could not claim interface 0:
Device or resource busy
   0.162665 detached kernel driver from USB device...
   0.173501 HID descriptor, method 1: (9 bytes) => 09 21 11 01 21 01 22
f2 01
   0.173518 i=0, extra[i]=09, extra[i+1]=21
   0.173528 HID descriptor, method 2: (9 bytes) => 09 21 11 01 21 01 22
f2...

Arnaud,

Thanks for the reply!  I imagine you are correct.  I ran the command you
suggested (below).  Apparently nut knows the device it should connect to,
but that device is "busy".  And running as root doesn't overcome the
problem...  (And I don't know why I should have to make /var/run/nut,
either.)

I am not well versed in Ubuntu bug reporting.  Do you think I need to submit
this separately?  Or should I just wait until the next release? (The lazy
way out.)

Thanks again,
Martin

martin@gimli:~$ sudo /lib/nut/usbhid-ups -u root -DDDD -a mybelkin
[sudo] password for martin:
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
   0.000000    debug level is '4'
   0.000580    Can't chdir to /var/run/nut: No such file or directory
martin@gimli:~$ sudo mkdir /var/run/nut
martin@gimli:~$ sudo /lib/nut/usbhid-ups -u root -DDDD -a mybelkin
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
   0.000000    debug level is '4'
   0.000546    upsdrv_initups...
   0.106579    Checking device (03F0/0317) (008/002)
   0.118917    - VendorID: 03f0
   0.118930    - ProductID: 0317
   0.118937    - Manufacturer: HewLett Packard
   0.118943    - Product: HP LaserJet 1200
   0.118948    - Serial Number: 00CNDL017843
   0.118953    - Bus: 008
   0.118958    Trying to match device
   0.118984    Device does not match - skipping
   0.118997    Checking device (1D6B/0001) (008/001)
   0.119031    - VendorID: 1d6b
   0.119038    - ProductID: 0001
   0.119043    - Manufacturer: Linux 2.6.38-8-generic uhci_hcd
   0.119048    - Product: UHCI Host Controller
   0.119053    - Serial Number: 0000:00:1d.2
   0.119059    - Bus: 008
   0.119063    Trying to match device
   0.119069    Device does not match - skipping
   0.119078    Checking device (0403/6001) (007/002)
   0.134688    - VendorID: 0403
   0.134702    - ProductID: 6001
   0.134709    - Manufacturer: ftdi
   0.134715    - Product: usb serial converter
   0.134721    - Serial Number: ftDWECKP
   0.134726    - Bus: 007
   0.134731    Trying to match device
   0.134738    Device does not match - skipping
   0.134748    Checking device (1D6B/0001) (007/001)
   0.134782    - VendorID: 1d6b
   0.134789    - ProductID: 0001
   0.134794    - Manufacturer: Linux 2.6.38-8-generic uhci_hcd
   0.134799    - Product: UHCI Host Controller
   0.134804    - Serial Number: 0000:00:1d.1
   0.134809    - Bus: 007
   0.134814    Trying to match device
   0.134820    Device does not match - skipping
   0.134828    Checking device (050D/1100) (006/002)
   0.160503    - VendorID: 050d
   0.160517    - ProductID: 1100
   0.160524    - Manufacturer: Belkin
   0.160530    - Product: Belkin UPS
   0.160536    - Serial Number: unknown
   0.160541    - Bus: 006
   0.160545    Trying to match device
   0.160553    Device matches
   0.160579    failed to claim USB device: could not claim interface 0:
Device or resource busy
   0.162665    detached kernel driver from USB device...
   0.173501    HID descriptor, method 1: (9 bytes) => 09 21 11 01 21 01 22
f2 01
   0.173518    i=0, extra[i]=09, extra[i+1]=21
   0.173528    HID descriptor, method 2: (9 bytes) => 09 21 11 01 21 01 22
f2 01
   0.173535    HID descriptor length 498
   0.243508    Report Descriptor size = 498
   0.243528    Report Descriptor: (498 bytes) => 05 84 09 04 a1 01 05 86 09
26 a1 02 85 01
   0.243541     75 08 95 01 15 00 26 ff 00 09 40 b1 02 85 02 09 42 b1 02 85
03 75 10 27 ff
   0.243553     ff 00 00 09 43 b1 02 85 04 09 44 b1 02 c0 05 86 09 29 a1 02
26 ff 00 85 0d
   0.243564     09 75 b1 02 85 0e 09 76 b1 02 85 0f 09 7c b1 02 c0 05 86 09
27 a1 02 85 10
   0.243575     75 08 95 01 26 ff 00 09 58 b1 02 85 11 09 5a b1 02 85 15 75
10 95 01 27 ff
   0.243586     ff 00 00 09 57 b1 02 85 16 09 56 b1 02 c0 05 86 09 2a a1 02
09 1a a1 02 85
   0.243597     18 75 10 95 01 27 ff ff 00 00 09 30 b1 02 85 19 09 32 b1 02
c0 09 1c a1 02
   0.243608     85 1b 75 10 95 01 27 ff ff 00 00 09 30 b1 02 85 1c 09 32 b1
02 85 1e 75 08
   0.243619     95 01 26 ff 00 09 35 b1 02 c0 c0 05 86 09 10 a1 02 05 86 85
20 75 10 95 01
   0.243630     27 ff ff 00 00 09 30 b1 02 85 21 75 08 95 01 26 ff 00 09 39
b1 02 c0 05 86
   0.243641     09 28 a1 02 85 22 75 10 95 01 27 ff ff 00 00 09 21 b1 02 85
23 75 08 95 01
   0.243652     26 ff 00 09 22 b1 02 c0 05 84 09 24 a1 00 85 28 09 fe 75 08
95 01 26 ff 00
   0.243663     b1 02 85 29 09 ff b1 02 05 85 85 2a 09 89 b1 02 85 2b 09 8f
b1 02 85 2c 09
   0.243674     8b b1 02 85 2d 09 44 75 08 95 01 81 82 09 44 b1 82 85 2e 09
45 81 82 09 45
   0.243685     b1 82 05 84 85 30 09 40 75 10 95 01 27 fe ff 00 00 b1 02 85
31 09 30 b1 02
   0.243696     85 32 09 31 75 08 95 01 26 ff 00 b1 02 05 85 85 33 09 2c 75
08 95 01 26 ff
   0.243707     00 b1 02 85 34 09 66 81 82 09 66 b1 82 85 35 09 68 75 10 95
01 27 ff ff 00
   0.243718     00 81 82 09 68 b1 82 85 36 26 ff 00 75 08 95 01 09 83 b1 02
85 37 09 67 b1
   0.243729     02 85 38 09 8c b1 02 85 39 09 8e b1 02 85 3a 09 29 b1 82 85
3b 09 8d b1 02
   0.243740     85 3c 09 d0 b1 82 09 d0 81 82 85 3d 09 42 81 82 09 42 b1 82
85 3e 05 84 09
   0.243748     69 81 82 09 69 b1 82 c0 c0
   0.243825    Using subdriver: Belkin HID 0.12
   0.243836    Entering libusb_get_report
   0.248503    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.248526    Can't retrieve Report 01: Device or resource busy
   0.248546    Path: UPS.BELKINConfig.BELKINConfigVoltage, Type: Feature,
ReportID: 0x01, Offset: 0, Size: 8
   0.248554    Entering libusb_get_report
   0.254471    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.254489    Can't retrieve Report 02: Device or resource busy
   0.254501    Path: UPS.BELKINConfig.BELKINConfigFrequency, Type: Feature,
ReportID: 0x02, Offset: 0, Size: 8
   0.254508    Entering libusb_get_report
   0.259523    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.259542    Can't retrieve Report 03: Device or resource busy
   0.259554    Path: UPS.BELKINConfig.BELKINConfigApparentPower, Type:
Feature, ReportID: 0x03, Offset: 0, Size: 16
   0.259561    Entering libusb_get_report
   0.264524    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.264543    Can't retrieve Report 04: Device or resource busy
   0.264555    Path: UPS.BELKINConfig.BELKINConfigBatteryVoltage, Type:
Feature, ReportID: 0x04, Offset: 0, Size: 16
   0.264562    Entering libusb_get_report
   0.269500    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.269519    Can't retrieve Report 0d: Device or resource busy
   0.269531    Path: UPS.BELKINDevice.BELKINModelString, Type: Feature,
ReportID: 0x0d, Offset: 0, Size: 16
   0.269538    Entering libusb_get_report
   0.274495    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.274514    Can't retrieve Report 0e: Device or resource busy
   0.274526    Path: UPS.BELKINDevice.BELKINModelStringOffset, Type:
Feature, ReportID: 0x0e, Offset: 0, Size: 16
   0.274533    Entering libusb_get_report
   0.279521    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.279541    Can't retrieve Report 0f: Device or resource busy
   0.279616    Path: UPS.BELKINDevice.BELKINUPSType, Type: Feature,
ReportID: 0x0f, Offset: 0, Size: 16
   0.279623    Entering libusb_get_report
   0.284523    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.284541    Can't retrieve Report 10: Device or resource busy
   0.284552    Path: UPS.BELKINControls.BELKINTest, Type: Feature, ReportID:
0x10, Offset: 0, Size: 8
   0.284559    Entering libusb_get_report
   0.289503    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.289522    Can't retrieve Report 11: Device or resource busy
   0.289534    Path: UPS.BELKINControls.BELKINAudibleAlarmControl, Type:
Feature, ReportID: 0x11, Offset: 0, Size: 8
   0.289541    Entering libusb_get_report
   0.294499    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.294517    Can't retrieve Report 15: Device or resource busy
   0.294529    Path: UPS.BELKINControls.BELKINDelayBeforeShutdown, Type:
Feature, ReportID: 0x15, Offset: 0, Size: 16
   0.294536    Entering libusb_get_report
   0.298501    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.298519    Can't retrieve Report 16: Device or resource busy
   0.298531    Path: UPS.BELKINControls.BELKINDelayBeforeStartup, Type:
Feature, ReportID: 0x16, Offset: 0, Size: 16
   0.298538    Entering libusb_get_report
   0.304535    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.304551    Can't retrieve Report 18: Device or resource busy
   0.304561    Path: UPS.BELKINPowerState.BELKINInput.BELKINVoltage, Type:
Feature, ReportID: 0x18, Offset: 0, Size: 16
   0.304567    Entering libusb_get_report
   0.309538    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.309555    Can't retrieve Report 19: Device or resource busy
   0.309565    Path: UPS.BELKINPowerState.BELKINInput.BELKINFrequency, Type:
Feature, ReportID: 0x19, Offset: 0, Size: 16
   0.309571    Entering libusb_get_report
   0.314488    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.314504    Can't retrieve Report 1b: Device or resource busy
   0.314514    Path: UPS.BELKINPowerState.BELKINOutput.BELKINVoltage, Type:
Feature, ReportID: 0x1b, Offset: 0, Size: 16
   0.314521    Entering libusb_get_report
   0.320521    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.320540    Can't retrieve Report 1c: Device or resource busy
   0.320551    Path: UPS.BELKINPowerState.BELKINOutput.BELKINFrequency,
Type: Feature, ReportID: 0x1c, Offset: 0, Size: 16
   0.320559    Entering libusb_get_report
   0.325471    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.325489    Can't retrieve Report 1e: Device or resource busy
   0.325501    Path: UPS.BELKINPowerState.BELKINOutput.BELKINPercentLoad,
Type: Feature, ReportID: 0x1e, Offset: 0, Size: 8
   0.325509    Entering libusb_get_report
   0.330499    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.330518    Can't retrieve Report 20: Device or resource busy
   0.330530    Path: UPS.BELKINBatterySystem.BELKINVoltage, Type: Feature,
ReportID: 0x20, Offset: 0, Size: 16
   0.330537    Entering libusb_get_report
   0.335477    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.335495    Can't retrieve Report 21: Device or resource busy
   0.335506    Path: UPS.BELKINBatterySystem.BELKINCharge, Type: Feature,
ReportID: 0x21, Offset: 0, Size: 8
   0.335514    Entering libusb_get_report
   0.340561    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.340578    Can't retrieve Report 22: Device or resource busy
   0.340589    Path: UPS.BELKINStatus.BELKINPowerStatus, Type: Feature,
ReportID: 0x22, Offset: 0, Size: 16
   0.340596    Entering libusb_get_report
   0.345491    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.345510    Can't retrieve Report 23: Device or resource busy
   0.345521    Path: UPS.BELKINStatus.BELKINBatteryStatus, Type: Feature,
ReportID: 0x23, Offset: 0, Size: 8
   0.345528    Entering libusb_get_report
   0.349524    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.349543    Can't retrieve Report 28: Device or resource busy
   0.349555    Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID:
0x28, Offset: 0, Size: 8
   0.349561    Entering libusb_get_report
   0.355476    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.355494    Can't retrieve Report 29: Device or resource busy
   0.355505    Path: UPS.PowerSummary.iSerialNumber, Type: Feature,
ReportID: 0x29, Offset: 0, Size: 8
   0.355513    Entering libusb_get_report
   0.360501    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.360520    Can't retrieve Report 2a: Device or resource busy
   0.360532    Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature,
ReportID: 0x2a, Offset: 0, Size: 8
   0.360539    Entering libusb_get_report
   0.365473    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.365491    Can't retrieve Report 2b: Device or resource busy
   0.365503    Path: UPS.PowerSummary.iOEMInformation, Type: Feature,
ReportID: 0x2b, Offset: 0, Size: 8
   0.365510    Entering libusb_get_report
   0.371498    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.371580    Can't retrieve Report 2c: Device or resource busy
   0.371591    Path: UPS.PowerSummary.Rechargeable, Type: Feature, ReportID:
0x2c, Offset: 0, Size: 8
   0.371598    Entering libusb_get_report
   0.375489    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.375508    Can't retrieve Report 2d: Device or resource busy
   0.375526    Path: UPS.PowerSummary.Charging, Type: Input, ReportID: 0x2d,
Offset: 0, Size: 8
   0.375534    Entering libusb_get_report
   0.380528    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.380547    Can't retrieve Report 2d: Device or resource busy
   0.380559    Path: UPS.PowerSummary.Charging, Type: Feature, ReportID:
0x2d, Offset: 0, Size: 8
   0.380566    Entering libusb_get_report
   0.385477    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.385495    Can't retrieve Report 2e: Device or resource busy
   0.385507    Path: UPS.PowerSummary.Discharging, Type: Input, ReportID:
0x2e, Offset: 0, Size: 8
   0.385514    Entering libusb_get_report
   0.390501    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.390520    Can't retrieve Report 2e: Device or resource busy
   0.390532    Path: UPS.PowerSummary.Discharging, Type: Feature, ReportID:
0x2e, Offset: 0, Size: 8
   0.390539    Entering libusb_get_report
   0.395471    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.395488    Can't retrieve Report 30: Device or resource busy
   0.395500    Path: UPS.PowerSummary.ConfigVoltage, Type: Feature,
ReportID: 0x30, Offset: 0, Size: 16
   0.395508    Entering libusb_get_report
   0.400499    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.400518    Can't retrieve Report 31: Device or resource busy
   0.400530    Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID:
0x31, Offset: 0, Size: 16
   0.400537    Entering libusb_get_report
   0.405497    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.405516    Can't retrieve Report 32: Device or resource busy
   0.405528    Path: UPS.PowerSummary.Current, Type: Feature, ReportID:
0x32, Offset: 0, Size: 8
   0.405535    Entering libusb_get_report
   0.410523    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.410542    Can't retrieve Report 33: Device or resource busy
   0.410553    Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID:
0x33, Offset: 0, Size: 8
   0.410560    Entering libusb_get_report
   0.415474    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.415492    Can't retrieve Report 34: Device or resource busy
   0.415504    Path: UPS.PowerSummary.RemainingCapacity, Type: Input,
ReportID: 0x34, Offset: 0, Size: 8
   0.415512    Entering libusb_get_report
   0.422500    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.422519    Can't retrieve Report 34: Device or resource busy
   0.422531    Path: UPS.PowerSummary.RemainingCapacity, Type: Feature,
ReportID: 0x34, Offset: 0, Size: 8
   0.422538    Entering libusb_get_report
   0.427474    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.427492    Can't retrieve Report 35: Device or resource busy
   0.427505    Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID:
0x35, Offset: 0, Size: 16
   0.427512    Entering libusb_get_report
   0.432497    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.432515    Can't retrieve Report 35: Device or resource busy
   0.432527    Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature,
ReportID: 0x35, Offset: 0, Size: 16
   0.432534    Entering libusb_get_report
   0.437492    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.437508    Can't retrieve Report 36: Device or resource busy
   0.437520    Path: UPS.PowerSummary.DesignCapacity, Type: Feature,
ReportID: 0x36, Offset: 0, Size: 8
   0.437526    Entering libusb_get_report
   0.442526    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.442544    Can't retrieve Report 37: Device or resource busy
   0.442556    Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature,
ReportID: 0x37, Offset: 0, Size: 8
   0.442563    Entering libusb_get_report
   0.447503    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.447520    Can't retrieve Report 38: Device or resource busy
   0.447530    Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature,
ReportID: 0x38, Offset: 0, Size: 8
   0.447536    Entering libusb_get_report
   0.452499    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.452518    Can't retrieve Report 39: Device or resource busy
   0.452529    Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature,
ReportID: 0x39, Offset: 0, Size: 8
   0.452537    Entering libusb_get_report
   0.457501    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.457520    Can't retrieve Report 3a: Device or resource busy
   0.457532    Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature,
ReportID: 0x3a, Offset: 0, Size: 8
   0.457539    Entering libusb_get_report
   0.462503    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.462521    Can't retrieve Report 3b: Device or resource busy
   0.462533    Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature,
ReportID: 0x3b, Offset: 0, Size: 8
   0.462540    Entering libusb_get_report
   0.467522    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.467541    Can't retrieve Report 3c: Device or resource busy
   0.467553    Path: UPS.PowerSummary.ACPresent, Type: Feature, ReportID:
0x3c, Offset: 0, Size: 8
   0.467560    Entering libusb_get_report
   0.472522    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.472540    Can't retrieve Report 3c: Device or resource busy
   0.472552    Path: UPS.PowerSummary.ACPresent, Type: Input, ReportID:
0x3c, Offset: 0, Size: 8
   0.472559    Entering libusb_get_report
   0.477502    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.477521    Can't retrieve Report 3d: Device or resource busy
   0.477533    Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type:
Input, ReportID: 0x3d, Offset: 0, Size: 8
   0.477540    Entering libusb_get_report
   0.482497    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.482515    Can't retrieve Report 3d: Device or resource busy
   0.482527    Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type:
Feature, ReportID: 0x3d, Offset: 0, Size: 8
   0.482535    Entering libusb_get_report
   0.488500    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.488519    Can't retrieve Report 3e: Device or resource busy
   0.488531    Path: UPS.PowerSummary.ShutdownImminent, Type: Input,
ReportID: 0x3e, Offset: 0, Size: 8
   0.488537    Entering libusb_get_report
   0.493496    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.493514    Can't retrieve Report 3e: Device or resource busy
   0.493526    Path: UPS.PowerSummary.ShutdownImminent, Type: Feature,
ReportID: 0x3e, Offset: 0, Size: 8
   0.493549    string_to_path: depth = 3
   0.493557    Entering libusb_get_report
   0.498492    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.498511    Can't retrieve Report 29: Device or resource busy
   0.498529    Report descriptor retrieved (Reportlen = 498)
   0.498536    Found HID device
   0.498542    Detected a UPS: Belkin /Belkin UPS
   0.498553    string_to_path: depth = 3
   0.498568    Entering libusb_get_report
   0.502533    libusb_get_report: could not claim interface 0: Device or
resource busy
   0.502552    Can't retrieve Report 21: Device or resource busy
   0.502561    Got disconnected by another driver: Device or resource busy
   0.502568    Can't initialize data from HID UPS

On Wed, Jul 13, 2011 at 3:17 AM, Arnaud Quette <aquette.dev@gmail.com>wrote:

> Hi Martin,
>
> 2011/6/27 Martin Ewing <martin.s.ewing@gmail.com>
>
> > I have a very similar situation with my Belkin UPS on Natty (worked on
> > previous release).
> >
> > See
> >
> > $ lsb_release -rd
> > Description:    Ubuntu 11.04
> > Release:        11.04
> >
> > martin@gimli:~$ aptitude show nut
> > Package: nut
> > State: installed
> > Automatically installed: no
> > Version: 2.6.0-1ubuntu3
> > ...
> >
> > sudo /lib/nut/usbhid-ups -DDDD -a mybelkin
> > Network UPS Tools - Generic HID driver 0.35 (2.6.0)
> > USB communication driver 0.31
> >    0.000000     debug level is '4'
> >    0.000583     upsdrv_initups...
> >   0.266176     Checking device (1D6B/0001) (008/001)
> >   0.266219     - VendorID: 1d6b
> >   0.266226     - ProductID: 0001
> >   0.266232     - Manufacturer: unknown
> >   0.266237     - Product: unknown
> >   0.266242     - Serial Number: unknown
> >   0.266247     - Bus: 008
> >   0.266252     Trying to match device
> >   0.266275     Device does not match - skipping
> >   0.266285     Checking device (1D6B/0001) (007/001)
> >   0.266303     - VendorID: 1d6b
> >   0.266309     - ProductID: 0001
> >   0.266315     - Manufacturer: unknown
> >   0.266320     - Product: unknown
> >   0.266325     - Serial Number: unknown
> >   0.266330     - Bus: 007
> >   0.266335     Trying to match device
> >   0.266341     Device does not match - skipping
> >   0.266349     Checking device (050D/1100) (006/002)
> >   0.291945     - VendorID: 050d
> >   0.291959     - ProductID: 1100
> >   0.291966     - Manufacturer: Belkin
> >   0.291972     - Product: Belkin UPS
> >   0.291977     - Serial Number: unknown
> >   0.291982     - Bus: 006
> >   0.291987     Trying to match device
> >   0.291995     Device matches
> > (...)
>
>  0.383981     Entering libusb_get_report
> >   0.388933     libusb_get_report: error sending control message:
> Operation
> > not permitted
> > ...
> >
> > Is this the same bug?
>
>
> I don't think so.
> the issue reported here was related to a code change, that resulted in a
> regression.
>
> yours seem to be with privileges.
> to validate this, try launching the driver with root privs (note the "-u
> root"):
> $ sudo /lib/nut/usbhid-ups -u root -DDDD -a mybelkin
>
>  Is there a fix
>
>
> it's related to udev, and since there seems to be quite some similar
> issues,
> I'm wondering if there is a race condition between udev (started through
> upstart native scripts) and nut (started through upstart sysV compat
> script).
>
> cheers,
> Arnaud
> --
> Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
> Debian Developer - http://www.debian.org
> Free Software Developer - http://arnaud.quette.free.fr/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/779512
>
> Title:
>  nut-2.6.0-1ubuntu3 behavior regression
>
> Status in “nut” package in Ubuntu:
>  Triaged
>
> Bug description:
>  Binary package hint: nut
>
>  Prior to upgrading to Natty, I had the nut-2.4.3-1ubuntu5 package and
>  it was working correctly.
>
>  After upgrading to Natty, I have the nut-2.6.0-1ubuntu3 package and it
>  is not working correctly. Here's my release info:
>
>  •[x4linux:~] mmusgrove $ lsb_release -rd
>  Description:  Ubuntu 11.04
>  Release:      11.04
>
>  The symptom is that it can't initialize data from HID UPS and so the
>  driver fails to start.
>
>  •[x4linux:~] mmusgrove $ sudo upsdrvctl start
>  Network UPS Tools - UPS driver controller 2.6.0
>  Network UPS Tools - Generic HID driver 0.35 (2.6.0)
>  USB communication driver 0.31
>  Using subdriver: CyberPower HID 0.3
>  libusb_get_report: No error
>  Can't initialize data from HID UPS
>  Driver failed to start (exit status=1)
>
>  This appears to be the old behavior from 2.4.x prior to 2.4.3.
>
>  This was reported for Debian months ago:
>
> http://www.google.com/search?source=ig&hl=en&q=nut+2.6.0-1+libusb_get_report%3A+No+error+Can%27t+initialize+data+from+HID+UPS
>
>  Possible related to Bug #701182 (although that is for 2.4.3-2)
>  https://bugs.launchpad.net/ubuntu/+source/nut/+bug/701182
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 11.04
>  Package: nut 2.6.0-1ubuntu3
>  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
>  Uname: Linux 2.6.38-8-generic x86_64
>  NonfreeKernelModules: fglrx
>  Architecture: amd64
>  Date: Sun May  8 09:37:55 2011
>  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
>  KernelVersion: Linux x4linux 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11
> 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
>  ProcEnviron:
>   LANGUAGE=en_US:en
>   PATH=(custom, user)
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: nut
>  UpgradeStatus: Upgraded to natty on 2011-05-06 (2 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions
>

-- 
Martin Ewing
Branford, Connecticut
martin.s.ewing@gmail.com

Revision history for this message

Arnaud Quette (aquette) wrote on 2011-07-13:

#20

2011/7/13 Martin Ewing <email address hidden>

> Arnaud,
>
> Thanks for the reply! I imagine you are correct. I ran the command you
> suggested (below). Apparently nut knows the device it should connect to,
> but that device is "busy". And running as root doesn't overcome the
> problem... (And I don't know why I should have to make /var/run/nut,
> either.)
>

this specific issue with claim is generally bound to another instance of the
driver still running.

> I am not well versed in Ubuntu bug reporting. Do you think I need to
> submit
> this separately? Or should I just wait until the next release? (The lazy
> way out.)
>

for now, we'll focus on hunting your issue here.
if it goes beyond another 2 mails, then we'll check for creating a dedicated
bug report, to be able to close it through 2.6.1 upload, while not forgiving
you ;)

cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

Revision history for this message

Arnaud Quette (aquette) wrote on 2011-12-16:

#21

Note for Ubuntu packagers:
- the original report was an issue with udev, and will be fixed with 2.6.3 upload,
- the 2nd one (Martin Ewing) was probably invalid, due to an already running driver instance.
I've asked the user for some more feedback.

cheers,
Arnaud

Revision history for this message

Martin Ewing (martin-s-ewing) wrote on 2011-12-16:

#22

ups_problem.txt Edit (30.4 KiB, text/plain)

I do still have an issue with NUT on Ubuntu Natty (64 bit).

I attach my latest info. Will appreciate any further suggestions about how to tame this problem - whether my configuration or otherwise.

Thanks!
Martin

Revision history for this message

Martin Ewing (martin-s-ewing) wrote on 2011-12-16:

#23

Perhaps I should have added the following

/dev/usb:

$ ls -l
total 0
crw------- 1 root root 180, 97 2011-12-16 10:15 hiddev1
crw-rw---- 1 root lp 180, 0 2011-12-16 10:15 lp0

-Martin

Revision history for this message

Arnaud Quette (aquette) wrote on 2011-12-16:

#24

Hi Martin,

I'm adding the nut users list, since other may be interested in.

2011/12/16 Martin Ewing <email address hidden>

> I do still have an issue with NUT on Ubuntu Natty (64 bit).
>
> I attach my latest info. Will appreciate any further suggestions about
> how to tame this problem - whether my configuration or otherwise.
>
> Thanks!
> Martin
>
>
> ** Attachment added: "ups_problem.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+attachment/2636234/+files/ups_problem.txt
>

What is strange, as per your next mail, is that "ls /dev/usb" shows
"hiddev1"!
Can you please forward us an excerpt of your system log, using the "usb"
pattern.

cheers,
Arnaud

Revision history for this message

Martin Ewing (martin-s-ewing) wrote on 2011-12-16:

#25

Download full text (7.2 KiB)

On Fri, Dec 16, 2011 at 3:31 PM, Arnaud Quette <email address hidden>wrote:

> Hi Martin,
>
> I'm adding the nut users list, since other may be interested in.
>
> 2011/12/16 Martin Ewing <email address hidden>
>
> > I do still have an issue with NUT on Ubuntu Natty (64 bit).
> >
> > I attach my latest info. Will appreciate any further suggestions about
> > how to tame this problem - whether my configuration or otherwise.
> >
> > Thanks!
> > Martin
> >
> >
> > ** Attachment added: "ups_problem.txt"
> >
> >
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+attachment/2636234/+files/ups_problem.txt
> >
>
> What is strange, as per your next mail, is that "ls /dev/usb" shows
> "hiddev1"!
> Can you please forward us an excerpt of your system log, using the "usb"
> pattern.
>
> cheers,
> Arnaud
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/779512
>
> Title:
> nut-2.6.0-1ubuntu3 behavior regression
>
> Status in “nut” package in Ubuntu:
> Triaged
>
> Bug description:
> Binary package hint: nut
>
> Prior to upgrading to Natty, I had the nut-2.4.3-1ubuntu5 package and
> it was working correctly.
>
> After upgrading to Natty, I have the nut-2.6.0-1ubuntu3 package and it
> is not working correctly. Here's my release info:
>
> •[x4linux:~] mmusgrove $ lsb_release -rd
> Description: Ubuntu 11.04
> Release: 11.04
>
> The symptom is that it can't initialize data from HID UPS and so the
> driver fails to start.
>
> •[x4linux:~] mmusgrove $ sudo upsdrvctl start
> Network UPS Tools - UPS driver controller 2.6.0
> Network UPS Tools - Generic HID driver 0.35 (2.6.0)
> USB communication driver 0.31
> Using subdriver: CyberPower HID 0.3
> libusb_get_report: No error
> Can't initialize data from HID UPS
> Driver failed to start (exit status=1)
>
> This appears to be the old behavior from 2.4.x prior to 2.4.3.
>
> This was reported for Debian months ago:
>
> http://www.google.com/search?source=ig&hl=en&q=nut+2.6.0-1+libusb_get_report%3A+No+error+Can%27t+initialize+data+from+HID+UPS
>
> Possible related to Bug #701182 (although that is for 2.4.3-2)
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/701182
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: nut 2.6.0-1ubuntu3
> ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
> Uname: Linux 2.6.38-8-generic x86_64
> NonfreeKernelModules: fglrx
> Architecture: amd64
> Date: Sun May 8 09:37:55 2011
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> KernelVersion: Linux x4linux 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11
> 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
> ProcEnviron:
> LANGUAGE=en_US:en
> PATH=(custom, user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: nut
> UpgradeStatus: Upgraded to natty on 2011-05-06 (2 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions
>

Arnaud -

I'm not sure how best to reply, so I'll just use this e-mail and put my
syslog inline. This includes the last boot that occurred before the
listi...

On Fri, Dec 16, 2011 at 3:31 PM, Arnaud Quette <aquette.dev@gmail.com>wrote:

> Hi Martin,
>
> I'm adding the nut users list, since other may be interested in.
>
> 2011/12/16 Martin Ewing <martin.s.ewing@gmail.com>
>
> > I do still have an issue with NUT on Ubuntu Natty (64 bit).
> >
> > I attach my latest info.  Will appreciate any further suggestions about
> > how to tame this problem - whether my configuration or otherwise.
> >
> > Thanks!
> > Martin
> >
> >
> > ** Attachment added: "ups_problem.txt"
> >
> >
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+attachment/2636234/+files/ups_problem.txt
> >
>
> What is strange, as per your next mail, is that "ls /dev/usb" shows
> "hiddev1"!
> Can you please forward us an excerpt of your system log, using the "usb"
> pattern.
>
> cheers,
> Arnaud
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/779512
>
> Title:
>  nut-2.6.0-1ubuntu3 behavior regression
>
> Status in “nut” package in Ubuntu:
>  Triaged
>
> Bug description:
>  Binary package hint: nut
>
>  Prior to upgrading to Natty, I had the nut-2.4.3-1ubuntu5 package and
>  it was working correctly.
>
>  After upgrading to Natty, I have the nut-2.6.0-1ubuntu3 package and it
>  is not working correctly. Here's my release info:
>
>  •[x4linux:~] mmusgrove $ lsb_release -rd
>  Description:  Ubuntu 11.04
>  Release:      11.04
>
>  The symptom is that it can't initialize data from HID UPS and so the
>  driver fails to start.
>
>  •[x4linux:~] mmusgrove $ sudo upsdrvctl start
>  Network UPS Tools - UPS driver controller 2.6.0
>  Network UPS Tools - Generic HID driver 0.35 (2.6.0)
>  USB communication driver 0.31
>  Using subdriver: CyberPower HID 0.3
>  libusb_get_report: No error
>  Can't initialize data from HID UPS
>  Driver failed to start (exit status=1)
>
>  This appears to be the old behavior from 2.4.x prior to 2.4.3.
>
>  This was reported for Debian months ago:
>
> http://www.google.com/search?source=ig&hl=en&q=nut+2.6.0-1+libusb_get_report%3A+No+error+Can%27t+initialize+data+from+HID+UPS
>
>  Possible related to Bug #701182 (although that is for 2.4.3-2)
>  https://bugs.launchpad.net/ubuntu/+source/nut/+bug/701182
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 11.04
>  Package: nut 2.6.0-1ubuntu3
>  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
>  Uname: Linux 2.6.38-8-generic x86_64
>  NonfreeKernelModules: fglrx
>  Architecture: amd64
>  Date: Sun May  8 09:37:55 2011
>  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
>  KernelVersion: Linux x4linux 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11
> 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
>  ProcEnviron:
>   LANGUAGE=en_US:en
>   PATH=(custom, user)
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: nut
>  UpgradeStatus: Upgraded to natty on 2011-05-06 (2 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions
>

Arnaud -

I'm not sure how best to reply, so I'll just use this e-mail and put my
syslog inline.  This includes the last boot that occurred before the
listings I gave previously:

Dec 16 10:02:10 gimli kernel: [92892.496522] usb 6-1: new low speed USB
device using uhci_hcd and address 2
Dec 16 10:02:11 gimli kernel: [92892.953384] generic-usb
0003:050D:1100.0004: hiddev0,hidraw2: USB HID v1.11 Device [Belkin  Belkin
UPS] on usb-0000:00:1d.0-1/input0
Dec 16 10:18:19 gimli kernel: [    1.992257] ehci_hcd: USB 2.0 'Enhanced'
Host Controller (EHCI) Driver
Dec 16 10:18:19 gimli kernel: [    1.992321] ehci_hcd 0000:00:1a.7: new USB
bus registered, assigned bus number 1
Dec 16 10:18:19 gimli kernel: [    2.017861] ehci_hcd 0000:00:1a.7: USB 2.0
started, EHCI 1.00
Dec 16 10:18:19 gimli kernel: [    2.017985] hub 1-0:1.0: USB hub found
Dec 16 10:18:19 gimli kernel: [    2.018098] ehci_hcd 0000:00:1d.7: new USB
bus registered, assigned bus number 2
Dec 16 10:18:19 gimli kernel: [    2.037847] ehci_hcd 0000:00:1d.7: USB 2.0
started, EHCI 1.00
Dec 16 10:18:19 gimli kernel: [    2.037971] hub 2-0:1.0: USB hub found
Dec 16 10:18:19 gimli kernel: [    2.038029] ohci_hcd: USB 1.1 'Open' Host
Controller (OHCI) Driver
Dec 16 10:18:19 gimli kernel: [    2.038038] uhci_hcd: USB Universal Host
Controller Interface driver
Dec 16 10:18:19 gimli kernel: [    2.038109] uhci_hcd 0000:00:1a.0: new USB
bus registered, assigned bus number 3
Dec 16 10:18:19 gimli kernel: [    2.038239] hub 3-0:1.0: USB hub found
Dec 16 10:18:19 gimli kernel: [    2.038329] uhci_hcd 0000:00:1a.1: new USB
bus registered, assigned bus number 4
Dec 16 10:18:19 gimli kernel: [    2.038459] hub 4-0:1.0: USB hub found
Dec 16 10:18:19 gimli kernel: [    2.038542] uhci_hcd 0000:00:1a.2: new USB
bus registered, assigned bus number 5
Dec 16 10:18:19 gimli kernel: [    2.047988] hub 5-0:1.0: USB hub found
Dec 16 10:18:19 gimli kernel: [    2.048076] uhci_hcd 0000:00:1d.0: new USB
bus registered, assigned bus number 6
Dec 16 10:18:19 gimli kernel: [    2.048200] hub 6-0:1.0: USB hub found
Dec 16 10:18:19 gimli kernel: [    2.048282] uhci_hcd 0000:00:1d.1: new USB
bus registered, assigned bus number 7
Dec 16 10:18:19 gimli kernel: [    2.048404] hub 7-0:1.0: USB hub found
Dec 16 10:18:19 gimli kernel: [    2.048490] uhci_hcd 0000:00:1d.2: new USB
bus registered, assigned bus number 8
Dec 16 10:18:19 gimli kernel: [    2.048615] hub 8-0:1.0: USB hub found
Dec 16 10:18:19 gimli kernel: [    2.577602] usb 2-3: new high speed USB
device using ehci_hcd and address 3
Dec 16 10:18:19 gimli kernel: [    2.847392] usb 2-5: new high speed USB
device using ehci_hcd and address 4
Dec 16 10:18:19 gimli kernel: [    3.367877] Initializing USB Mass Storage
driver...
Dec 16 10:18:19 gimli kernel: [    3.368086] USB Mass Storage support
registered.
Dec 16 10:18:19 gimli kernel: [    3.373063] usbhid: USB HID core driver
Dec 16 10:18:19 gimli kernel: [    3.426953] usb 3-1: new full speed USB
device using uhci_hcd and address 2
Dec 16 10:18:19 gimli kernel: [    3.896667] usb 3-2: new low speed USB
device using uhci_hcd and address 3
Dec 16 10:18:19 gimli kernel: [    4.356309] usb 6-1: new low speed USB
device using uhci_hcd and address 2
Dec 16 10:18:19 gimli kernel: [    4.802324] generic-usb
0003:050D:1100.0004: hiddev0,hidraw0: USB HID v1.11 Device [Belkin  Belkin
UPS] on usb-0000:00:1d.0-1/input0
Dec 16 10:18:19 gimli kernel: [   22.880415] usblp0: USB Bidirectional
printer dev 2 if 0 alt 1 proto 2 vid 0x03F0 pid 0x0317
Dec 16 10:18:19 gimli kernel: [   23.193489] USB Video Class driver (v1.0.0)
Dec 16 10:18:19 gimli kernel: [   23.223021] input: Logitech USB Receiver
as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2:1.0/input/input3
Dec 16 10:18:19 gimli kernel: [   23.223119] logitech 0003:046D:C517.0002:
input,hidraw1: USB HID v1.10 Keyboard [Logitech USB Receiver] on
usb-0000:00:1a.0-2/input0
Dec 16 10:18:19 gimli kernel: [   23.252510] input: Logitech USB Receiver
as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2:1.1/input/input4
Dec 16 10:18:19 gimli kernel: [   23.252673] logitech 0003:046D:C517.0003:
input,hiddev0,hidraw2: USB HID v1.10 Mouse [Logitech USB Receiver] on
usb-0000:00:1a.0-2/input1
Dec 16 10:18:23 gimli gpsd[2281]: gpsd: GPS device /dev/ttyUSB0 nonexistent
or can't be read

-Martin

-- 
Martin Ewing
Branford, Connecticut
martin.s.ewing@gmail.com

Revision history for this message

Arnaud Quette (aquette) wrote on 2011-12-17:

#26

I don't see any message related to usbhid-ups.
Is it started?
we can see hiddev0 (the device linked to the kernel module hiddev) loaded,
but nothing more.

So, try launching again nut, and check back /var/log/syslog for usb and nut
('ups') messages.

Arno

Revision history for this message

Martin Ewing (martin-s-ewing) wrote on 2011-12-18:

#27

Download full text (9.8 KiB)

On Sat, Dec 17, 2011 at 3:45 AM, Arnaud Quette <email address hidden>wrote:

> I don't see any message related to usbhid-ups.
> Is it started?
> we can see hiddev0 (the device linked to the kernel module hiddev) loaded,
> but nothing more.
>
> So, try launching again nut, and check back /var/log/syslog for usb and nut
> ('ups') messages.
>
> Arno
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/779512
>
> Title:
> nut-2.6.0-1ubuntu3 behavior regression
>
> Status in “nut” package in Ubuntu:
> Triaged
>
> Bug description:
> Binary package hint: nut
>
> Prior to upgrading to Natty, I had the nut-2.4.3-1ubuntu5 package and
> it was working correctly.
>
> After upgrading to Natty, I have the nut-2.6.0-1ubuntu3 package and it
> is not working correctly. Here's my release info:
>
> •[x4linux:~] mmusgrove $ lsb_release -rd
> Description: Ubuntu 11.04
> Release: 11.04
>
> The symptom is that it can't initialize data from HID UPS and so the
> driver fails to start.
>
> •[x4linux:~] mmusgrove $ sudo upsdrvctl start
> Network UPS Tools - UPS driver controller 2.6.0
> Network UPS Tools - Generic HID driver 0.35 (2.6.0)
> USB communication driver 0.31
> Using subdriver: CyberPower HID 0.3
> libusb_get_report: No error
> Can't initialize data from HID UPS
> Driver failed to start (exit status=1)
>
> This appears to be the old behavior from 2.4.x prior to 2.4.3.
>
> This was reported for Debian months ago:
>
> http://www.google.com/search?source=ig&hl=en&q=nut+2.6.0-1+libusb_get_report%3A+No+error+Can%27t+initialize+data+from+HID+UPS
>
> Possible related to Bug #701182 (although that is for 2.4.3-2)
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/701182
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: nut 2.6.0-1ubuntu3
> ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
> Uname: Linux 2.6.38-8-generic x86_64
> NonfreeKernelModules: fglrx
> Architecture: amd64
> Date: Sun May 8 09:37:55 2011
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> KernelVersion: Linux x4linux 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11
> 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
> ProcEnviron:
> LANGUAGE=en_US:en
> PATH=(custom, user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: nut
> UpgradeStatus: Upgraded to natty on 2011-05-06 (2 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions
>

This is what I'm seeing after a recent reboot:

Dec 17 20:54:34 gimli kernel: [ 1.962117] ehci_hcd: USB 2.0 'Enhanced'
Host Controller (EHCI) Driver
Dec 17 20:54:34 gimli kernel: [ 1.962182] ehci_hcd 0000:00:1a.7: new USB
bus registered, assigned bus number 1
Dec 17 20:54:34 gimli kernel: [ 1.987718] ehci_hcd 0000:00:1a.7: USB 2.0
started, EHCI 1.00
Dec 17 20:54:34 gimli kernel: [ 1.987842] hub 1-0:1.0: USB hub found
Dec 17 20:54:34 gimli kernel: [ 1.987956] ehci_hcd 0000:00:1d.7: new USB
bus registered, assigned bus number 2
Dec 17 20:54:34 gimli kernel: [ 2.007705] ehci_hcd 0000:00:1d.7: USB 2....

On Sat, Dec 17, 2011 at 3:45 AM, Arnaud Quette <aquette.dev@gmail.com>wrote:

> I don't see any message related to usbhid-ups.
> Is it started?
> we can see hiddev0 (the device linked to the kernel module hiddev) loaded,
> but nothing more.
>
> So, try launching again nut, and check back /var/log/syslog for usb and nut
> ('ups') messages.
>
> Arno
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/779512
>
> Title:
>  nut-2.6.0-1ubuntu3 behavior regression
>
> Status in “nut” package in Ubuntu:
>  Triaged
>
> Bug description:
>  Binary package hint: nut
>
>  Prior to upgrading to Natty, I had the nut-2.4.3-1ubuntu5 package and
>  it was working correctly.
>
>  After upgrading to Natty, I have the nut-2.6.0-1ubuntu3 package and it
>  is not working correctly. Here's my release info:
>
>  •[x4linux:~] mmusgrove $ lsb_release -rd
>  Description:  Ubuntu 11.04
>  Release:      11.04
>
>  The symptom is that it can't initialize data from HID UPS and so the
>  driver fails to start.
>
>  •[x4linux:~] mmusgrove $ sudo upsdrvctl start
>  Network UPS Tools - UPS driver controller 2.6.0
>  Network UPS Tools - Generic HID driver 0.35 (2.6.0)
>  USB communication driver 0.31
>  Using subdriver: CyberPower HID 0.3
>  libusb_get_report: No error
>  Can't initialize data from HID UPS
>  Driver failed to start (exit status=1)
>
>  This appears to be the old behavior from 2.4.x prior to 2.4.3.
>
>  This was reported for Debian months ago:
>
> http://www.google.com/search?source=ig&hl=en&q=nut+2.6.0-1+libusb_get_report%3A+No+error+Can%27t+initialize+data+from+HID+UPS
>
>  Possible related to Bug #701182 (although that is for 2.4.3-2)
>  https://bugs.launchpad.net/ubuntu/+source/nut/+bug/701182
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 11.04
>  Package: nut 2.6.0-1ubuntu3
>  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
>  Uname: Linux 2.6.38-8-generic x86_64
>  NonfreeKernelModules: fglrx
>  Architecture: amd64
>  Date: Sun May  8 09:37:55 2011
>  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
>  KernelVersion: Linux x4linux 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11
> 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
>  ProcEnviron:
>   LANGUAGE=en_US:en
>   PATH=(custom, user)
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: nut
>  UpgradeStatus: Upgraded to natty on 2011-05-06 (2 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions
>

This is what I'm seeing after a recent reboot:

Dec 17 20:54:34 gimli kernel: [    1.962117] ehci_hcd: USB 2.0 'Enhanced'
Host Controller (EHCI) Driver
Dec 17 20:54:34 gimli kernel: [    1.962182] ehci_hcd 0000:00:1a.7: new USB
bus registered, assigned bus number 1
Dec 17 20:54:34 gimli kernel: [    1.987718] ehci_hcd 0000:00:1a.7: USB 2.0
started, EHCI 1.00
Dec 17 20:54:34 gimli kernel: [    1.987842] hub 1-0:1.0: USB hub found
Dec 17 20:54:34 gimli kernel: [    1.987956] ehci_hcd 0000:00:1d.7: new USB
bus registered, assigned bus number 2
Dec 17 20:54:34 gimli kernel: [    2.007705] ehci_hcd 0000:00:1d.7: USB 2.0
started, EHCI 1.00
Dec 17 20:54:34 gimli kernel: [    2.007830] hub 2-0:1.0: USB hub found
Dec 17 20:54:34 gimli kernel: [    2.007888] ohci_hcd: USB 1.1 'Open' Host
Controller (OHCI) Driver
Dec 17 20:54:34 gimli kernel: [    2.007897] uhci_hcd: USB Universal Host
Controller Interface driver
Dec 17 20:54:34 gimli kernel: [    2.007968] uhci_hcd 0000:00:1a.0: new USB
bus registered, assigned bus number 3
Dec 17 20:54:34 gimli kernel: [    2.008097] hub 3-0:1.0: USB hub found
Dec 17 20:54:34 gimli kernel: [    2.008187] uhci_hcd 0000:00:1a.1: new USB
bus registered, assigned bus number 4
Dec 17 20:54:34 gimli kernel: [    2.008318] hub 4-0:1.0: USB hub found
Dec 17 20:54:34 gimli kernel: [    2.008400] uhci_hcd 0000:00:1a.2: new USB
bus registered, assigned bus number 5
Dec 17 20:54:34 gimli kernel: [    2.008523] hub 5-0:1.0: USB hub found
Dec 17 20:54:34 gimli kernel: [    2.008610] uhci_hcd 0000:00:1d.0: new USB
bus registered, assigned bus number 6
Dec 17 20:54:34 gimli kernel: [    2.008734] hub 6-0:1.0: USB hub found
Dec 17 20:54:34 gimli kernel: [    2.008816] uhci_hcd 0000:00:1d.1: new USB
bus registered, assigned bus number 7
Dec 17 20:54:34 gimli kernel: [    2.008938] hub 7-0:1.0: USB hub found
Dec 17 20:54:34 gimli kernel: [    2.009024] uhci_hcd 0000:00:1d.2: new USB
bus registered, assigned bus number 8
Dec 17 20:54:34 gimli kernel: [    2.009150] hub 8-0:1.0: USB hub found
Dec 17 20:54:34 gimli kernel: [    2.647392] usb 3-1: new full speed USB
device using uhci_hcd and address 2
Dec 17 20:54:34 gimli kernel: [    3.126994] usb 3-2: new low speed USB
device using uhci_hcd and address 3
Dec 17 20:54:34 gimli kernel: [    3.326265] usbhid: USB HID core driver
Dec 17 20:54:34 gimli kernel: [    3.456857] input: Logitech USB Receiver
as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2:1.0/input/input2
Dec 17 20:54:34 gimli kernel: [    3.456917] logitech 0003:046D:C517.0001:
input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Receiver] on
usb-0000:00:1a.0-2/input0
Dec 17 20:54:34 gimli kernel: [    3.485432] input: Logitech USB Receiver
as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2:1.1/input/input3
Dec 17 20:54:34 gimli kernel: [    3.485537] logitech 0003:046D:C517.0002:
input,hiddev0,hidraw1: USB HID v1.10 Mouse [Logitech USB Receiver] on
usb-0000:00:1a.0-2/input1
Dec 17 20:54:34 gimli kernel: [    3.486732] usb 2-3: new high speed USB
device using ehci_hcd and address 3
Dec 17 20:54:34 gimli kernel: [    3.680792] Initializing USB Mass Storage
driver...
Dec 17 20:54:34 gimli kernel: [    3.681205] USB Mass Storage support
registered.
Dec 17 20:54:34 gimli kernel: [    3.796506] usb 2-5: new high speed USB
device using ehci_hcd and address 4
Dec 17 20:54:34 gimli kernel: [    4.386049] usb 6-1: new low speed USB
device using uhci_hcd and address 2
Dec 17 20:54:34 gimli kernel: [    4.839276] generic-usb
0003:050D:1100.0004: hiddev0,hidraw2: USB HID v1.11 Device [Belkin  Belkin
UPS] on usb-0000:00:1d.0-1/input0
Dec 17 20:54:34 gimli kernel: [   23.077150] usblp0: USB Bidirectional
printer dev 2 if 0 alt 1 proto 2 vid 0x03F0 pid 0x0317
Dec 17 20:54:34 gimli kernel: [   23.356500] USB Video Class driver (v1.0.0)
Dec 17 20:54:34 gimli kernel: [   25.350999] type=1400
audit(1324173273.830:10): apparmor="STATUS" operation="profile_load"
name="/usr/lib/cups/backend/cups-pdf" pid=1125 comm="apparmor_parser"
Dec 17 20:54:34 gimli kernel: [   25.351610] type=1400
audit(1324173273.840:11): apparmor="STATUS" operation="profile_load"
name="/usr/sbin/cupsd" pid=1125 comm="apparmor_parser"
Dec 17 20:54:38 gimli upsd[2468]: listening on 127.0.0.1 port 3493
Dec 17 20:54:38 gimli upsd[2468]: listening on ::1 port 3493
Dec 17 20:54:38 gimli upsd[2468]: Can't connect to UPS [mybelkin]
(usbhid-ups-mybelkin): No such file or directory
Dec 17 20:54:38 gimli upsd[2494]: Startup successful
Dec 17 20:54:38 gimli upsmon[2497]: Startup successful
Dec 17 20:54:38 gimli upsd[2494]: User upsmon@::1 logged into UPS [mybelkin]
Dec 17 20:54:38 gimli upsmon[2500]: Poll UPS [mybelkin@localhost] failed -
Driver not connected
Dec 17 20:54:38 gimli upsmon[2500]: Communications with UPS
mybelkin@localhost lost
Dec 17 20:54:43 gimli upsmon[2500]: Poll UPS [mybelkin@localhost] failed -
Driver not connected
Dec 17 20:54:43 gimli upsmon[2500]: UPS mybelkin@localhost is unavailable
Dec 17 20:54:48 gimli upsmon[2500]: Poll UPS [mybelkin@localhost] failed -
Driver not connected
Dec 17 20:55:23 gimli upsmon[2500]: last message repeated 7 times
Dec 17 20:55:28 gimli upsmon[2500]: Poll UPS [mybelkin@localhost] failed -
Driver not connected
Dec 17 20:55:33 gimli upsmon[2500]: Poll UPS [mybelkin@localhost] failed -
Driver not connected
Dec 17 20:56:34 gimli upsmon[2500]: last message repeated 12 times
Dec 17 20:57:34 gimli upsmon[2500]: last message repeated 12 times
Dec 17 20:58:34 gimli upsmon[2500]: last message repeated 12 times
Dec 17 20:59:34 gimli upsmon[2500]: last message repeated 12 times
Dec 17 20:59:38 gimli upsmon[2500]: Poll UPS [mybelkin@localhost] failed -
Driver not connected
Dec 17 20:59:38 gimli upsd[2494]: Can't connect to UPS [mybelkin]
(usbhid-ups-mybelkin): No such file or directory
Dec 17 20:59:43 gimli upsmon[2500]: Poll UPS [mybelkin@localhost] failed -
Driver not connected
Dec 17 20:59:48 gimli upsmon[2500]: Poll UPS [mybelkin@localhost] failed -
Driver not connected
Dec 17 20:59:48 gimli upsmon[2500]: UPS mybelkin@localhost is unavailable
Dec 17 20:59:53 gimli upsmon[2500]: Poll UPS [mybelkin@localhost] failed -
Driver not connected
Dec 17 21:00:58 gimli upsmon[2500]: last message repeated 13 times
Dec 17 21:02:03 gimli upsmon[2500]: last message repeated 13 times
Dec 17 21:03:04 gimli upsmon[2500]: last message repeated 12 times
Dec 17 21:04:04 gimli upsmon[2500]: last message repeated 12 times
Dec 17 21:04:38 gimli upsmon[2500]: last message repeated 7 times
Dec 17 21:04:38 gimli upsd[2494]: Can't connect to UPS [mybelkin]
(usbhid-ups-mybelkin): No such file or directory
Dec 17 21:04:43 gimli upsmon[2500]: Poll UPS [mybelkin@localhost] failed -
Driver not connected
Dec 17 21:04:53 gimli upsmon[2500]: last message repeated 2 times
Dec 17 21:04:53 gimli upsmon[2500]: UPS mybelkin@localhost is unavailable
Dec 17 21:04:58 gimli upsmon[2500]: Poll UPS [mybelkin@localhost] failed -
Driver not connected
Dec 17 21:06:04 gimli upsmon[2500]: last message repeated 13 times
Dec 17 21:07:04 gimli upsmon[2500]: last message repeated 12 times
Dec 17 21:08:05 gimli upsmon[2500]: last message repeated 12 times
Dec 17 21:09:02 gimli upsmon[2500]: last message repeated 11 times
Dec 17 21:09:04 gimli upsmon[2500]: Poll UPS [mybelkin@localhost] failed -
Driver not connected
Dec 17 21:09:38 gimli upsmon[2500]: last message repeated 6 times

-- 
Martin Ewing
Branford, Connecticut
martin.s.ewing@gmail.com

Revision history for this message

Arnaud Quette (aquette) wrote on 2012-01-24:

#28

Martin,

could you please check this bug report, and apply the udev related procedure I've documented at the end of the thread:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200

Once applied, stop nut, unplug/replug your UPS USB cord, and restart nut (at least the driver), and report back the status.

Arnaud

Changed in nut (Ubuntu):
status:	Triaged → Fix Committed

Revision history for this message

Martin Ewing (martin-s-ewing) wrote on 2012-01-27:

#29

Hi Arnaud,

I seem to have fixed my NUT problem by upgrading my system to Ubuntu
11.10. (upsd 2.6.1)

I never resolved the issue on 11.04, but your udev rules file probably
would have done it, I would guess!

Thanks for all your help!

Martin

On Tue, Jan 24, 2012 at 10:09 AM, Arnaud Quette <email address hidden>wrote:

> Martin,
>
> could you please check this bug report, and apply the udev related
> procedure I've documented at the end of the thread:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200
>
> Once applied, stop nut, unplug/replug your UPS USB cord, and restart nut
> (at least the driver), and report back the status.
>
> Arnaud
>
> ** Changed in: nut (Ubuntu)
> Status: Triaged => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/779512
>
> Title:
> nut-2.6.0-1ubuntu3 behavior regression
>
> Status in “nut” package in Ubuntu:
> Fix Committed
>
> Bug description:
> Binary package hint: nut
>
> Prior to upgrading to Natty, I had the nut-2.4.3-1ubuntu5 package and
> it was working correctly.
>
> After upgrading to Natty, I have the nut-2.6.0-1ubuntu3 package and it
> is not working correctly. Here's my release info:
>
> •[x4linux:~] mmusgrove $ lsb_release -rd
> Description: Ubuntu 11.04
> Release: 11.04
>
> The symptom is that it can't initialize data from HID UPS and so the
> driver fails to start.
>
> •[x4linux:~] mmusgrove $ sudo upsdrvctl start
> Network UPS Tools - UPS driver controller 2.6.0
> Network UPS Tools - Generic HID driver 0.35 (2.6.0)
> USB communication driver 0.31
> Using subdriver: CyberPower HID 0.3
> libusb_get_report: No error
> Can't initialize data from HID UPS
> Driver failed to start (exit status=1)
>
> This appears to be the old behavior from 2.4.x prior to 2.4.3.
>
> This was reported for Debian months ago:
>
> http://www.google.com/search?source=ig&hl=en&q=nut+2.6.0-1+libusb_get_report%3A+No+error+Can%27t+initialize+data+from+HID+UPS
>
> Possible related to Bug #701182 (although that is for 2.4.3-2)
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/701182
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: nut 2.6.0-1ubuntu3
> ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
> Uname: Linux 2.6.38-8-generic x86_64
> NonfreeKernelModules: fglrx
> Architecture: amd64
> Date: Sun May 8 09:37:55 2011
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> KernelVersion: Linux x4linux 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11
> 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
> ProcEnviron:
> LANGUAGE=en_US:en
> PATH=(custom, user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: nut
> UpgradeStatus: Upgraded to natty on 2011-05-06 (2 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions
>

--
Martin Ewing
Branford, Connecticut
<email address hidden>

Hi Arnaud,

I seem to have fixed my NUT problem by upgrading my system to Ubuntu
11.10.  (upsd 2.6.1)

I never resolved the issue on 11.04, but your udev rules file probably
would have done it, I would guess!

Thanks for all your help!

Martin

On Tue, Jan 24, 2012 at 10:09 AM, Arnaud Quette <aquette.dev@gmail.com>wrote:

> Martin,
>
> could you please check this bug report, and apply the udev related
> procedure I've documented at the end of the thread:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200
>
> Once applied, stop nut, unplug/replug your UPS USB cord, and restart nut
> (at least the driver), and report back the status.
>
> Arnaud
>
> ** Changed in: nut (Ubuntu)
>       Status: Triaged => Fix Committed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/779512
>
> Title:
>  nut-2.6.0-1ubuntu3 behavior regression
>
> Status in “nut” package in Ubuntu:
>   Fix Committed
>
> Bug description:
>  Binary package hint: nut
>
>  Prior to upgrading to Natty, I had the nut-2.4.3-1ubuntu5 package and
>  it was working correctly.
>
>  After upgrading to Natty, I have the nut-2.6.0-1ubuntu3 package and it
>  is not working correctly. Here's my release info:
>
>  •[x4linux:~] mmusgrove $ lsb_release -rd
>  Description:  Ubuntu 11.04
>  Release:      11.04
>
>  The symptom is that it can't initialize data from HID UPS and so the
>  driver fails to start.
>
>  •[x4linux:~] mmusgrove $ sudo upsdrvctl start
>  Network UPS Tools - UPS driver controller 2.6.0
>  Network UPS Tools - Generic HID driver 0.35 (2.6.0)
>  USB communication driver 0.31
>  Using subdriver: CyberPower HID 0.3
>  libusb_get_report: No error
>  Can't initialize data from HID UPS
>  Driver failed to start (exit status=1)
>
>  This appears to be the old behavior from 2.4.x prior to 2.4.3.
>
>  This was reported for Debian months ago:
>
> http://www.google.com/search?source=ig&hl=en&q=nut+2.6.0-1+libusb_get_report%3A+No+error+Can%27t+initialize+data+from+HID+UPS
>
>  Possible related to Bug #701182 (although that is for 2.4.3-2)
>  https://bugs.launchpad.net/ubuntu/+source/nut/+bug/701182
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 11.04
>  Package: nut 2.6.0-1ubuntu3
>  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
>  Uname: Linux 2.6.38-8-generic x86_64
>  NonfreeKernelModules: fglrx
>  Architecture: amd64
>  Date: Sun May  8 09:37:55 2011
>  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
>  KernelVersion: Linux x4linux 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11
> 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
>  ProcEnviron:
>   LANGUAGE=en_US:en
>   PATH=(custom, user)
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: nut
>  UpgradeStatus: Upgraded to natty on 2011-05-06 (2 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+subscriptions
>

-- 
Martin Ewing
Branford, Connecticut
martin.s.ewing@gmail.com

Revision history for this message

Arnaud Quette (aquette) wrote on 2012-01-27:

#30

Hi Martin,

thanks for your confirmation.
I'm now closing this bug.

Arnaud

Changed in nut (Ubuntu):
assignee:	nobody → Arnaud Quette (aquette)
status:	Fix Committed → Fix Released

Ubuntu
nut package

nut-2.6.0-1ubuntu3 behavior regression

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntunut package

nut-2.6.0-1ubuntu3 behavior regression

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
nut package