just some comments to ease your audit:
- all the mentioned functions (upslog*, upsdebug*, fatal*) point to
vupslog, and vupslog use only numbered copy functions,
- we centralize as much as possible such kind of functions to manage
the security and reliability of NUT,
- we enforce in general the use
well, that will have to wait for NUT 2.4, so HH+1...
--
main inclusion report
https://bugs.launchpad.net/bugs/182790
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
Hi Jamie,
2008/2/8, Jamie Strandboge <[EMAIL PROTECTED]>:
> Arnaud,
>
> I was curious as to why the Debian packaging doesn't do the 'security
> domains' as listed in:
> http://www.networkupstools.org/faq/
>
> or even the chrooting as in:
> http://www.networkupstools.org/doc/2.2.0/chroot.html
wel
2008/2/7, Siegfried Gevatter (RainCT) <[EMAIL PROTECTED]>:
> If Sunday version 2.2.2 isn't yet in Debian, please resubscribe u-u-s so
> that we get this into Ubuntu before Feature Freeze. Thanks.
>
> --
> [sync request] nut 2.2.1 from debian unstable
> https://bugs.launchpad.net/bugs/185565
> You r
Public bug reported:
Binary package hint: wmnut
I've uploaded wmnut 0.62-2 in Debian.
It fixes and update several bugs (build failing, many lintian problems, ...)
** Affects: wmnut (Ubuntu)
Importance: Undecided
Status: New
--
[sync request] wmnut 0.62.2
https://bugs.launchpad.ne
I've uploaded nut 2.2.1-1 yesterday in Debian.
I've logged a sync request too:
https://bugs.edge.launchpad.net/ubuntu/+source/nut/+bug/185565
--
main inclusion report
https://bugs.launchpad.net/bugs/182790
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bu
Public bug reported:
Binary package hint: nut
nut 2.2.1 has been released in Debian.
please sync.
** Affects: nut (Ubuntu)
Importance: Undecided
Status: New
--
[sync request] nut 2.2.1
https://bugs.launchpad.net/bugs/185565
You received this bug notification because you are a mem
guys,
first; it's a pleasure to see this since I wasn't aware of ;-)
I took the liberty to complete it a bit the report.
some more notes:
- 2.2.1 packages are underway (should be done by the end of this
week). I've been busy with many things upstream... and real life
> - the shared libraries sho
+1 (for the Elisa Media Center and Ubuntu Media Center which use
Coherence)
--
Request for sync in Hardy
https://bugs.launchpad.net/bugs/184766
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
this has been fixed in the 2.2.0 release: nut-usb is now part of the
nut package, and the udev rule is installed as 52_nut-usbups.rules
thanks for your report,
Arnaud
--
Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com
Network UPS Tools (NUT) Project Leader - http:/
thanks guys!
I take this opportunity to mention that there is a blueprint for Hardy
Heron linked to nut 2.2.0:
https://blueprints.edge.launchpad.net/ubuntu/+spec/integrated-usb-ups-support
Arnaud
--
Linux / Unix Expert R&D - MGE Office Protection Systems - http://www.mgeops.com
Network UPS Tools
Hi Sarah,
This is linked to 2 points:
- nut was previously in the dialout group. There was a discussion
years ago on the Debian devel ml about this, and it was decided to
remove it for security reason, and add a mention in the README.Debian
file (check changelog.Debian/0.44.1-3),
- I've planned fo
Hi Luca,
thanks for this update.
Two side notes:
- I've added a blueprint for HH and the integrated UPS support:
https://blueprints.edge.launchpad.net/ubuntu/+spec/integrated-usb-ups-support
This is really the way forward in terms of desktop integration, and
user experience (the simplest way, and
2007/10/15, Andrew <[EMAIL PROTECTED]>:
> Public bug reported:
>
> Binary package hint: nut
>
> I have just switched over from debian testing and cannot get my Belkin
> USB UPS working with kubuntu gutsy on amd64.
>
> I was surprised to see that nut is still on 2.0.5 in ubuntu. My UPS
> requires th
Hi Seb,
thanks for your action. But you also need to import python-coherence, otherwise
elisa won't be working fine.
see https://bugs.launchpad.net/ubuntu/+source/elisa/+bug/128205
As mentioned, I've already updated and uploaded 0.4 into Sid.
thanks.
--
upgrade elisa to 0.3.1
https://bugs.lau
the package nut-usb has to be installed ;-)
nut 2.2.0 packages will fixed that since I've merged nut-usb into nut...
--
bcmxcp_usb powerware 3105 can not connect to UPS.
https://bugs.launchpad.net/bugs/132998
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I've uploaded 0.4.0 into Sid...
--
import python-coherence depends from Debian
https://bugs.launchpad.net/bugs/128205
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
0.0.5 has hit Sid, and should hit testing by August 9th.
--
import python-lirc depends from Debian
https://bugs.launchpad.net/bugs/128473
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
coherence 0.2.1 has hit Sid, and is should hit testing by August 6th.
I'll then upload 0.4.0 (only need to remove the python-soappy dependency).
--
import python-coherence depends from Debian
https://bugs.launchpad.net/bugs/128205
You received this bug notification because you are a member of Ubu
fully right Stephen,
I've developed the following plans, since I took over the project 2
years ago, to address this problem:
- make nut configless for USB UPS. NUT 2.2.0 has opened the door to
the HAL bridge.
but for those still needing a classic NUT installation (for
redundancy, network UPS serve
I meant that it's in the NEW queue...
--
import python-lirc depends from Debian
https://bugs.launchpad.net/bugs/128473
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
Public bug reported:
Binary package hint: elisa
python-lirc is needed for remote controls support through LIRC.
The Debian Sid upload is pending:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430642
** Affects: elisa (Ubuntu)
Importance: Undecided
Status: New
--
import python
Public bug reported:
Binary package hint: elisa
coherence is needed for Elisa to support uPnP.
it's only available in Debian experimental for the moment (I'm checking with
[EMAIL PROTECTED] why, since I don't remember why it hasn't reached Sid):
http://packages.debian.org/cgi-bin/search_package
thanks a lot Michael.
I just realize that I will have to open one more bug for coherence (UPnP
support, already in Debian), and another for pylirc (remote controls support,
not yet uploaded to Debian)
--
import python-pigment depends from Debian
https://bugs.launchpad.net/bugs/127347
You receiv
Public bug reported:
Binary package hint: elisa
pigment is mandatory to run Elisa:
http://packages.debian.org/unstable/python/python-pigment
currently, elisa is not installable.
** Affects: elisa (Ubuntu)
Importance: Undecided
Status: New
--
import python-pigment depends from D
** Description changed:
Binary package hint: lirc
A new lirc version was released last month (0.8.2), and includes the new
- lirchw.db file. It needs packaging for gutsy yet.
+ lirc.hwdb file. It needs packaging for gutsy yet.
--
Package new lirc version
https://bugs.launchpad.net/bugs/
Hy Russel,
2007/5/31, Russel Winder <[EMAIL PROTECTED]>:
> Arnaud,
>
> Thanks for getting back on this one quickly. Much appreciated.
>
> > just a question: have plugged your UPS USB cord before or after having
> > installed nut?
> > the udev script is there to do the job, but I've recently made
Hi Russel,
just a question: have plugged your UPS USB cord before or after having
installed nut?
the udev script is there to do the job, but I've recently made a
change to the package to fire up the udev restart upon install.
Otherwise, if the UPS USB cord was already plugged in, the device is
not
2007/5/30, Laur Mõtus <[EMAIL PROTECTED]>:
> I believe this function to be VERY necessary, it would really speed up
> the translation process for me.
seconded.
I mainly abandoned my translation work through rosetta (not upstream)
due to this lack!
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS
Public bug reported:
Binary package hint: network-manager
switching from home (wifi + dhcp) to work (ethernet + static conf), after an
hibernation, the switch is fine for the interface and address...
But the DNS are not updated: the displayed one in NetworkManager are fine, but
resolv.conf isn'
*** This bug is a duplicate of bug 44 ***
https://bugs.launchpad.net/bugs/44
I second that proposition.
I had to fix a typo error in synaptic, and ended up attaching the patch
to mvo...
--
request: search functionnality for Rosetta
https://bugs.launchpad.net/bugs/35801
You received this bug
IIRC, tripplite has not a compliant HID implementation.
So the HAL embedded addon has chance not to work properly...
we have addressed it in the NUT newhidups / usbhid-ups driver.
Your salvation will come when I've finished the NUT to HAL bridging I'm
currently working on.
There is already some b
This bug will be addressed upstream by a sub project of the Ubuntu Media
Center Team.
https://wiki.ubuntu.com/RemoteControls
I have already started to discuss with Christoph Bartelmus (LIRC project
leader) and Jon Smirl, who has started some work.
Kernel hackers needed. If you're interested in,
This bug will be addressed upstream by a sub project of the Ubuntu Media
Center Team.
https://wiki.ubuntu.com/RemoteControls
I have already started to discuss with Christoph Bartelmus (LIRC project
leader) and Jon Smirl, who has started some work.
Kernel hackers needed. If you're interested in,
This bug will be addressed upstream by a sub project of the Ubuntu Media
Center Team.
https://wiki.ubuntu.com/RemoteControls
I have already started to discuss with Christoph Bartelmus (LIRC project
leader) and Jon Smirl, who has started some work.
Kernel hackers needed. If you're interested in,
seems krb5-config is needed too.
I've got this without it:
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not
stable yet
warnings.warn("apt API not stable yet", FutureWarning)
Traceback (most recent call last):
File "/usr/bin/authtool-gtk", line 552, in
app =
Public bug reported:
Binary package hint: linux-image-2.6-amd64-generic
having an USB KVM (mine is a Avocent SwitchView USB, 4 ports)
- boot the system,
- get an ssh access to monitor the log,
- switch to another box, using the KVM
there you are:
linux-amd64 kernel: [ 2094.596780] CR2:
I get the same here with a QC Communication STX Plus
(046d:08d7)
--
Newer Logitech Quickcams not properly detected
https://launchpad.net/bugs/70532
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
there is a debian bug already filled on this subject, which I've
leaved explicitly open.
I've explained there that I will integrate in nut 2.2 a tool to
generate configuration, as well as a library to allow external apps
creation.
for the time being, the /usr/share/doc/nut/example/ will help you ;
2007/1/22, Kai Kasurinen <[EMAIL PROTECTED]>:
> Thanks for the bug report. I'm closing it because the bug has been fixed
> in Feisty.
not completely in fact.
it has fully been solved in 2.0.4-3, so an update to 2.0.5 would do too.
thanks Kai,
Arnaud
--
Linux / Unix Expert - MGE UPS SYSTEMS - R&D
Public bug reported:
Binary package hint: nut
the upstream and deb are available for 2.0.5.
there are many many many fixes and improvements that Ubuntu should benefit
from, such as improved USB support, many new supported UPSs, LSB compliant init
script, ...
** Affects: nut (Ubuntu)
Impor
Public bug reported:
Binary package hint: gnome-power-manager
already fixed upstream (http://bugzilla.gnome.org/show_bug.cgi?id=395021).
I've asked the upstream for a 2.17.5 release, so that the problem can be fixed
in ubuntu.
As a side note, this is related to the UPS support in HAL through NU
as side notes:
- this bug hits all *buntu since the hotplug removal (shouldn't impact
dapper?!),
- a temporary workaround is described here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396704;msg=20
quote:
A temporary solution is to edit /etc/udev/nut-usbups.rules and replace every
(or at l
Public bug reported:
I'm a bit new to the ndiswrapper thingies, so I might have missed
something obvious, though I've searched a bit around.
After having played a bit on edgy with the 1.18 release, I get what
seems to be a standard msg for unsync'ed part of ndiswrapper: " Error
inserting ndiswrap
uh, right. I mixed up between fix commited and released.
so I wasn't wrong, simply too tired (was around 2 in the morning...)
thx for your update and action Barry ;-)
--
nut (Network UPS) does not restart after suspend.
https://launchpad.net/bugs/45114
--
ubuntu-bugs mailing list
ubuntu-bugs@l
digging a bit more the panel issue, I found bug 52405.
As I've mentioned on it, removing menu-xdg solve the panel issue *and* the gpm
issue.
So it seems that it was linked to the panel eating too much cpu.
--
systray doesn't show up
https://launchpad.net/bugs/57516
--
ubuntu-bugs mailing list
argh, I forgot to add that it was due to the fact that I'm a "repented"
kde/kubuntu user, as it seems menu-xdg isn't used on gnome (strange btw,
as I though it was a shared mechanism for both kde and gnome!)
** Changed in: gnome-power (upstream)
Status: Unconfirmed => Rejected
** Changed i
for me, gp was eating up to 90 %
removing menu-xdg solved the issue, though it forced me to also remove the side
kubuntu packages. As some others, I'd like to keep both. So a long term
solution would be appreciated ;-)
Also note that it had side effect, like the one mentionned in lp bug
57516...
Public bug reported:
Binary package hint: gnome-power-manager
[side note: I'm freshly back to gnome, so I might miss something
obvious...]
I've switched to edgy a few days ago, mainly to test gpm and my work in
NUT for it (I'm currently testing gpm on a laptop). At first, the tray
was showed, bu
replying to me: ok, I've misread the status. Fix commited means closed,
but I got wrong since the other bug assigned to me "disapear" from the
assigned to me as long as these have a fix commited. This one is
indirectly assigned to me through my nut package... QED and sorry for
the noise (I'm not ye
this bug has been (not so) long fixed, at least in edgy and possibly in dapper
(IIRC) and so it should be closed.
This might not have been done since no distrib is set!
--
nut (Network UPS) does not restart after suspend.
https://launchpad.net/bugs/45114
--
ubuntu-bugs mailing list
ubuntu-bugs
this bug has been (not so) long fixed, at least in edgy and possibly in dapper
(IIRC) and so it should be closed.
This might not have been done since no distrib is set!
Or should I consider it upstream, and so close it myself?
--
nut (Network UPS) does not restart after suspend.
https://launchpa
** Changed in: nut (Debian)
Status: Unconfirmed => Fix Released
--
fails to start because of change to /var/run
https://launchpad.net/bugs/6679
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: nut (Debian)
Status: Unconfirmed => Fix Released
--
Hotplug dependency in nut-usb package
https://launchpad.net/bugs/6585
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
avoid -1, and prefer to use 2.0.4-2 as per http://bugs.debian.org/358696
--
[Sync Request] nut 2.0.4-1
https://launchpad.net/bugs/54981
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
201 - 255 of 255 matches
Mail list logo
