'gkrellm plugin displaying the current processor speed'
=====
There is such a thing as having Process so things get handled Properly. And then there is such a thing as getting so bogged down in process that trivial bugs don't get fixed for 12 years! This is a one-line fix in a text file:
--- gkrellmapcupsd-0.02/debian/control.orig 2005-07-05 15:52:37.000000000 -0700
+++ gkrellmapcupsd-0.02/debian/control 2022-07-21 20:45:21.402880151 -0700
@@ -8,7 +8,7 @@
Package: gkrellmapcupsd
Architecture: any
Depends: ${shlibs:Depends}, gkrellm (>= 2.1.4)
-Description: gkrellm plugin displaying the current processor speed
+Description: gkrellm plugin displaying UPS info from apcupsd
This gkrellm plugin shows information about your UPS controlled by
apcupsd. apcupsd.status must be enabled and STATTIME should be set
to a low value.
=====
I have no idea if this thing works, have never even installed it. Just ran into it in looking at packages.
If it were fixed Right Now, it could have been reported in 10.04 'lucid lynx' and fixed in time for L's next time in the spotlight, 23.04 'lurching lunatic'!
Howdy. I just happened to notice this on my crusty old LinuxMint 17.1 (trusty-based) system, so I checked and ... it's still a bug in kinetic:
https:/ /packages. ubuntu. com/kinetic/ gkrellmapcupsd
'gkrellm plugin displaying the current processor speed'
=====
There is such a thing as having Process so things get handled Properly. And then there is such a thing as getting so bogged down in process that trivial bugs don't get fixed for 12 years! This is a one-line fix in a text file:
--- gkrellmapcupsd- 0.02/debian/ control. orig 2005-07-05 15:52:37.000000000 -0700 0.02/debian/ control 2022-07-21 20:45:21.402880151 -0700
+++ gkrellmapcupsd-
@@ -8,7 +8,7 @@
Package: gkrellmapcupsd
Architecture: any
Depends: ${shlibs:Depends}, gkrellm (>= 2.1.4)
-Description: gkrellm plugin displaying the current processor speed
+Description: gkrellm plugin displaying UPS info from apcupsd
This gkrellm plugin shows information about your UPS controlled by
apcupsd. apcupsd.status must be enabled and STATTIME should be set
to a low value.
=====
I have no idea if this thing works, have never even installed it. Just ran into it in looking at packages.
If it were fixed Right Now, it could have been reported in 10.04 'lucid lynx' and fixed in time for L's next time in the spotlight, 23.04 'lurching lunatic'!