Search Criteria
Package Details: powerpanel 1.4.2-3
Package Actions
| Git Clone URL: | https://aur.archlinux.org/powerpanel.git (read-only, click to copy) |
|---|---|
| Package Base: | powerpanel |
| Description: | CyberPower UPS daemon |
| Upstream URL: | https://www.cyberpowersystems.com/product/software/power-panel-personal/powerpanel-personal-linux/ |
| Licenses: | LicenseRef-CyberPower |
| Submitter: | 0x2501 |
| Maintainer: | 0x2501 |
| Last Packager: | 0x2501 |
| Votes: | 7 |
| Popularity: | 0.049941 |
| First Submitted: | 2022-11-24 15:52 (UTC) |
| Last Updated: | 2026-05-22 21:04 (UTC) |
Latest Comments
1 2 Next › Last »
0x2501 commented on 2026-05-24 19:19 (UTC)
lfcr: This is due to
pwrstatdtrying to connect toiotapi.cyberpower.combut the included libraries lack theSSL_set_tlsext_host_namesymbol, so it does not pass the SNI extension header during its TLS Client Hello, so Azure returns a generic*.azureedge.netcertificate which is obviously different from what it expects.You can ignore this error.
lfcr commented on 2026-05-24 12:42 (UTC)
I still get the error: pwrstatd[755]: BIO_do_connect failed pwrstatd[755]: OpenSSL error: error:1416F086:SSLroutines:tls_process_server_certificate:certificate verify failed
(but no problem with -status)
GYDev commented on 2026-05-22 21:15 (UTC)
My issue seems to have been fixed, thank you so much for your help!
0x2501 commented on 2026-05-22 20:55 (UTC) (edited on 2026-05-22 21:05 (UTC) by 0x2501)
Ah, it seems that the client "writes" to the socket
/var/pwrstatd.ipcwhich is dynamically created bypwrstatdasroot:rootwith 755 permissions.Add the following snippet as an override using
systemctl edit pwrstatdor wait a bit and let me send an update.I will send a fix, as I realize I might have inadvertently broken users setups. Edit: fix out
GYDev commented on 2026-05-22 20:10 (UTC)
I tried adding execute permissions to /usr/bin/pwrstat for the power group and it allowed execution for
pwrstat, but it wont allow execution for thepwrstat -statussubcommand. I usually run the command via a script + systemd service/timer so that i can keep track of my power usage on my taskbar, so Im not sure if i can enter my sudo password for that use case. Is my usecase just not viable anymore?0x2501 commented on 2026-05-22 20:05 (UTC)
GYDev, the PKGBUILD now follows CyberPower's install script, which restricts
pwrstatto root-only execution. You can either usesudo pwrstator change its permissions and allow execution by other users (sudo chmod 755 /usr/bin/pwrstat). Hope that helps.GYDev commented on 2026-05-22 19:57 (UTC)
After the recent update I am no longer able to run
pwrstat -statusdespite my user being in the power group. I simply get an output of "Permission denied" and there arent any other logs to point me in the direction of what is going wrong, at least that ive seen. Do you have any ideas that could point me in the right direction?dbb commented on 2026-05-22 14:20 (UTC)
Works for me, thanks.
0x2501 commented on 2026-05-22 05:56 (UTC)
Thanks @dbb. I decided to use the static libraries provided by cyberpower instead of having to installing old dependencies. It should work now (at least, it did on my install). Please let me know if you encounter any issues.
dbb commented on 2026-05-20 11:31 (UTC)
Immediate issue:
openssl-1.1is still required for this to function, notopenssl:Other issues:
I don't think
usr/lib/systemd/system/pwrstatd.serviceshould be in thebackuparray. Users shouldn't be modifying that file directly, and if they want to change its behavior they should be using systemd drop-in files either manually or viasystemctl edit pwrstatd.service.You can have architecture specific
sourceand checksum arrays (i.e.source_x86_64,source_i686,sha256sums_x86_64, andsha256sums_i686), no need to explicitly check against$CARCH. I assume thei686build is currently broken as is since thesha256sumsarray isn't modified.1 2 Next › Last »