Bug 454576 - NetworkManager causes gconf to write too frequently
NetworkManager causes gconf to write too frequently
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
Blocks: F10Target 454582
  Show dependency treegraph
Reported: 2008-07-08 22:55 EDT by Jesse Keating
Modified: 2013-01-09 22:21 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-20 19:22:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jesse Keating 2008-07-08 22:55:47 EDT
Every minute or so gconf-d starts writing to various xml files (no changes
though it seems).  Files like:


things like that.  These constant writes are preventing the disk from sleeping
and saving power.  Please to be fixing.
Comment 1 Dan Williams 2008-07-09 12:09:55 EDT
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).
Comment 2 Jesse Keating 2008-07-09 12:25:54 EDT
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?
Comment 3 Eric Sandeen 2008-07-10 00:16:07 EDT
I think even a 5 minute update isn't going to make disk spindown very possible,
Comment 4 John Poelstra 2008-10-20 18:53:03 EDT
Is this problem still happening and if so what package names and versions are involved?
Comment 5 Jesse Keating 2008-10-20 19:22:37 EDT
This does not seem to be happening any more, not at the frequency it was before.

Note You need to log in before you can comment on or make changes to this bug.