[SRU] libusb_get_report: error sending control message: Operation not permitted

please try to unplug and plug back your UPS's USB cord, and then relaunch
nut.

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

Arnaud,

Have tried already with the same result (system log fragment is below). Also, if I understand well, upsdrvctl call doesn't need nut service be started at all.

Apr 30 17:03:53 localhost kernel: [ 6278.291294] usb 4-2: USB disconnect, address 3
Apr 30 17:03:57 localhost kernel: [ 6282.780029] usb 4-2: new low speed USB device using uhci_hcd and address 4
Apr 30 17:03:58 localhost kernel: [ 6282.956175] usb 4-2: configuration #1 chosen from 1 choice
Apr 30 17:03:58 localhost kernel: [ 6283.115231] generic-usb 0003:0764:0501.0004: hiddev96,hidraw1: USB HID v1.10 Device [CPS UPS VALUE] on usb-0000:00:1d.2-2/input0

Can you try the version in my ppa (https://launchpad.net/~zulcss/+archive/server-lucid-bug-fixes)

chuck

Chuck, I will. Now I see:

nut 11 hours ago
Waiting to build

What is expected time lag before the package be built?

I'm having this same problem since upgrading to Lucid this afternoon and would like to try out this fix.

Whith these updates from zulcss ppa

libupsclient1 [2.4.3-1ubuntu3 -> 2.4.3-1ubuntu4]
nut [2.4.3-1ubuntu3 -> 2.4.3-1ubuntu4]

the problem has gone, thanks!

Both patches worked for me as well, great!

Statement of Impact:

nut in lucid was shipped with a bug that prevented some UPSes from connecting to the nut daemon. Checking google fedora was also affected by the same problem and has the same patch that we used.

Explanation:

This bug has been fixed by the attached debdiff that fixes this issue. This patch needs to be sent upstream if its not already fixed.

How to reproduce:

1. Have a UPS that is affected by this problem.
2. Try to connect to NUT
3. You should get the error message.

There should not be any regressions with this patch.

chuck

Accepted nut into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Verified: have downgraded from 2.4.3-1ubuntu4 (from zulcss ppa) to 2.4.3-1ubuntu3.1 (from proposed) - at my case all does work as expected. Thanks!

2010/5/3 Chuck Short <email address hidden>

> Statement of Impact:
>
> nut in lucid was shipped with a bug that prevented some UPSes from
> connecting to the nut daemon. Checking google fedora was also affected
> by the same problem and has the same patch that we used.
>
> Explanation:
>
> This bug has been fixed by the attached debdiff that fixes this issue.
> This patch needs to be sent upstream if its not already fixed.
>

FYI, this has already reached upstream (through RH/Fedora maintainer who is
part of the team) and was applied in NUT trunk r2407 (
http://boxster.ghz.cc/projects/nut/changeset/2407)

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

This bug was fixed in the package nut - 2.4.3-1ubuntu3.1

---------------
nut (2.4.3-1ubuntu3.1) lucid-proposed; urgency=low

  * debian/patches/04_nut-small-buffers.dpatch: Fix "libusb_get_report: error sending control message:
    Operation not permitted" error on some UPS devices. (LP: #572262)
 -- Chuck Short <email address hidden> Mon, 03 May 2010 13:38:37 -0400

Copied to maverick.

Yes, bug fixed.

My UPS:

Bus 006 Device 124: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS

Systems: Ubuntu, debian testing/unstable.
nut: 2.4.3-1