Hi Martin,
thanks for your confirmation.
I'm now closing this bug.
Arnaud
** Changed in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
** Changed in: nut (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member
Hi Martin,
thanks for your confirmation.
I'm now closing this bug.
Arnaud
** Changed in: nut (Ubuntu)
Assignee: (unassigned) = Arnaud Quette (aquette)
** Changed in: nut (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member
Hi Arnaud,
I seem to have fixed my NUT problem by upgrading my system to Ubuntu
11.10. (upsd 2.6.1)
I never resolved the issue on 11.04, but your udev rules file probably
would have done it, I would guess!
Thanks for all your help!
Martin
On Tue, Jan 24, 2012 at 10:09 AM, Arnaud Quette
Hi Arnaud,
I seem to have fixed my NUT problem by upgrading my system to Ubuntu
11.10. (upsd 2.6.1)
I never resolved the issue on 11.04, but your udev rules file probably
would have done it, I would guess!
Thanks for all your help!
Martin
On Tue, Jan 24, 2012 at 10:09 AM, Arnaud Quette
Martin,
could you please check this bug report, and apply the udev related procedure
I've documented at the end of the thread:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200
Once applied, stop nut, unplug/replug your UPS USB cord, and restart nut
(at least the driver), and report
Martin,
could you please check this bug report, and apply the udev related procedure
I've documented at the end of the thread:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/578200
Once applied, stop nut, unplug/replug your UPS USB cord, and restart nut
(at least the driver), and report
I don't see any message related to usbhid-ups.
Is it started?
we can see hiddev0 (the device linked to the kernel module hiddev) loaded,
but nothing more.
So, try launching again nut, and check back /var/log/syslog for usb and nut
('ups') messages.
Arno
--
You received this bug notification
On Sat, Dec 17, 2011 at 3:45 AM, Arnaud Quette
aquette@gmail.comwrote:
I don't see any message related to usbhid-ups.
Is it started?
we can see hiddev0 (the device linked to the kernel module hiddev) loaded,
but nothing more.
So, try launching again nut, and check back /var/log/syslog
I don't see any message related to usbhid-ups.
Is it started?
we can see hiddev0 (the device linked to the kernel module hiddev) loaded,
but nothing more.
So, try launching again nut, and check back /var/log/syslog for usb and nut
('ups') messages.
Arno
--
You received this bug notification
On Sat, Dec 17, 2011 at 3:45 AM, Arnaud Quette
aquette@gmail.comwrote:
I don't see any message related to usbhid-ups.
Is it started?
we can see hiddev0 (the device linked to the kernel module hiddev) loaded,
but nothing more.
So, try launching again nut, and check back /var/log/syslog
Note for Ubuntu packagers:
- the original report was an issue with udev, and will be fixed with 2.6.3
upload,
- the 2nd one (Martin Ewing) was probably invalid, due to an already running
driver instance.
I've asked the user for some more feedback.
cheers,
Arnaud
--
You received this bug
Perhaps I should have added the following
/dev/usb:
$ ls -l
total 0
crw--- 1 root root 180, 97 2011-12-16 10:15 hiddev1
crw-rw 1 root lp 180, 0 2011-12-16 10:15 lp0
-Martin
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I do still have an issue with NUT on Ubuntu Natty (64 bit).
I attach my latest info. Will appreciate any further suggestions about
how to tame this problem - whether my configuration or otherwise.
Thanks!
Martin
** Attachment added: ups_problem.txt
Hi Martin,
I'm adding the nut users list, since other may be interested in.
2011/12/16 Martin Ewing martin.s.ew...@gmail.com
I do still have an issue with NUT on Ubuntu Natty (64 bit).
I attach my latest info. Will appreciate any further suggestions about
how to tame this problem - whether
On Fri, Dec 16, 2011 at 3:31 PM, Arnaud Quette
aquette@gmail.comwrote:
Hi Martin,
I'm adding the nut users list, since other may be interested in.
2011/12/16 Martin Ewing martin.s.ew...@gmail.com
I do still have an issue with NUT on Ubuntu Natty (64 bit).
I attach my latest info.
Note for Ubuntu packagers:
- the original report was an issue with udev, and will be fixed with 2.6.3
upload,
- the 2nd one (Martin Ewing) was probably invalid, due to an already running
driver instance.
I've asked the user for some more feedback.
cheers,
Arnaud
--
You received this bug
I do still have an issue with NUT on Ubuntu Natty (64 bit).
I attach my latest info. Will appreciate any further suggestions about
how to tame this problem - whether my configuration or otherwise.
Thanks!
Martin
** Attachment added: ups_problem.txt
Perhaps I should have added the following
/dev/usb:
$ ls -l
total 0
crw--- 1 root root 180, 97 2011-12-16 10:15 hiddev1
crw-rw 1 root lp 180, 0 2011-12-16 10:15 lp0
-Martin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Martin,
I'm adding the nut users list, since other may be interested in.
2011/12/16 Martin Ewing martin.s.ew...@gmail.com
I do still have an issue with NUT on Ubuntu Natty (64 bit).
I attach my latest info. Will appreciate any further suggestions about
how to tame this problem - whether
On Fri, Dec 16, 2011 at 3:31 PM, Arnaud Quette
aquette@gmail.comwrote:
Hi Martin,
I'm adding the nut users list, since other may be interested in.
2011/12/16 Martin Ewing martin.s.ew...@gmail.com
I do still have an issue with NUT on Ubuntu Natty (64 bit).
I attach my latest info.
Hi Martin,
2011/6/27 Martin Ewing martin.s.ew...@gmail.com
I have a very similar situation with my Belkin UPS on Natty (worked on
previous release).
See
$ lsb_release -rd
Description:Ubuntu 11.04
Release:11.04
martin@gimli:~$ aptitude show nut
Package: nut
State:
Arnaud,
Thanks for the reply! I imagine you are correct. I ran the command you
suggested (below). Apparently nut knows the device it should connect to,
but that device is busy. And running as root doesn't overcome the
problem... (And I don't know why I should have to make /var/run/nut,
2011/7/13 Martin Ewing martin.s.ew...@gmail.com
Arnaud,
Thanks for the reply! I imagine you are correct. I ran the command you
suggested (below). Apparently nut knows the device it should connect to,
but that device is busy. And running as root doesn't overcome the
problem... (And I
Hi Martin,
2011/6/27 Martin Ewing martin.s.ew...@gmail.com
I have a very similar situation with my Belkin UPS on Natty (worked on
previous release).
See
$ lsb_release -rd
Description:Ubuntu 11.04
Release:11.04
martin@gimli:~$ aptitude show nut
Package: nut
State:
Arnaud,
Thanks for the reply! I imagine you are correct. I ran the command you
suggested (below). Apparently nut knows the device it should connect to,
but that device is busy. And running as root doesn't overcome the
problem... (And I don't know why I should have to make /var/run/nut,
2011/7/13 Martin Ewing martin.s.ew...@gmail.com
Arnaud,
Thanks for the reply! I imagine you are correct. I ran the command you
suggested (below). Apparently nut knows the device it should connect to,
but that device is busy. And running as root doesn't overcome the
problem... (And I
creating usbhid-ups from source did it for me. Thanks
--
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/779512
Title:
nut-2.6.0-1ubuntu3 behavior regression
To manage notifications about
creating usbhid-ups from source did it for me. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779512
Title:
nut-2.6.0-1ubuntu3 behavior regression
To manage notifications about this bug go
I have a very similar situation with my Belkin UPS on Natty (worked on
previous release).
See
$ lsb_release -rd
Description:Ubuntu 11.04
Release:11.04
martin@gimli:~$ aptitude show nut
Package: nut
State: installed
Automatically installed: no
Version:
I have a very similar situation with my Belkin UPS on Natty (worked on
previous release).
See
$ lsb_release -rd
Description:Ubuntu 11.04
Release:11.04
martin@gimli:~$ aptitude show nut
Package: nut
State: installed
Automatically installed: no
Version:
** Changed in: nut (Ubuntu)
Importance: Undecided = Medium
** Changed in: nut (Ubuntu)
Status: New = Triaged
--
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/779512
Title:
** Changed in: nut (Ubuntu)
Importance: Undecided = Medium
** Changed in: nut (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779512
Title:
2011/5/14 Mr. Muskrat 779...@bugs.launchpad.net
Yes, I can confirm that this fixed the issue I reported.
thanks for the confirmation
Arnaud, thank you so much!
my pleasure Matt :)
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project
2011/5/14 Mr. Muskrat 779...@bugs.launchpad.net
Yes, I can confirm that this fixed the issue I reported.
thanks for the confirmation
Arnaud, thank you so much!
my pleasure Matt :)
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project
I thought I'd be able to just copy/paste the instructions one at a time
but I hit a few snags. I installed the missing prereqs and continued on.
(See config.txt.)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
I thought I'd be able to just copy/paste the instructions one at a time
but I hit a few snags. I installed the missing prereqs and continued on.
•[x4linux:~/nut] mmusgrove $ ./autogen.sh
bash: ./autogen.sh: No such file or directory
•[x4linux:~/nut] mmusgrove $ ls
trunk
•[x4linux:~/nut] mmusgrove
The output from the run is in usbhid-ups.txt.
** Attachment added: usbhid-ups.txt
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+attachment/2127333/+files/usbhid-ups.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
(config.txt didn't get uploaded the first time)
** Attachment added: config.txt
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+attachment/2127348/+files/config.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in
Hey Matt,
2011/5/13 Mr. Muskrat 779...@bugs.launchpad.net
I thought I'd be able to just copy/paste the instructions one at a time
but I hit a few snags. I installed the missing prereqs and continued on.
(...)
hem, sorry. I should have given you more info on build-deps and more
generally
Yes, I can confirm that this fixed the issue I reported. Arnaud, thank you
so much!
Matt
On Fri, May 13, 2011 at 3:18 PM, Arnaud Quette aquette@gmail.comwrote:
Hey Matt,
2011/5/13 Mr. Muskrat 779...@bugs.launchpad.net
I thought I'd be able to just copy/paste the instructions one at a
I thought I'd be able to just copy/paste the instructions one at a time
but I hit a few snags. I installed the missing prereqs and continued on.
•[x4linux:~/nut] mmusgrove $ ./autogen.sh
bash: ./autogen.sh: No such file or directory
•[x4linux:~/nut] mmusgrove $ ls
trunk
•[x4linux:~/nut] mmusgrove
I thought I'd be able to just copy/paste the instructions one at a time
but I hit a few snags. I installed the missing prereqs and continued on.
(See config.txt.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(config.txt didn't get uploaded the first time)
** Attachment added: config.txt
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+attachment/2127348/+files/config.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The output from the run is in usbhid-ups.txt.
** Attachment added: usbhid-ups.txt
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+attachment/2127333/+files/usbhid-ups.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hey Matt,
2011/5/13 Mr. Muskrat 779...@bugs.launchpad.net
I thought I'd be able to just copy/paste the instructions one at a time
but I hit a few snags. I installed the missing prereqs and continued on.
(...)
hem, sorry. I should have given you more info on build-deps and more
generally
Yes, I can confirm that this fixed the issue I reported. Arnaud, thank you
so much!
Matt
On Fri, May 13, 2011 at 3:18 PM, Arnaud Quette aquette@gmail.comwrote:
Hey Matt,
2011/5/13 Mr. Muskrat 779...@bugs.launchpad.net
I thought I'd be able to just copy/paste the instructions one at a
2011/5/11 Mr. Muskrat 779...@bugs.launchpad.net
Certainly!
excellent, here we go:
$ svn co svn://svn.debian.org/nut/trunk
$ ./autogen.sh
$ ./configure --prefix=/usr \
--exec-prefix=/ \
--sysconfdir=/etc/nut \
--mandir=/usr/share/man \
2011/5/11 Mr. Muskrat 779...@bugs.launchpad.net
Certainly!
excellent, here we go:
$ svn co svn://svn.debian.org/nut/trunk
$ ./autogen.sh
$ ./configure --prefix=/usr \
--exec-prefix=/ \
--sysconfdir=/etc/nut \
--mandir=/usr/share/man \
2011/5/11 Mr. Muskrat 779...@bugs.launchpad.net
Arnaud,
I hope that I captured enough of the information for you.
thanks Matt.
I'm still trying to find a solution that would satisfy everybody. not that
easy!
would you be able to test an svn version (just a checkout and minimum
compilation to
Certainly!
--
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/779512
Title:
nut-2.6.0-1ubuntu3 behavior regression
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
2011/5/11 Mr. Muskrat 779...@bugs.launchpad.net
Arnaud,
I hope that I captured enough of the information for you.
thanks Matt.
I'm still trying to find a solution that would satisfy everybody. not that
easy!
would you be able to test an svn version (just a checkout and minimum
compilation to
Certainly!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779512
Title:
nut-2.6.0-1ubuntu3 behavior regression
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hi Matt,
2011/5/10 Mr. Muskrat 779...@bugs.launchpad.net
Arnaud,
Here is what you have asked for.
Matt
•[x4linux:~] mmusgrove $ sudo service nut stop
[sudo] password for mmusgrove:
* Stopping Network UPS Tools
[ OK ]
•[x4linux:~]
Arnaud,
I hope that I captured enough of the information for you.
Matt
** Attachment added: usbhid-ups.txt
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+attachment/2123594/+files/usbhid-ups.txt
--
You received this bug notification because you are a member of Ubuntu
Server
Hi Matt,
2011/5/10 Mr. Muskrat 779...@bugs.launchpad.net
Arnaud,
Here is what you have asked for.
Matt
•[x4linux:~] mmusgrove $ sudo service nut stop
[sudo] password for mmusgrove:
* Stopping Network UPS Tools
[ OK ]
•[x4linux:~]
Arnaud,
I hope that I captured enough of the information for you.
Matt
** Attachment added: usbhid-ups.txt
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/779512/+attachment/2123594/+files/usbhid-ups.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Arnaud,
Here is what you have asked for.
Matt
•[x4linux:~] mmusgrove $ sudo service nut stop
[sudo] password for mmusgrove:
* Stopping Network UPS Tools
Arnaud,
Here is what you have asked for.
Matt
•[x4linux:~] mmusgrove $ sudo service nut stop
[sudo] password for mmusgrove:
* Stopping Network UPS Tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779512
Title:
nut-2.6.0-1ubuntu3 behavior regression
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
59 matches
Mail list logo