On 3 August 2010 12:21, JB <jb.123abc(a)yahoo.com> wrote:
Chris Rouch <chris.rouch <at> gmail.com> writes:
> ...
> > [jb <at> localhost ~]$ ps aux |grep -i power
> > root 1439 0.0 0.3 6028 2364 ? S Aug01 0:04
> > /usr/libexec/upowerd
> > ...
> Bingo! For whatever reason, upowerd is not running. If I start it by
> hand everything works as expected. So now I need to find out why it's
> either not being started or is failing silently. According to the man
> page it should be started by dbus-daemon, which is running, "whenever
> an application calls into the org.freedesktop.UPower service"
> ...
Hi,
i would suggest that you make sure your system is up to date, so we can be
on the same page.
# yum check-update
# yum update
The system was updated yesterday, but I did this anyway and updated
everything suggested including a new kernel.
Next:
# yum list *upower*
Installed Packages
upower.i686 0.9.5-1.fc13 @updates
...
# yum reinstall upower
...
Did this too.
Now log out and back your KDE so services are restarted.
I rebooted.
Some testing:
# ps aux |grep -i power
Regardless of its presence above, try (it may start upowerd on demand):
- pull power cord (give it 10 secs time)
- plug in again
Any changes in battery/power icon or popup msgs ?
See again:
# ps aux |grep -i power
Still nothing.
At this point we have to do some more research:
- look into package files for anything related (config, rules, your machine)
# rpm -ql upower
# less /lib/udev/rules.d/95-upower*
# ...
- are you checking your system status mail (logwatch configured) ?
Root mail or user mail if root forwarded to.
- /var/log/* # messages, pm-*, ...
There could be errors, status hints reported.
There isn't :-(
I've no idea where the kde services log to - they don't appear to be
processes as such, and I can't work out how to start powerdevil
manually. I thought that there might be something in .xsession-errors,
but there are no power references therein.
- Google search (this is a package that was formerly DeviceKit-power,
got
rewritten, and causes upowerd problems in various contexts in some distros).
- search Bugzilla for reported problems/solutions/hints
- contact developer(s)
- become religious :-)
That's beginning to look like the best bet :-)
But in the meantime I'm going to try a yum reinstall of kde*, and then
if it is still failing I might try a complete re-install - if only to
see if it did once work and an update broke it.
Regards,
Chris