Bug 589418
| Summary: | Automatic Refresh No Longer Works | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Le Sage <dlesage> |
| Component: | nautilus | Assignee: | Tomáš Bžatek <tbzatek> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | mclasen, tbzatek, tsmetana |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-27 16:07:34 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
David Le Sage
2010-05-06 05:27:36 UTC
Hmm, works here. Possible that you ran out of inotify watches. Are you running some indexer, like tracker ? Yes, I am indeed running tracker and I recently had another issue because it used up the inotify watchers so it is probably the culprit. Will investigate a bit more. Thanks! One more thing to try is the gvfs-monitor-dir command, I'd be interested if it throws an error or not. Hello Tomas, I did a reboot the other day (for other reasons) and paused Tracker at that time and Nautilus is now functioning correctly. I just ran the command as you suggested and it is not reporting any errors. It is just sitting there, even when I run "reload" in Nautilus, etc. Cheers. Actually, Nautilus does still need the refresh, even with Tracker paused, I have discovered from using it throughout today. I basically rebooted my machine on Friday and paused Tracker (through its GUI) as soon as a I logged in so whether it had already consumed the inodes, I do not know. Nautilus definitely needs to be manually reloaded all of the time, though but gvfs-monitor-dir does not report any errors. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |