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
