https://bugs.kde.org/show_bug.cgi?id=356331
--- Comment #2 from Matthias Apitz <g...@unixarea.de> --- 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 -- You are receiving this mail because: You are watching all bug changes.
