Comment 8 for bug 162480

Funny zip behavior(on a old gutsy7.10 distro,and yes still using it)

Something similar happened to my zip when tried to eject.
Im my case it would not even eject.
Complained about a application using the drive.
Some command output.

ubuntu:~$ gnome-umount -vbd /dev/hdb4
gnome-mount 0.6
** (gnome-umount:32082): DEBUG: Will attempts methods on drive object
** (gnome-umount:32082): DEBUG: Unmounting /org/freedesktop/Hal/devices/storage_model_IOMEGA_ZIP_100_ATAPI
** (gnome-umount:32082): DEBUG: Setting up 750ms timer for Flushing Cache dialog
** (gnome-umount:32082): DEBUG: in unmount_done : user_data = 0x0

** (gnome-umount:32082): WARNING **: Unmount failed for /org/freedesktop/Hal/devices/storage_model_IOMEGA_ZIP_100_ATAPI: org.freedesktop.Hal.Device.Volume.Busy : umount: /media/disk: device is busy

ubuntu:~$ sudo umount -v /dev/hdb4
umount: /media/disk: device is busy
umount: /media/disk: device is busy
---------
Well nothing odd with that if you are using the disk.
But by some reason it was nautilus that hanged on to the drive,,(filelock)?
Not until i killed of the "unseen" nautilus process the behavior disappeared.

ps ax ouput
8134 ? S 0:05 nautilus --no-default-window --sm-client-id default2

I think the --sm-client-id was default4 thou before the kill?
However it seems to work as supposed now.
Fault persisted even if rebooted whole computer.
Version of Nautilus 2.20.0
----