Comment 20 for bug 102097

Some update

Yesterday I upgraded one of my feisty boxen to gutsy (as usb automount doesn't work on either I may as well have the newer version to see what is going on and gutsy is due soon) upon installation / upgrade yesterday I was able to mount my drive with 'pmount-hal sdb1' and read from it.

I noticed that in todays update there were some hal related packages so I decided to try my drive again, firstly no automagic but secondly (and perhaps more seriously) I now get an error when issuing the pmount command.

:~$ fdisk -l

Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x170a8ae2

   Device Boot Start End Blocks Id System
/dev/sdb1 * 1 38913 312568641 c W95 FAT32 (LBA)

:~$ pmount-hal sdb1
process 5387: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
This is normally a bug in some application using the D-Bus library.
libhal.c 1122 : Couldn't allocate D-BUS message
process 5387: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
This is normally a bug in some application using the D-Bus library.
libhal.c 1122 : Couldn't allocate D-BUS message
Error: given UDI is not a mountable volume

Child