Bug 78324
| Summary: | nautius monitors the floppy when it doesn't need to | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Bill Bledsoe <billb> |
| Component: | nautilus | Assignee: | Alexander Larsson <alexl> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | feliciano.matias, jeffrey.d.kowing |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-10-04 12:53:22 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Bill Bledsoe
2002-11-21 14:00:55 UTC
The question is what is causing fam to monitor that file. Fam never does anything on itself, only by request from a client. Do you run a desktop on the machine? Does nautilus or konqueror run? I run the default RH 8.0 GNOME desktop. Nautilus runs automatically. Someone suggested nautilus as the culprit in our Linux users group. I tried to use the kill command to kill the nautilus and the system would automatically restart nautilus under a new PID. Nautilus File Browser does not have to be open for the floppy to lock up. I do not open the nautilus when I mount the floppy and it still locks up. If Nautilus opens, I do not change to the floppy directory at all. It stays at the default root directory and still locks up. I do not know how to tell what calls the fam process. If there is a way, let me know and I will run the commands and give you feedback. I hope this helps. Try running "killall -9 nautilus" lots of times repeatedly until nautilus no longer comes up again, and see if fam still monitors the floppy. Yes the "killall -9 nautilus" command after fam has the floppy locked will release the fam and allow the floppy to umount normally. So. Now to figure out why nautilus was monitoring that directory. Did you ever view the floppy in nautilus? Did you ever move something on the floppy to the trash? <Did you ever view the floppy in nautilus?> Answer: No. It locks up even if nautilus is not open. I do not have to view the floppy in nautilus. It locks up with only the "terminal command line window" opened and running. It locks up with only the RH disk manager mounting and umounting the floppy. Interesting enough, once nautilus is killed, both the terminal window and RH disk manager work to mount and umount the floppy. They continue to work until I open the nautilus to the root directory only and then close nautilus. From then on they fail until I use the "kill -9 nautilus" command again. <Did you ever move something on the floppy to the trash?> Answer: No. I have not deleted from the floppy. Do you get a floppy icon on the desktop? <Do you get a floppy icon on the desktop?> Answer: Yes the icon is on the desktop. I never paid attention to it. If I right click the icon and select "Eject" the floppy umounts. The "umount command" does not work from the "RH disk manager" or from the "terminal command line" but the "floppy icon's Eject button" will umount the floppy normally. I guess this means that the icon is the culprit and will not release the floppy without selecting the "EJECT" button. It means that nautilus is monitoring something on the floppy, and when Nautilus is asked to unmount the floppy it knows it has to stop monitoring it first. That doesn't happen when you try to unmount from the command line. I don't understand why it was monitoring the floppy if you've never looked at it with nautilus though. *** Bug 80550 has been marked as a duplicate of this bug. *** I'm having what I believe to be the same problem, except with a USB memory key. I have added my report to a bug already in the gnome nautilus bugzilla that may be of interest. In fact, the behavior seems to be the same, whether for the USB memory key or for a floppy. http://bugzilla.gnome.org/show_bug.cgi?id=115211 I believe this is fixed in fc3 with gnome 2.8 and gamin. Reopen if you see this again. |