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://hel
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 becaus
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)
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
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 r
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 noti
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 htt
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.
>
> # unpl
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
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 un
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 checke
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
** 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 Cy
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.
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
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
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
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
** 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, whi
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
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
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
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.ubu
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 notif
** 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 [cy
** 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, whi
** 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 man
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 togethe
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
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 man
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.launchpa
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
** 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 n
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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1099947
Title:
driver unable to connect to CyberPow
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 usi
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
39 matches
Mail list logo
