[Expired for nut (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nut (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850672
Title:
[Expired for nut (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nut (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
** Changed in: nut (Ubuntu)
Status: New = Incomplete
--
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/850672
Title:
port = auto does not work with bcmxcp_usb (powerware 5115)
To
** Changed in: nut (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850672
Title:
port = auto does not work with bcmxcp_usb (powerware 5115)
To manage
Correction to above: Udevadm-trigger does seem to get fired. Symptoms
looked indentical but might be a different issue this time.
crw-rw-r-- 1 root nut 189, 258 Dec 26 02:00 /dev/bus/usb/003/003
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Reinstalled nut on 14.04.1 with identical changes in config files, got
same issue again.
udevadm trigger does not seem to get activated, not even by replugging ups.
(command used to start it right after install + editing config files: sudo
service nut-server restart)
Bus 003 Device 003: ID
Trusty issue seems to be different from original one, to actually get
the error message printed I had to use:
$ sudo -g nut -u nut upsdrvctl start
... which revealed an unrelated documentation bug in newer ups.conf.
Might file another bug for that unless one is already filed.
** Tags removed:
Correction to above: Udevadm-trigger does seem to get fired. Symptoms
looked indentical but might be a different issue this time.
crw-rw-r-- 1 root nut 189, 258 Dec 26 02:00 /dev/bus/usb/003/003
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Reinstalled nut on 14.04.1 with identical changes in config files, got
same issue again.
udevadm trigger does not seem to get activated, not even by replugging ups.
(command used to start it right after install + editing config files: sudo
service nut-server restart)
Bus 003 Device 003: ID
Trusty issue seems to be different from original one, to actually get
the error message printed I had to use:
$ sudo -g nut -u nut upsdrvctl start
... which revealed an unrelated documentation bug in newer ups.conf.
Might file another bug for that unless one is already filed.
** Tags removed:
[Expired for nut (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nut (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
[Expired for nut (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nut (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850672
Title:
Setting as incomplete per aquette@'s comment.
** Changed in: nut (Ubuntu)
Importance: Undecided = Medium
** Changed in: nut (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
Setting as incomplete per aquette@'s comment.
** Changed in: nut (Ubuntu)
Importance: Undecided = Medium
** Changed in: nut (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
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/850672
Title:
port = auto does not work with bcmxcp_usb (powerware 5115)
To manage notifications about this bug go to:
After changing port back to auto it seems to work. System has not been rebooted
since installing nut.
Could this be some form of a race condition as speculated in other bug reports?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut
2011/9/15 Tuomas Heino iheino...@cc.hut.fi
After changing port back to auto it seems to work. System has not been
rebooted since installing nut.
Could this be some form of a race condition as speculated in other bug
reports?
not at all.
the value of port, as for other NUT USB drivers, is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850672
Title:
port = auto does not work with bcmxcp_usb (powerware 5115)
To manage notifications about this bug go to:
After changing port back to auto it seems to work. System has not been rebooted
since installing nut.
Could this be some form of a race condition as speculated in other bug reports?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
2011/9/15 Tuomas Heino iheino...@cc.hut.fi
After changing port back to auto it seems to work. System has not been
rebooted since installing nut.
Could this be some form of a race condition as speculated in other bug
reports?
not at all.
the value of port, as for other NUT USB drivers, is
20 matches
Mail list logo
