From time to time, on start of KDE4 (with 'startx') there are messages about a problem with the power daemon; the pop-ups are unreadable due to their short presence, but in the log of the startx-session I can capture: $ fgrep Power startkde.log.last 18:19:23: kded(940): KDE Power Management System init failed! The result is that in the tray no battery symbol is presented. Until now I could only fix this with a reboot, not with a restart of KDE4. This is with: 11-CURRENT r285885 on amd64 and KDE from ports r392920. Reproducible: Sometimes Steps to Reproduce: 1. boot and login into alpha console 2. startx 3. as I said: not always reproduceable
*** Bug 356332 has been marked as a duplicate of this bug. ***
I have had it today again and the situation re/ hald is like this in the moment of 'startx': 885 - Ds 0:00,01 /usr/local/sbin/hald 890 - I 0:00,03 hald-runner 764 v0- I 0:00,01 /usr/local/sbin/hald 988 v0 R 0:00,00 fgrep hal 06:42:19: startkde: Starting up... 06:42:20: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) 06:42:20: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. ... The proc 885 can not be killed, not even with -9; only a re-boot solves the situation; I instructed the start of hald with debug logging and it says on boot: $ fgrep hal /var/log/messages Dec 9 08:28:58 c720-r285885-amd64 hald[965]: 08:28:58.772 [E] hald_runner.c:676: Error running 'hald-addon-input': org.freedesktop.HalRunner.Failed: Start request failed Dec 9 08:28:58 c720-r285885-amd64 hald[965]: 08:28:58.772 [E] hald_dbus.c:3579: Cannot start singleton addon hald-addon-input for udi /org/freedesktop/Hal/devices/atkbd_0 Dec 9 08:28:58 c720-r285885-amd64 hald[965]: 08:28:58.772 [E] hald.c:137: Couldn't add device to singleton Don't know if the above messages are related to the problem. Right now the battery is shown fine and the hald situation is: $ ps ax | fgrep hal 965 - Ss 0:03,16 /usr/local/sbin/hald --verbose=yes --use-syslog 970 - I 0:00,04 hald-runner 1724 - S 0:00,41 /usr/local/libexec/gvfs-hal-volume-monitor
I think, we can close this issue here; Seems to be really a hald problem, and not a KDE4 problem; right now it occured again and qdbus only says: $ qdbus --system :1.2 org.freedesktop.ConsoleKit :1.25 :1.26 :1.27 :1.28 :1.3 :1.31 :1.32 :1.4 org.freedesktop.PolicyKit1 :1.40 org.freedesktop.DBus i.e. nothing about hald :-( Maybe the error message in KDE should a) not only popup for a second and b) contain something about the real problem, i.e. that hald can not be contacted;
Thanks.