Latest update for hal on Karmic causes failure to start completely
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dbus (Ubuntu) |
Fix Released
|
Critical
|
Scott James Remnant (Canonical) |
Bug Description
Binary package hint: hal
I just updated my Karmic test box to the latest version of the HAL, and the new version will not start properly by default. It just sits there saying "Starting hardware abstraction layer hald:" At this point, hald is actually running, but the script to start it has not terminated, locking the process. I found that I could work-around the problem by adding "--background" to the options for start-stop-daemon in the /etc/init.d/hal file, like this:
do_start() {
if [ ! -d $PIDDIR ]; then
mkdir -p $PIDDIR
chmod 770 $PIDDIR
chown $DAEMONUSER:
fi
start-stop-daemon --start --background --oknodo --pidfile $PIDFILE \
--exec $DAEMON -- $DAEMON_OPTS
}
Related branches
Changed in dbus (Ubuntu): | |
status: | Confirmed → Fix Released |
This is caused by a bug in the D-Bus timeout patches.
The HAL author was involved in the original discussions about those, so had pre-empted the use of INT_MAX in pending call timeout arguments - thus HAL was using code that had never been tested, since a version of D-Bus that supported INT_MAX to mean "no timeout" had not yet been written.
The first of the patches uploaded was the wrong one that had missing code; this has been rectified