Bug 454576
Summary: | NetworkManager causes gconf to write too frequently | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jesse Keating <jkeating> |
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | dcantrell, dcbw, esandeen, poelstra, wtogami |
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: | 2008-10-20 23:22:37 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: | |||
Bug Depends On: | |||
Bug Blocks: | 438944, 454582 |
Description
Jesse Keating
2008-07-09 02:55:47 UTC
Hmm; it may be the connection timestamp updates, but those are only scheduled every 5 minutes. Also, if NM roams to a new AP, that will trigger an update of GConf to store the new BSSID. That could happen at any time, but shouldn't write anything out if nothing has changed (ie if the BSSID was already stored). I agree that it shouldn't (: But it is, and I'm sitting on my couch, not roaming around or anything. Anything I can do to help debug why it thinks it should write? I think even a 5 minute update isn't going to make disk spindown very possible, FWIW... Is this problem still happening and if so what package names and versions are involved? This does not seem to be happening any more, not at the frequency it was before. |