found 393794 0.5.9.1-2 retitle 393794 no longer automounts firewire, USB and optical disc drives thanks
Confirmed with DVD and USB drives using recent hal on two notebooks, an IBM ThinkPad T42 and T23. Drives appear in syslog and udevmonitor, but then the usual hal actions do not appear in the log (see below). KDE doesn't notice the presence of the new drive. Devices files are there, udevmonitor shows suitable looking events (see below). Hal finds the device as lshal shows it. On disconnecting the USB stick I get in syslog: Aug 9 12:07:19 shambala kernel: usb 1-4: USB disconnect, address 36 Aug 9 12:07:19 shambala udevd-event[12636]: run_program: exec of program '/usr/lib/hal/hal-unmount.sh' failed Well that file does not exist... shambala:~> file /usr/lib/hal/hal-unmount.sh /usr/lib/hal/hal-unmount.sh: ERROR: cannot open `/usr/lib/hal/hal-unmount.sh' (No such file or directory) Seems that this file has been renamed to "hal-storage-unmount". A similar change might have happened to the mount script, with now is called "hal-storage-mount". But just adding symlinks from the old to the new names did not solve the issue that automount does not happen. I was using udev 0.105-4. I thought hal might have introduce a change that my installed udev version was not aware of and just upgraded to udev 0.114-2 on my ThinkPad T42, rebooted and now it works again ;-): So this combination works: shambala:~> apt-show-versions | egrep "(udev|hal|dbus)" | egrep -v "(python|strigi)" dbus/sid uptodate 1.1.1-3 dbus-x11/sid uptodate 1.1.1-3 hal/sid uptodate 0.5.9.1-2 libdbus-1-dev/sid uptodate 1.1.1-3 dbus-1-doc/sid uptodate 1.1.1-3 libdbus-glib-1-2/sid uptodate 0.74-1 udev/sid uptodate 0.114-2 hal-device-manager/sid uptodate 0.5.9.1-2 libhal1/sid uptodate 0.5.9.1-2 hal-info/sid uptodate 20070618-1 libhal-storage1/sid uptodate 0.5.9.1-2 libdbus-qt-1-1c2/sid uptodate 0.62.git.20060814-2 libdbus-1-3/sid uptodate 1.1.1-3 While with udev 0.105-4 it didn't. I also upgraded to udev 0.114-2 on my older ThinkPad T23 and here this also solves the issue. So this combination also works: [EMAIL PROTECTED]:~> apt-show-versions | egrep "(udev|hal|dbus)" | egrep -v "(python|strigi)" dbus/sid uptodate 1.1.1-3 dbus-x11/sid uptodate 1.1.1-3 libdbus-1-2 0.62-4 installed: No available version in archive hal/sid upgradeable from 0.5.8.1-9 to 0.5.9.1-2 libdbus-1-dev/sid uptodate 1.1.1-3 dbus-1-doc/sid upgradeable from 1.0.2-1 to 1.1.1-3 libdbus-glib-1-2/sid uptodate 0.74-1 udev/sid uptodate 0.114-2 hal-device-manager/sid upgradeable from 0.5.8.1-9 to 0.5.9.1-2 libhal1/sid uptodate 0.5.9.1-2 libhal-storage1/sid uptodate 0.5.9.1-2 libdbus-qt-1-1c2/sid uptodate 0.62.git.20060814-2 libdbus-1-3/sid uptodate 1.1.1-3 hal 0.5.8.1-9 is from etch according to apt-cache policy. So it seems its not the newer hal package that introduced the change that broke udev, but maybe libhal or dbus stuff. The package that introduced the change that does not work with udev 0.105-4 IMHO should depend on a newer udev version. I tested with KDE. Just strange is, that I do no get hald log messages in the syslog... I used to get mount and unmount notifications there. Regards -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
signature.asc
Description: This is a digitally signed message part.
