Created attachment 605321 [details] copy of my /var/log/messages Description of problem: Excessive power source added/changed/removed events are generated by upower (several each second). The system becomes more and more sluggish as upowerd CPU usage gets progressively higher (time seems to vary but with xfce it takes about an hour for the average CPU usage to reach ~60% on my single-core hyperthreaded Atom, whereas with KDE the CPU usage gets up that high moments after logging in). How reproducible: Always when a battery is plugged in. Steps to Reproduce: 1. Start computer with a battery plugged in. 2. Observe. Actual results: Excessive bogus power source events are generated. CPU usage gets progressively higher (speed varies and appears to depend on exact software being used, but eventually it eats away an entire core). Expected results: No bogus power source events are generated. CPU usage should stay minimal. Workaround: The system appears to be working normally when no battery is present. Additional info: The following lines appear repeatedly in my /var/log/messages: Aug 18 19:35:16 [hostname] upowerd[800]: (upowerd:800): UPower-Linux-WARNING **: energy 48.051900 bigger than full 47.064000 Aug 18 19:35:18 [hostname] upowerd[800]: (upowerd:800): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s1 != NULL' failed and Aug 18 21:53:00 [hostname] upowerd[705]: ** (upowerd:705): WARNING **: Property get or set does not have an interface string as first arg I'm attaching my entire messages log for anyone interested. I don't think this is a hardware fault as all of Windows 7, Debian Squeeze and Slackware 13.37 work fine on this system. "upower --monitor" outputs the following: Monitoring activity from the power daemon. Press Ctrl+C to cancel. [22:22:36.032] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:36.032] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:36.033] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:36.033] device changed: /org/freedesktop/UPower/devices/line_power_AC0 [22:22:36.800] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:36.873] device removed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:38.079] device added: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:38.079] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:38.080] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:38.104] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:38.104] device changed: /org/freedesktop/UPower/devices/line_power_AC0 [22:22:38.918] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:38.933] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:39.017] device removed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:40.228] device added: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:40.245] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:40.257] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:40.273] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:40.273] device changed: /org/freedesktop/UPower/devices/line_power_AC0 [22:22:41.074] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:41.147] device removed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:42.392] device added: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:42.392] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:42.392] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:42.424] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:42.424] device changed: /org/freedesktop/UPower/devices/line_power_AC0 [22:22:43.230] device changed: /org/freedesktop/UPower/devices/battery_BAT0 [22:22:43.290] device removed: /org/freedesktop/UPower/devices/battery_BAT0
Created attachment 605322 [details] Brief output of "upower --monitor-detail"
This appears to be related to the following bugs: https://bugzilla.redhat.com/show_bug.cgi?id=838369 https://bugzilla.redhat.com/show_bug.cgi?id=743779
Created attachment 605434 [details] Brief output from "udevadm monitor"
I noticed that the Aug 19 09:02:32 [hostname] upowerd[681]: ** (upowerd:681): WARNING **: Property get or set does not have an interface string as first arg warnings only appear when running KDE. However, the following: Aug 18 23:13:27 [hostname] upowerd[705]: (upowerd:705): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s1 != NULL' failed Aug 18 23:13:27 [hostname] upowerd[705]: (upowerd:705): UPower-Linux-WARNING **: energy 47.985300 bigger than full 47.064000 appear regardless of which DE I'm running. Also, now upowerd CPU usage is around 70% right after login even under xfce, taking up an entire thread of my single-core Atom. I'm going to attach anything that I think might possibly be of use before I nuke the system and go back to Debian.
Created attachment 605435 [details] Brief output from "udevadm monitor --property"
A kernel upgrade (had the one that comes with the installation DVD, upgraded to latest which I think was 3.5?) appears to have partially fixed the problem (I thought it was a upower problem so I had previously updated only that and some related packages)... my messages log is no longer being spammed by the above assertion failures or energy level warnings, upowerd CPU usage appears more "normal" (fluctuating in the 1%-5% range which seems a bit high to me but is no big deal), and I'm no longer getting bogus device added/removed from upower. However, "upower --monitor" still outputs several device changed events each second, which I don't think is normal, and when in KDE I still get excessive "Property get or set does not have an interface string as first arg" errors in my messages. I think these two remaining issues are separated, though. Looks like I just saved myself a needless reinstall.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.