Description of problem:

With a setup updated to the the current rawhide level pluggina a USB
floppy with a read-only floppy inside results in a floppy beeing mounted
on /media/floppy1.  So far so good (disregarding that currently hal and
nautilus do not seem to talk to each other and that floppy does not show
up on a desktop and is also not nautilus-browsable).

But if now I will pull a usb plug (yes, I know that I should not do that
but users not always listen to such reminders) then I see in 'dmesg'

usb 5-1: USB disconnect, address 3

but no reaction from hal and that floppy remains mounted.

If, in an apparent attempt to rectify the mistake, I will replug that floppy
again then 'mount' now shows

....
/dev/sdb on /media/floppy1 type vfat (ro,nosuid,nodev,_netdev)
/dev/sdc on /media/floppy2 type vfat (ro,nosuid,nodev,_netdev)

and two corresponding entries in /etc/fstab even if /dev/sdb at this
moment is actually gone.  Moreover neither 'umount /media/floppy1' nor
'umount /dev/sdc' rewrites /etc/fstab.  Unplugging a usb enclosure with
unmounted /dev/sdc removes its entry in /etc/fstab but the one for /dev/sdb
is there (although it will be "recycled" if one will re-plug that USB floppy
now, i.e with both /media/floppy{1,2} unmounted).

I do not have a USB memory stick right now but I suspect that reactions will
be similar.

Version-Release number of selected component (if applicable):
hal-0.5.4-3