[Nut-upsuser] This one's a head-scratcher.

[Sam Varshavchik]

Bill Gee writes:

> However - The only reason I noticed is because I set up logwatch to include  
> output from upsc in the daily report.  When that went missing, I went  
> hunting.  If I did not have that daily logwatch, I would never have  
> noticed.  It would not surprise me if a lot of people are having a problem  
> and don't know it.

I noticed immediately. Many moons ago I had a misfortune of getting what  
turned out to be some UPS model with a known flaky USB port that kept going  
south, even with the manufacturer's Windows drivers. You supposedly were  
able to bring it back alive by power-cycling the USB port, but I never got  
that to work. Since those times I had a cron job that ran every 5 minutes  
and if it didn't get anything useful out of upsc it would bark in my  
mailbox. And it started barking.

> And another thing - This machine runs XFCE which by default includes a  
> battery monitor in the system tray.  That battery monitor works correctly  
> regardless of the status of nut.

Yup. Same here. It's apparently talking to the hardware directly.

> Fourth - There is an open bug report at RedHat about this.  The Fedora 37  
> package version 2.8.0-5 is supposed to have a fix.  The comments report  
> other problems with the package, hence it is not yet in the testing  
> repository.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2127269

The 2.8.0-5 does not work. Full stop. It's a simple, one line fix, but it  
hasn't gotten to, yet.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20221202/316e6a80/attachment.sig>