You are not logged in.
I'm having an odd problem with the apcupsd (3.10.17-1) package in the Community repo. I'm running a Back-UPS RS 1000 according to apcaccess. It was working swimmingly through a USB connection until recently. I have the timeout set to 0 and the automatic shutdown set when the battery reaches 5%.
After my system-wide upgrade, there popped up a problem. Although 'apcaccess status' tells me that my unit is online and the battery charge is at 100% and the load and timeleft is reasonable, the daemon doesn't actually use this information when a switch to battery happens.
When there is a switchover from a power-outage, the system shuts down (despite timeout set to 0). Later when I check the log in /var/log/apcupsd.events, it says, for example,
Fri Jul 15 19:24:11 EDT 2005 apcupsd 3.10.17 (18 March 2005) unknown startup succeeded
Sat Jul 16 18:11:26 EDT 2005 Power failure.
Sat Jul 16 18:11:26 EDT 2005 Reached remaining time percentage limit on batteries.
Sat Jul 16 18:11:26 EDT 2005 Initiating system shutdown!
Sat Jul 16 18:11:26 EDT 2005 User logins prohibited
Sat Jul 16 18:11:28 EDT 2005 apcupsd exiting, signal 15
Sat Jul 16 18:11:28 EDT 2005 apcupsd shutdown succeededThe first line being when I booted my system. As you can see, it thinks it reached the 5% limit, despite telling me it had 100% earlier. It's a new battery and the hardware is not bugging me in any way.
I've read other people having some trouble with USB after recent upgrades of DBUS (I'm running 0.34-1), or perhaps it is UDev (060-5). Could this be related? I'm not sure which upgrade did it because I don't test my apc unit after every pacman -Syu.
Offline
Well, the problem mysteriously disappeared (apparently). I did update udev... maybe that has something to do with it. Did no one else have this problem?
Offline