Package: hal
Version: 0.5.6-2
Severity: important

After update to 0.5.6-2 the /etc/dbus-1/event.d/20hal script locks up:
start-stop-daemon waits for hald process fork which apparently doesn't
occur.
/usr/sbin/hald actually forks but it seems unable to detach completely,
even when explicitly calling it with the '--daemon=yes' option.

Passing the dirty '--background' option to start-stop-daemon allowed me to
start the system (without that it hung at the 'Starting Hardware abstraction
layer: hald' message) with functional dbus+hal.

Mau

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (200, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686-smp
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages hal depends on:
ii  adduser               3.80               Add and remove users and groups
ii  dbus                  0.60-5             simple interprocess messaging syst
ii  libc6                 2.3.5-12.1         GNU C Library: Shared libraries an
ii  libdbus-1-2           0.60-5             simple interprocess messaging syst
ii  libdbus-glib-1-2      0.60-5             simple interprocess messaging syst
ii  libexpat1             1.95.8-3           XML parsing C library - runtime li
ii  libglib2.0-0          2.8.6-1            The GLib library of C routines
ii  libhal1               0.5.6-2            Hardware Abstraction Layer - share
ii  libusb-0.1-4          2:0.1.11-4         userspace USB programming library
ii  lsb-base              3.0-15             Linux Standard Base 3.0 init scrip
ii  pciutils              1:2.1.11-15.3      Linux PCI Utilities
ii  udev                  0.084-1            /dev/ and hotplug management daemo
ii  usbutils              0.71+cvs20051029-4 USB console utilities

hal recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to