** Changed in: nut (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1099947
Title:
driver unable to connect to CyberPower UPS using usbhid-ups drive
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
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1099947
Title:
driver unable
** 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 a
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
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1099947
Title:
driver unable to conne
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
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1099947
Title:
driver unable to connect to Cybe
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
** 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
