Sjoerd Simons wrote:
Which hack ?
This one:
In file /etc/udev/hal.rules change
ENV{SEQNUM}=="[0-9]*", ENV{UDEVD_EVENT}=="1",
RUN+="/usr/lib/hal/hal.hotplug"
with
ENV{SEQNUM}=="[0-9]*", ENV{UDEVD_EVENT}=="1",
RUN+="/usr/lib/hal/hal.hotplug $env{SUBSYSTEM}"
Debian Sid on AMD64, hal 0.5.6-2 and udev 0.084-1.
Does /etc/udev/hal.rules contain
``RUN+="socket:/org/freedesktop/hal/udev_event"'' ?
Yes it does:
[EMAIL PROTECTED]:~$ cat /etc/udev/hal.rules
# Have udev pass data over a socket to hal
RUN+="socket:/org/freedesktop/hal/udev_event"
# unmount block devices when they are removed
SUBSYSTEM=="block",ACTION="remove", RUN+="/usr/lib/hal/hal-unmount.sh"
Could you try to restart the udev daemon (/etc/init.d/udev restart)?
It worked. My bad I suppose: i really didn't think about restarting udev
after HAL upgrade.
Thanks for your help, I suppose the bug can be really closed now.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
