Gamin doesn't let me to umount my pen disk. It is necessary to kill it
&& umount the device
The version I tried is:
Connect the pen disk and try to umount it
It's impossible to umount.
I can confirm this behavior with 0.0.24 - this makes it very difficult
to work with removable storage so I'm raising the severity to high.
Also fixing version to devel.
Created attachment 111527 [details]
This patch disables gam_server actions on banned paths. Works foe me.
It not a perfect solution -- in disables gam_server at all
for paths, markes as excludes (not using [di]notify, not pool).
It may be acceptable for removable drives
Patch is just wrong, it's a terrible regression, sorry I really
can't use this. I'm still chasing the real problem.
Fix should be in release 0.0.25 of gamin available at
It's pushed to rawhide
It looks to me that gamin-0.1.0-1.1 breaks this yet again (jrb experienced this
yesterday and I've just reproduced this) so I'm reopening this bug. It's also
really bad that this is the version in FC4, it really needs to be fixed so I'm
changing the priority to high.
DV, can you confirm the problem on your end?
No. I don't have FC-4, but on RHEL-4 with the exact same version of gamin
recompiled locally and nautilus-2.8.1-4, plugging my USB drive with pictures
it shows up on the desktop automatically, I can browse the images, and then
if I right click on the drive icon, select umount, it does umount, the window
and icons disapears and df shows the volume has been unmounted.
Either the paths where the device it has been mounted to have changed in FC-4
but /media/ is forbidden by default from being watched with dnotify. And this
kind of checks is part of gamin regression tests nowadays.
I doubt it's really gamin regression, something else changed. The mount point
I'm seeing here is /media/UDISK_2_0, and lsof /media/UDISK_2_0 with
nautilus window open over the images on the drive shows no open descriptors
I think I can say I can't reproduce it at this point. Need more informations !
Just tried with downgrading to gamin-0.0.26-1 on Rawhide and that made things
work. So, this means the bug is indeed with gamin-0.1.0-1.1. Also, note the bug
here is that /usr/libexec/gnome-vfs-daemon doesn't catch the change in /etc/mtab
that occurs when gnome-volume-manager is invoking mount(1) (and mount(1) updates
the /etc/mtab file). Of course, there is the possibility that this is a bug with
gnome-vfs but since it works with gamin-0.0.26-1 (and fam before the gamin era)
I doubt it.
Please fix this soon, it's a very serious end-user bug.
So is that reproduced on Rawhide or FC-4 ?
I don't see how catching or not catching a change in /etc/mtab makes a
file system not unmountable, at least from a gamin perspective.
Can you explain *precisely* the sequence of event you did to reproduce
the problem ? Could you also tell me the mount path used for the device
and the lsof output for that device ?
Sorry for hijacking this bug, my mistake, I've filed the issue detailed in
comment 7 in bug 159748. Closing this bug as RAWHIDE since the issue in this
report have been solved.