User-Agent: Mozilla/5.0 (X11; U; Linux i686; en; rv:1.8.1.1) Gecko/20061223 Epiphany/2.16 Build Identifier: When I insert a DVD or CD and try to mount it in thunar, the first time I try, I always get this error and thunar does lock the drive, but the disc is not fully mounted: Failed to mount "New DVD". Failed to determine the mount point for /dev/sr0. When I click on the disc icon again, it works. Reproducible: Always Steps to Reproduce: 1.Insert a disc 2.Click the disc icon in thunar's side pane Actual Results: error message is shown, selected folder stays. Expected Results: mount the disc and open it to show the content hal 0.5.8.1-3 dbus 0.93-1 pmount 0.9.13-2 arch linux. when i pmount the disc manually after inserting it, then the content is shown in thunar the immediately when i click the disc icon without showing the error. I read about a similar bug in the mailing list some time ago, but this still happens with the latest svn version here.
Should be fixed with revision 24277. 2007-01-06 Benedikt Meurer <benny@xfce.org> * thunar-vfs/thunar-vfs-volume-freebsd.c, docs/README.volumes, thunar-vfs/thunar-vfs-volume-hal.c: Use exo-mount to mount, eject and unmount volumes instead of relying on external utilities that don't always behave properly. Bug #2715.
ejecting a disc with exo-mount does not work, thunar still looks for the "eject" program. is this correct like this? from the changelog i thought "eject" wouldn't be needed anymore. i also removed pmount and tried the reported stuff (insert dvd, click the icon) with thunar and exo-mount only (both exo and thunar are updated to latest svn after your changes) and i still get the same error dialog about failed to determine the mount point.
btw, the disc is still mounted the 2nd time i click the disc icon. i tried mounting the disc with exo-mount and ejecting it with exo-eject in a terminal, and i get those errors: $ exo-mount /dev/sr0 exo-mount: Must specify HAL device UDI or device file. $ exo-eject /dev/sr0 exo-eject: Must specify HAL device UDI or device file.
HAL refuses to handle volumes listed in /etc/fstab. So if you have such volumes, you'll still need to have eject around. To use exo-eject, you must either specify a HAL UDI with -h or a device file with -d, i.e. exo-eject -d /dev/sr0.
you're right, i had added the device in the fstab lately. dunno exactly why, but i removed it again. now when i try to mount or eject the disc, i get this error: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.Hal.Device.Volume" member "Eject" error name "(unset)" destination "org.freedesktop.Hal"). when i add them to the fstab, it works, except exo-eject complains about "eject" missing, when i don't have it installed. just to be sure: with the new exo-mount stuff, i don't need pmount and eject anymore when i use hal, right?
You don't need pmount, but you still need eject for volumes in /etc/fstab. The error message tells you that you are not allowed to use the D-Bus methods on the Volume interface. You need to the tell D-Bus system message bus to allow these methods. I.e. to allow for group users, add a file hal-local.conf to your dbus-1/system.d/ directory and restart the system message bus (and hald): ---< hal-local.conf >--- <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd"> <busconfig> <!-- Every user may use HAL --> <policy group="users"> <allow send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/> <allow send_interface="org.freedesktop.Hal.Device.Volume"/> <allow send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/> </policy> </busconfig> ------------------------ This way you can also shutdown your computer using HAL (the SystemPowerManagement interface, as used by xfce4-session).
ah ok, thanks for pointing there. arch linux has groups for shutdown/restart (group power) and for volume and volume.crypto (storage), so after adding the user to storage, and reinstalling eject, it works fine now. (the user was added to power already, so shutdown worked fine before :)) i had a situation just now where i clicked on the disc and nothing happened and i couldn't eject the disc because it wasn't mounted according to hal mtab or sth like that, but i could eject it from a terminal and i couldn't reproduce it anymore, so i guess it wasn't really a bug. one last question though: you said i need eject for devices in my fstab. but i commented out any cd and dvd devices in my fstab and i still need it to eject the disc. so what is this exo-eject about? is it just using eject or can it eject discs on its own when the device is not listed in the fstab? if this is the case, then it's not working correctly. else it's working fine now without pmount. thanks for your help!
exo-eject invokes eject directly for volumes listed in /etc/fstab. If a volume is not listed in /etc/fstab, it invokes the Eject method on HAL's Volume interface. I'm not sure how the Eject method is implemented for Linux, maybe HAL also uses eject at some point. So, don't uninstall eject (it doesn't take up that match disk space anyway)! ;-)