DeviceKit-power is a little service that takes data from the kernel, and processes it so that it's easy to consume. Known consumers are gnome-power-manager and the XFCE battery widget. DeviceKit-power gets all the data from the kernel over the dbus service DeviceKit.
How to test
- yum install gnome-power-manager DeviceKit-power
- Remove or insert the AC adaptor, see changes in status using 'devkit --monitor' 'devkit-power --monitor'
- Using gnome-power-statistics you can obserbe the values in more detail. Make sure the percentages are all 0..100 and the value look sensible (for instance, Voltage is 0..20V, not 340034V). If this is the case please open a bug and dump the output of /sys/class/power_supply/*/*. If the values in /sys are wrong, then it's not a DeviceKit-power bug, it's a kernel bug or hardware fault.
- For the wakeups, ensure "devkit-power --wakeups" produces userspace and kernel wakeups, and that these are sensible. The first time you run this command, you'll probably get no data, but just try again in a few seconds, and you should have some values. We don't poll by default all the time, as this itself would use power.
- Run devkit-power-daemon in verbose mode: 'killall devkit-power-daemon; /usr/libexec/devkit-power-daemon --verbose'
- Crash test - devkit-power: use 'kill - SIGSEGV'; use invalid input
- Crash test - devkit-power-daemon: use dbus-send; use d-feet to execute methods
- All steps succefully executed with no SELinux errors or permission denials
- If you don't get changed signals in DeviceKit or DeviceKit-power then it's probably a kernel bug. This is known for some Sony laptops, and needs to be fixed in the kernel.
- devkit-power-daemon or devkit-power should not crash unless killed