The key values set and read by gconf-editor are correct. However, Gnome ignores these settings.
So, either gconf-editor is not handling it properly, or another application is overriding the settings of the gconf-editor (or gnome for that matter). Of course I don't know how Ubuntu handles this internally, but the place where I noticed the bug was when using gconf-editor. I'm not claiming it should be a bug there. For all I know it is related to other software, but I was hoping that this is where your expertise comes in. Whichever it is, the settings gconf-editor stores are (partly) not read/followed up by the system. That is the actual bug. Unfortunately my in dept knowledge of the Gnome desktop is not such that I would know which software (layers) deal with these settings. If I would have had any hints, I would have let you know. So it is not necessarily a bug in the editor itself. It is the place where I (and others) have noticed it though. Technically speaking it could be that the editor saves the settings on a server on the net somewhere and reads them fine, but Gnome never sees them. It could be that there are more than just one file with these kind of settings: one not being read by Gnome and one being read by Gnome, of which the editor edits the wrong one. And I can go on and on for a while like this. Anyway, I don't know where the actual bug lies, all I can do at this point is report what I noticed and which indicates a malfunction. I was hoping you would be able to find the actual bug with this information. Again, let me know if I can help with additional information. -- Hardy: gconf-editor changed settings ignored by system https://bugs.launchpad.net/bugs/203877 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
