Red Hat Bugzilla – Bug 134347
Dbus fails on boot
Last modified: 2013-03-13 00:46:53 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040930
Description of problem:
I have been keeping my machine synchronized with rawhide for several
months. Today I updated to 10/1/04 rawhide and rebooted. The system
message bus failed on startup. The system log contains the following
Oct 1 10:32:30 redbud dbus-daemon-1: Unknown username "haldaemon" in
message bus configuration file
Oct 1 10:32:30 redbud messagebus: messagebus startup failed
Oct 1 10:32:31 redbud cups-config-daemon:
Oct 1 10:32:31 redbud cups-config-daemon: ** (process:3826): WARNING
**: DbusConfigDaemon: Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory
Oct 1 10:32:31 redbud cups-config-daemon: cups-config-daemon startup
I logged in as root and
(a) Verified that user "haldaemon" still exists (uid 100).
(b)Attempted to start dbus manually through Services configuration
utility. It failed with the same error message.
I have had no problems of this nature until today's update.
While preparing this report, I noticed that the Services utility
thought "hald" was stopped (despite the successful report in the
system log). I then confirmed that process "hald" was not running
using the system monitor.
Vendor: Dell Precision Workstation 420
Details: 2 1Ghz Pentium III cpus, Adaptec AIC-7899P U160/m SCSI, 256MB
Operating System: Fedora Rawhide (updated via yum as of 10/1/04)
*** Bug 134348 has been marked as a duplicate of this bug. ***
This was a glibc bug. Fix is being built into rawhide.
The update from rawhide on 10/2/04 resolved both the dbus and hal