volume.mount_point will not be updated as well. I use the CVS-Version.
This works fine for me; I just committed some changes a while ago, you might want to cvs update. If it still doesn't work please include the output of 'HALD_VERBOSE=1 hald --daemon=no' when you unmount/mount the disc. Either way, let me know.
17:41:21.034 [E] linux/net_class_device.c:227: SIOCGMIIPHY on eth1 failed: Operation not supported17:41:21.127 [E] linux/net_class_device.c:227: SIOCGMIIPHY on eth0 failed: Operation not supported17:41:21.224 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/computer 17:41:21.311 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/pci_1274_5880 17:41:21.388 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/pci_8086_7113 17:41:21.464 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/pci_8086_7112 17:41:21.544 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/usb_usb_device_0_0_206_-1_0000:00:07.2_0 17:41:21.545 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/pci_8086_7111 17:41:21.629 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/ide_host_1 17:41:21.631 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/ide_1_1 17:41:21.719 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/ide_1_0 17:41:21.824 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/ide_host_0 17:41:21.913 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/ide_0_0 17:41:22.067 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/pci_8086_7110 17:41:22.068 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/pci_8086_7191 17:41:22.155 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/pci_121a_5 17:41:22.157 [W] hald_dbus.c:121: No property info.capabilities on device with id /org/freedesktop/Hal/devices/pci_8086_7190 I use /udev for udev. Maybe it's important. The cd/dvd is shown correctly under my drive but it's marked as non-mounted, even if it's mounted. So gnome-volume-manager can't find the mount-point and fail to start my dvd-player :-(. I use the cvs-version. udev and d-bus both are the newest version.
I need more debug information, sorry; it should look like this when mounting the cdrom: 18:22:24.019 [I] linux/block_class_device.c:2188: Directory /etc changed 18:22:24.247 [I] linux/block_class_device.c:2102: /etc/mtab changed, processing all block devices 18:22:24.348 [I] linux/block_class_device.c:1981: /dev/hdd is mounted at /media/dvdrom, major:minor=22:64, fstype=udf, udi=/org/freedesktop/Hal/devices/block_SOLARIS and like this when unmounting it: 18:22:31.878 [I] linux/block_class_device.c:2188: Directory /etc changed 18:22:31.878 [I] linux/block_class_device.c:2102: /etc/mtab changed, processing all block devices Also post (as an attachment please) the output of lshal.
I found the error: if you start hald with "--daemon=no", the mentioned properties are updated correctly and gnome-volume-manager works too. But if you start hald as a daemon, the properties aren't updated.
Good catch, thanks. I've fixed this in CVS but now we daemonize as the very first thing and make the parent exit; I probably need to setup a pipe to make the child tell the parent when probing has completed and exit at that point. David
I've now setup the pipe so the parents exit is deferred until all device probing is done; just like before the fix, but now with the advantage that it actually works. It's in CVS.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.