[Bug 71092] hald-runner crashes making hal unusuable.

[Sivan Greenberg]

Public bug reported:

using hal 0.5.8.1-3ubuntu2 , hal-device-manager (currently what I've
managed to stop are mainly Python apps using dbus->Hal)  and similar
apps (like hubackup) are able to crash hald-runner such that it never
comes back (is it a daemon at all?).

simply restarting dbus (which triggers restart of its dependnet
services) fixes this until the next time hal-device-manager is run.

lshal runs okay, but outputs this:

process 18899: Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application.
  D-Bus not built with -rdynamic so unable to print a backtrace
Aborted (core dumped)


The error received on the hal-device-manager console output:
<gtk.Menu object (GtkMenu) at 0xb670cd24>
Introspect error: Message did not receive a reply (timeout by message bus)
Traceback (most recent call last):
  File "/usr/bin/hal-device-manager", line 20, in ?
    DeviceManager()
  File "/usr/share/hal/device-manager/DeviceManager.py", line 98, in __init__
    self.update_device_list()
  File "/usr/share/hal/device-manager/DeviceManager.py", line 198, in update_device_list
    self.virtual_root = self.build_device_tree()
  File "/usr/share/hal/device-manager/DeviceManager.py", line 269, in build_device_tree
    properties = device_dbus_obj.GetAllProperties(dbus_interface="org.freedesktop.Hal.Device")
  File "/var/lib/python-support/python2.4/dbus/proxies.py", line 25, in __call__
    ret = self._proxy_method (*args, **keywords)
  File "/var/lib/python-support/python2.4/dbus/proxies.py", line 102, in __call__
    reply_message = self._connection.send_with_reply_and_block(message, timeout)
  File "dbus_bindings.pyx", line 455, in dbus_bindings.Connection.send_with_reply_and_block
dbus_bindings.DBusException: The name org.freedesktop.Hal was not provided by any .service files

after this hald-runner is no longer reported in ps aux | grep hal and then even lshal cannot use hal:
error: libhal_ctx_init: (null): (null)
Could not initialise connection to hald. 
 Normally this mean the HAL daemon (hald) is not running or not ready.
lshal.c 689 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set.

** Affects: hal (Ubuntu)
     Importance: Undecided
         Status: Unconfirmed

-- 
hald-runner crashes making hal unusuable.
https://launchpad.net/bugs/71092