After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 127426 - Nautilus does not cancel file monitoring with fam
Nautilus does not cancel file monitoring with fam
Status: RESOLVED DUPLICATE of bug 94552
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.4.x
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-11-19 21:32 UTC by Jukka-Pekka Partanen
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jukka-Pekka Partanen 2003-11-19 21:32:22 UTC
Distribution: Unknown
Package: nautilus
Severity: normal
Version: GNOME2.4.0 2.4.x
Gnome-Distributor: Gentoo Linux
Synopsis: Nautilus does not cancel file monitoring with fam
Bugzilla-Product: nautilus
Bugzilla-Component: File and Folder Operations
Bugzilla-Version: 2.4.x
Description:
Description of Problem:
Nautilus is set up to use fam for file monitoring. When mounting a
(read&write) file system and acessing files with nautilus the monitoring
stays on after clocing all nautilus windows. This effectively prevents
the unmount of the file system (resource busy...). Killing nautilus
won't help. The only solution is to kill fam. After this the umount
command succeeds.

Steps to reproduce the problem:
1. Mount a file system in rw mode. (Read only fs does not have
this problem)
2. Access the file(s) with nautilus.
3. Close nautilus window and umount the file system. 

Actual Results:
Umount command will fail complaining that resource is busy.

Expected Results:


How often does this happen?
Every time

Additional Information:




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-19 16:32 -------

The original reporter (jukpart@yahoo.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.

Comment 1 Sebastien Bacher 2003-11-20 13:48:58 UTC
Are you using fam in standalone or inetd mode ? If you're using the
inetd one could you try with standalone, fam seems to have some
problems with the inetd mode ...
Comment 2 Sebastien Bacher 2003-11-20 13:51:22 UTC

*** This bug has been marked as a duplicate of 94552 ***
Comment 3 Jukka-Pekka Partanen 2003-11-20 16:58:01 UTC
I am using fam in standalone mode, it is started from init scripts as:
fam -T 0 -c /etc/fam.conf
/etc/fam.conf:
insecure_compatibility = false
untrusted_user = nobody
local_only = true
xtab_verification = true

Distribution that I use is Gentoo 1.4
Comment 4 Jukka-Pekka Partanen 2003-11-21 17:45:13 UTC
There is one difference with bug #94552:
Umount succeeded if the files shown in nautilus window were not
accessed (properties, open etc.) e.g. the device was just mounted,
window opened and then unmounted.
Umount failed only after the files were accessed.
Fam version is 2.6.10.