When I insert a CF into my laptop it doesn't get mounted by g-v-m. I filed a bug on b.g.o against g-v-m but fejj thinks (and I think too) that this is a hal bug because it is returning /dev/hde instead of /dev/hde1 as mount point. All the debugging foo is attached to http://bugzilla.gnome.org/show_bug.cgi?id=314633 See that for details. If you need any more info I'll am happy to help. Thanks
I have the same problem with my USB card reader. The devices show up in the GTK+ file selector but when clicked it tries to mount /dev/sdb, /dev/sdc, /dev/sdd and /dev/sde instead of /dev/sdb1, /dev/sdc1, /dev/sdd1 and /dev/sde1. gnome-volume-manager is also unable to automount anything now. I'm running HAL 0.5.4, dbus 0.50, udev-068 and GNOME 2.12.0 on Kernel 2.6.11, everything built from sources. Earlier versions did work.
Btw this bug is fix for me on my box with lastest breezy updates. Not sure if it was due to a hal or udev update or if they vendor patch it.
Note: this is a comment related to the gnome bug. This is IMO not a HAL bug. The property block.device = '/dev/hde' is correct. Take a look at the spec of HAL. If you want to mount, you should wait for a volume. What you have in the case above is the storage device self and not a volume. This is the same behavior as for harddisk, where you also not try to mount e.g. /dev/hda HAL maybe does not create a volume for the CF-card in the device list, but this is then an other bug.
Yep, this is not a HAL bug.
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.