[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Launchpad has imported 20 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=488368. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-03-03T22:14:16+00:00 Russell wrote: Description of problem: I have an MGE Ellipse Pulsar 500 UPS (USB ID 0463:), connected via USB, and since upgrading to F10 from F8, usbhid-ups will not start. Version-Release number of selected component (if applicable): [root@detritus ~]# rpm -qa | grep ^nut nut-client-2.2.2-4.fc10.x86_64 nut-2.2.2-4.fc10.x86_64 [root@detritus ~]# uname -r 2.6.27.15-170.2.24.fc10.x86_64 How reproducible: Every time Steps to Reproduce: 1. Configure a UPS with driver = usbhid-ups 2. Attempt to start ups service Actual results: [root@detritus ~]# service ups start Starting UPS driver controller:[FAILED] Starting upsd: [ OK ] Starting UPS monitor (master): [ OK ] Expected results: Service should start successfully Additional info: [root@detritus ~]# lsusb -d 0463: Bus 003 Device 002: ID 0463: MGE UPS Systems UPS [root@detritus ~]# usbhid-ups -D -a mge -x vendorid=0463 -x productid= Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) debug level is '5' upsdrv_initups... [snipped checking other USB devices here] Checking device (0463/) (003/002) - VendorID: 0463 - ProductID: - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 003 Trying to match device Device matches failed to claim USB device, trying 2 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... failed to claim USB device, trying 1 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... failed to claim USB device, trying 0 more time(s)... detaching kernel driver from USB device... failed to detach kernel driver from USB device... trying again to claim USB device... Unable to get HID descriptor (error sending control message: Operation not permitted) i=0, extra[i]=09, extra[i+1]=21 HID descriptor, method 2: (9 bytes) => 09 21 00 01 21 01 22 14 02 HID descriptor length 532 Unable to get Report descriptor: Operation not permitted [snipped checking other USB devices here] No appropriate HID device found No matching HID UPS found This looks very similar to bug 461374, but that was apparently fixed. The documentation tells me that this is definitely the correct driver to use (I think I could use mge-shut if I used a serial cable instead, but my serial port is in use for something else). Reply at: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/comments/0 On 2009-03-10T16:09:33+00:00 Michal wrote: could you try check if usbhid-ups -u root -DD -a works? is name of your ups in ups.conf - in square brackets also, do you have any selinux denial messages? do you see any messages in /var/log/messages related to this? Reply at: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/comments/1 On 2009-03-14T19:01:17+00:00 Russell wrote: "usbhid-ups -u root -DD -a mge" is successful. When I start usbhid-ups on its own, without "-u root", /var/log/messages doesn't contain anything (and just a "Connection refused" message when I try to start NUT via the initscript), and I don't see any selinux messages. Adding "user = root" to ups.conf seems to allow it to start OK but (having amended my config to use IPv4, as upsd doesn't seem to want to listen on IPv6) upsd still can't connect until I fix a socket permission problem: [root@detritus ~]# ls -l /var/run/nut/usbhid-ups-mge srw-rw 1 root root 0 2009-03-14 18:44 /var/run/nut/usbhid-ups-mge [root@detritus ~]# chmod o+rw /var/run/nut/usbhid-ups-mge After doing this (after NUT startup) everything works, but obviously this is a dirty hack - but I imagine the problem will go away once we get to the bottom of why usbhid-ups needs to run as root in order to work. Reply at: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/comments/2 On 2009-03-17T12:49:59+00:00 Michal wrote: First, I've got the same errors when starting ups service. Then I've fully configured it and it works for me now without any errors. could you upload all your nut config files in this bz? /etc/sysconfig/ups /etc/ups/ups.conf /etc/ups/upsd.conf /etc/ups/upsd.users /etc/ups/upsmon.conf /etc/ups/upssched.conf
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Since this was to get around the entangled SRUs I correct the state back to invalid. See comment #29. ** Changed in: nut (Ubuntu Trusty) Status: Fix Released => Invalid ** Changed in: nut (Ubuntu Xenial) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
This bug was fixed in the package nut - 2.7.1-1ubuntu1.2 --- nut (2.7.1-1ubuntu1.2) trusty; urgency=medium * Drop d/p/Fix-USB-permission-issues-related-to-Linux-udev.patch: this issue seems fixed via other updates and is no more reproducible (LP 1099947). nut (2.7.1-1ubuntu1.1) trusty; urgency=medium * debian/nut-server.postinst: The udevd process is called systemd-udevd for quite sometimes already, properly detect whether it's running or not, this should fix the devices permissions for USB UPS's (LP: #1540008) * d/p/Fix-USB-permission-issues-related-to-Linux-udev.patch: make udev rule apply correctly (LP 1099947). -- Christian Ehrhardt Mon, 28 Aug 2017 08:48:47 +0200 ** Changed in: nut (Ubuntu Trusty) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
This bug was fixed in the package nut - 2.7.2-4ubuntu1.2 --- nut (2.7.2-4ubuntu1.2) xenial; urgency=medium * Drop d/p/Fix-USB-permission-issues-related-to-Linux-udev.patch: this issue seems fixed via other updates and is no more reproducible (LP 1099947). Also fixes a FTBFS on the ongoing SRU of 2.7.2-4ubuntu1.1. nut (2.7.2-4ubuntu1.1) xenial; urgency=medium * debian/nut-server.postinst: The udevd process is called systemd-udevd for quite sometimes already, properly detect whether it's running or not, this should fix the devices permissions for USB UPS's (LP: #1540008) * d/p/Fix-USB-permission-issues-related-to-Linux-udev.patch: make udev rule apply correctly (LP 1099947). -- Christian Ehrhardt Thu, 24 Aug 2017 09:47:35 +0200 ** Changed in: nut (Ubuntu Xenial) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
For the sake of passing the SRU process - setting this verification- done. It really is no more part of the (refreshed) update anymore, but still listed so SRU members might wait for a verification to happen. Well in some sense the verification was "done", led to new insights and the change was removed from the SRU - so we are not faking the "done" too much :-) ** Tags removed: verification-needed verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Thanks for the extra checks Simon! We can say - until we have a reproducer/verification-chance this stays as is. The SRU will only cover the other issue that the install does not retrigger the events to work right away (without e.g. replug) but not this issue here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Fresh install of Trusty 14.04.0 with *old* udev: # apt-cache policy udev udev: Installed: 204-5ubuntu20 Candidate: 204-5ubuntu20.24 Version table: 204-5ubuntu20.24 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages *** 204-5ubuntu20 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Plugging CyberPower USB cable: # udevadm monitor --subsystem-match=usb monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[212.661306] add /devices/pci:00/:00:1a.1/usb4/4-2 (usb) KERNEL[212.663416] add /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0 (usb) UDEV [212.861460] add /devices/pci:00/:00:1a.1/usb4/4-2 (usb) UDEV [212.863063] add /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0 (usb) Wrong perms: # find /dev/bus/usb/ -ls 73290 drwxr-xr-x 10 root root 200 Aug 29 16:14 /dev/bus/usb/ ... 73360 drwxr-xr-x 2 root root 80 Aug 29 16:17 /dev/bus/usb/004 114060 crw-rw-r-- 1 root root Aug 29 16:17 /dev/bus/usb/004/002 73370 crw-rw-r-- 1 root root Aug 29 16:14 /dev/bus/usb/004/001 ... Install nut-server # apt-get install -y nut-server # pulling 2.7.1-1ubuntu1 # lsusb | grep Cyber Bus 004 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Unplugging/re-plugging the CyberPower: # udevadm monitor --subsystem-match=usb monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[544.264436] remove /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0 (usb) KERNEL[544.264626] remove /devices/pci:00/:00:1a.1/usb4/4-2 (usb) UDEV [544.271603] remove /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0 (usb) UDEV [544.271648] remove /devices/pci:00/:00:1a.1/usb4/4-2 (usb) KERNEL[548.024486] add /devices/pci:00/:00:1a.1/usb4/4-2 (usb) KERNEL[548.027386] add /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0 (usb) UDEV [548.186083] add /devices/pci:00/:00:1a.1/usb4/4-2 (usb) UDEV [548.187851] add /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0 (usb) Notice that nut-server's 52-nut-usbups.rules worked: # find /dev/bus/usb/ -ls 73290 drwxr-xr-x 10 root root 200 Aug 29 16:14 /dev/bus/usb/ ... 73360 drwxr-xr-x 2 root root 80 Aug 29 16:23 /dev/bus/usb/004 123290 crw-rw-r-- 1 root nut Aug 29 16:23 /dev/bus/usb/004/003 73370 crw-rw-r-- 1 root root Aug 29 16:14 /dev/bus/usb/004/001 ... What's weird in the above is that udev reports it's adding 4-2 but the device is apparently at 4-3: # lsusb | grep Cyber Bus 004 Device 003: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS I did unplug/plug back in the exact same physical slot. Here's dmesg just in case: # dmesg -T | grep 0501 [Tue Aug 29 16:17:32 2017] usb 4-2: New USB device found, idVendor=0764, idProduct=0501 [Tue Aug 29 16:17:32 2017] hid-generic 0003:0764:0501.0002: hiddev0,hidraw1: USB HID v1.10 Device [CPS CP685AVR-G] on usb-:00:1a.1-2/input0 [Tue Aug 29 16:23:08 2017] usb 4-2: New USB device found, idVendor=0764, idProduct=0501 [Tue Aug 29 16:23:08 2017] hid-generic 0003:0764:0501.0003: hiddev0,hidraw1: USB HID v1.10 Device [CPS CP685AVR-G] on usb-:00:1a.1-2/input0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
On 2017-08-28 09:01 AM, ChristianEhrhardt wrote: > Hi Simon, > while we might pursue the reddest herring ever since you have the testbed > around you might run in one console. So lets help each other to not > over-engineer this, but OTOH it might be interesting to see why it is fixed. > > # unplug the device > $ udevadm monitor --subsystem-match=usb > # plug the device $ udevadm monitor --subsystem-match=usb monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[72.829167] add /devices/pci:00/:00:1a.1/usb4/4-2 (usb) KERNEL[72.831253] add /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0 (usb) UDEV [73.022997] add /devices/pci:00/:00:1a.1/usb4/4-2 (usb) UDEV [73.031355] add /devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.0 (usb) > and install from the trusty > release ISO (no updates) including nut-server. Then pass through the usb > device and see if it is working there as well. I'm downloading 14.04.0 [1] to install it on my physical test box and will report how it goes without updates. [1] http://old-releases.ubuntu.com/releases/trusty/ubuntu-14.04-server-amd64+mac.iso -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Hi Simon, while we might pursue the reddest herring ever since you have the testbed around you might run in one console. So lets help each other to not over-engineer this, but OTOH it might be interesting to see why it is fixed. # unplug the device $ udevadm monitor --subsystem-match=usb # plug the device Interested to see if the rules in 52-... (or whatever else) is processed then. If you want to go "hardcore" (reading as "please don't if you not really want to") you could set up a KVM guest and install from the trusty release ISO (no updates) including nut-server. Then pass through the usb device and see if it is working there as well. P.S. making +1 on my "spend a beer if I ever see ..." note -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Thanks Charles and Christian. I'll keep the Trusty machine around for a while so let me know if any more tests would be useful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Hi Charles, thank you to chime in! The current "issue" is that there is no issue left anymore as it seems. Which is why I have removed that change from the current SRU activity and Simon set invalid on the bug tasks until we know otherwise. But every check is a good one - so in this case I checked the oldest possible version which is trusty. But even there is no trace of the old SYSFS left. root@trusty-test:~# grep ATTR /lib/udev/rules.d/52-nut-usbups.rules | wc -l 90 root@trusty-test:~# grep SYSFS /lib/udev/rules.d/52-nut-usbups.rules | wc -l 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Simon, can you check whether the SYSFS/ATTR comment from the Debian bug applies? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721600#10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/nut/+git/nut/+merge/329714 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
So whatever overwrote the privs in the past due to having a too low rules number no more does so. Thanks for verifying Trusty as well Simon! Hmm, that SRU was supposed to be so trivial as all was clear yet the lack of the special HW caused me to miss this "already fixed" by whatever third source. I already feel this comes back one day, but for now keep it invalid and I'll upload an updated SRU that only tackles the remaining issue (which I can test as I don't need the special HW to ensure btw). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Hi Christian, Even on Trusty (*without* the -proposed package) I'm unable to repro the original issue: # tail -n 5 /etc/nut/ups.conf [cyberpower] driver = usbhid-ups port = auto desc = "CyberPower CP685AVR-G" vendorid = 0764 # lsusb | grep Cyber Bus 004 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS # ll /dev/bus/usb/004/002 crw-rw-r-- 1 root nut 189, 385 Aug 25 18:01 /dev/bus/usb/004/002 # find /lib/udev/rules.d/ -name '*nut*' /lib/udev/rules.d/52-nut-usbups.rules I will thus mark the Trusty task as invalid as well. ** Changed in: nut (Ubuntu Trusty) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
On 2017-08-24 09:44 AM, ChristianEhrhardt wrote: > I'd like to ensure to know on the state of this for Trusty. > But my last UPS device was still serial and died a decade ago. > So if you can spend the HW and time to test there please go for it as you can > afford. I already have the UPS so it's just a matter of setting up a Trusty host. I'll get to that next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Hi Simon, I'd like to ensure to know on the state of this for Trusty. But my last UPS device was still serial and died a decade ago. So if you can spend the HW and time to test there please go for it as you can afford. P.S. I see a "I need that for work" discussion at home :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
On 2017-08-24 03:45 AM, ChristianEhrhardt wrote: > Do you have a setup to verify the change on Trusty? Unfortunately no because I would have verified if the SRU was still needed there or not :( If you want to pursue the Trusty SRU for other users, I'll arrange a setup for the validation (if nobody beats me to it). Thanks Christian! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/nut/+git/nut/+merge/329502 ** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/nut/+git/nut/+merge/329504 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
That is what happens when bugs are dormant for too long :-/. It still seems to be an issue for Trusty, but you are right without the ability to reproduce we should cancel that bug here from the Xenial SRU. I have to redo it anyway for Xenial as there is an FTBFS in the fix (that is the reason you don't see it), and on that I'll reduce it to the other bug that was part of the planned SRU. Thanks for your quick response! I'm marking Xenial as invalid now - and the follow on upload will revert the change for this bug here. Do you have a setup to verify the change on Trusty? Not that this was fixed by e.g. udev changes unknown to us as well without us noticing. ** Changed in: nut (Ubuntu Xenial) Status: Fix Committed => Invalid ** Changed in: nut (Ubuntu Xenial) Status: Invalid => Fix Released ** Changed in: nut (Ubuntu Xenial) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
If there is someone else who can reliably reproduce on Xenial still please ping me or update here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
For some reason I cannot get the package from xenial-proposed but before doing that I tried to reproduce on Xenial with 2.7.2-4ubuntu1. Turns out that I cannot reproduce so I'm not sure this SRU is worth pursuing. That said, if I somehow get the -proposed package eventually, I'll make sure to test it out. Here's my current test setup (*without* the -proposed package) unable to repro the original issue: # tail -n 5 /etc/nut/ups.conf [cyberpower] driver = usbhid-ups port = auto desc = "CyberPower CP685AVR-G" vendorid = 0764 # lsusb | grep Cyber Bus 003 Device 003: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS # ll /dev/bus/usb/003/003 crw-rw-r-- 1 root nut 189, 258 Aug 23 10:23 /dev/bus/usb/003/003 Yet, I don't seem to have manually mv'ed the udev file: # find /lib/udev/rules.d/ -name '*nut*' /lib/udev/rules.d/52-nut-usbups.rules So maybe it was fixed in a different way at some point after I reported the problem on Lucid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Hello Simon, or anyone else affected, Accepted nut into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nut/2.7.2-4ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nut (Ubuntu Xenial) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-xenial ** Changed in: nut (Ubuntu Trusty) Status: Triaged => Fix Committed ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Uploaded SRU changes for review - branches are linked -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
** Description changed:
- I hooked my new CyberPower UPS: CP685AVR-G on my Lucid server and got
- this error:
+ [Impact]
- Jan 15 12:06:33 xeon upsd[5441]: Can't connect to UPS [cyberpower]
(usbhid-ups-cyberpower): No such file or directory
- Jan 15 12:06:38 xeon upsmon[5445]: Poll UPS [cyberpower@127.0.0.1] failed -
Driver not connected
+ * Plugging in a USB controlled UPS solution does fail to execute the udev
+rules; Due to that the permissions are not set correctly
+
+ * Fix is a backport from upstream which only changes the numbering on the
+rule to execute at the right time.
+
+ [Test Case]
+
+ * Install nut-server
+ * Plug in a usb controlled UPS of your choice
+ * The device node created should be mode 664 and group "nut", but it is
+not.
+ * Install the proposed package
+ * (It also fixes but 1540008, so no need to replug anymore to test if
+ successful)
+ * it should now be created with proper permissions.
+
+ [Regression Potential]
+
+ * If people with the old set up have created something that would not be
+able to access anymore that could cuase issues, but before it was
+root:root and now nut:root; the group permission didn't change (was 6
+before) - so anything before could only access with root and they still
+can - therefore I consider this of low/no risk, yet in some obscure
+setups it might be one.
+
+ [Other Info]
+
+ * n/a
+
+ ---
+
+
+ I hooked my new CyberPower UPS: CP685AVR-G on my Lucid server and got this
error:
+
+ Jan 15 12:06:33 xeon upsd[5441]: Can't connect to UPS [cyberpower]
(usbhid-ups-cyberpower): No such file or directory
+ Jan 15 12:06:38 xeon upsmon[5445]: Poll UPS [cyberpower@127.0.0.1] failed -
Driver not connected
After trying many things, I found
https://bugzilla.redhat.com/show_bug.cgi?id=488368 that hint me in the
right direction. The required change was to rename the udev rule like
this:
- mv /lib/udev/rules.d/{5,6}2-nut-usbups.rules
+ mv /lib/udev/rules.d/{5,6}2-nut-usbups.rules
Now, everything works well, without requiring "user = root" in
/etc/nut/ups.conf because the udev rule now ensures the device file is
owned by the group "nut":
- # find /dev/bus/usb/ -ls
- 15360 drwxr-xr-x 10 root root 200 Jan 15 12:40
/dev/bus/usb/
- 15790 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/008
- 15800 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/008/001
- 15730 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/007
- 15740 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/007/001
- 15670 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/006
- 15680 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/006/001
- 15610 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/005
- 15620 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/005/001
- 15550 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/004
- 15560 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/004/001
- 15490 drwxr-xr-x 2 root root 80 Jan 15 12:40
/dev/bus/usb/003
- 21630 crw-rw-r-- 1 root nut Jan 15 12:49
/dev/bus/usb/003/002
- 15500 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/003/001
- 15430 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/002
- 15440 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/002/001
- 15370 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/001
- 15380 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/001/001
+ # find /dev/bus/usb/ -ls
+ 15360 drwxr-xr-x 10 root root 200 Jan 15 12:40
/dev/bus/usb/
+ 15790 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/008
+ 15800 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/008/001
+ 15730 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/007
+ 15740 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/007/001
+ 15670 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/006
+ 15680 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/006/001
+ 15610 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/005
+ 15620 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/005/001
+ 15550 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/004
+ 15560 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/004/001
+ 15490 drwxr-xr-x 2 root root 80 Jan 15 12:40
/dev/bus/usb/003
+ 21630 crw-rw-r-- 1 root nut
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/nut/+git/nut/+merge/329207 ** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/nut/+git/nut/+merge/329208 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
** Changed in: nut (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
I'd like to SRU that together with bug 1540008 on which we wait for Debian reply. Since this one over here waited for so long it will survive my PTO which is enough time for Debian to reply (or me to give up). Then I can SRU both together (as they are related to each other). I linked them together on my current todo and will revisit either on an update or in approx 3 weeks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
I don't even know how much pardon to beg on this one ... a lot for sure. I'm coming by trying to clear bugs that are dormant for too long - and this one is really way too long :-/ Anyway forget the past and work on it ... Now this is fixed in Zesty and later due to merging 2.7.4. Updating tasks and consider backporting https://github.com/networkupstools/nut/commit/040c800efad46ead9670077c9764360802d7aaf5 ** Also affects: nut (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nut (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: nut (Ubuntu Trusty) Status: New => Triaged ** Changed in: nut (Ubuntu Xenial) Status: New => Triaged ** Changed in: nut (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Closed the Debian bug as well as it has >=2.7.3 just as we do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
I believe caribou is working on the nut merge in zesty, at which point we can consider this for SRU. ** Changed in: nut (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Also affects Xenial. C'mon please integrate a later upstream version of nut. The bug has been fixed in 2014! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
** Changed in: nut (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Logged upstream, fixed and due with the next 2.7.3 release: https://github.com/networkupstools/nut/issues/140 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
** Bug watch added: Debian Bug tracker #721600 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721600 ** Also affects: nut (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721600 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Still affecting Trusty and the same workaround (mv
/lib/udev/rules.d/{5,6}2-nut-usbups.rules) works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1099947
Title:
driver unable to connect to CyberPower UPS using usbhid-ups driver
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
I can confirm this bug in raring. The fix in the originale bug report fixed it for me too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
Marking confirmed based on the fedora report. THe Makefile.am in raring still shows: ./scripts/udev/Makefile.am: udevrules_DATA += 52-nut-usbups.rules ./scripts/udev/Makefile.am: udevrules_DATA += 52-nut-ipmipsu.rules so I doubt it has been fixed there. ** Changed in: nut (Ubuntu) Importance: Undecided => High ** Changed in: nut (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
** Bug watch added: Red Hat Bugzilla #488368 https://bugzilla.redhat.com/show_bug.cgi?id=488368 ** Also affects: nut (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=488368 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099947 Title: driver unable to connect to CyberPower UPS using usbhid-ups driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
