|Summary:||gsettings seem to generate multiple entries|
|Product:||[Fedora] Fedora||Reporter:||Ali Akcaagac <aliakc>|
|Component:||gsettings-desktop-schemas||Assignee:||Matthias Clasen <mclasen>|
|Status:||CLOSED EOL||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||20||CC:||debarshir, fmuellner, mclasen|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2015-06-29 15:05:26 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Ali Akcaagac 2014-02-08 21:31:30 UTC
Dunno if this matters but whenever I run: gsettings list-recursively | sort I receive n+1 entries in my output. This is not valid for all programs using dconf as backend but plenty of the apps show double and more equal entries. Example: net.sf.liferea.plugins active-plugins ['gnome-keyring', 'media-player'] net.sf.liferea.plugins active-plugins ['gnome-keyring', 'media-player'] org.freedesktop.ibus.general dconf-preserve-name-prefixes ['/desktop/ibus/engine/pinyin', '/desktop/ibus/engine/bopomofo', '/desktop/ibus/ org.freedesktop.ibus.general dconf-preserve-name-prefixes ['/desktop/ibus/engine/pinyin', '/desktop/ibus/engine/bopomofo', '/desktop/ibus/ org.freedesktop.ibus.general embed-preedit-text true org.freedesktop.ibus.general embed-preedit-text true org.freedesktop.ibus.general enable-by-default false org.freedesktop.ibus.general enable-by-default false org.freedesktop.ibus.general engines-order @as  org.freedesktop.ibus.general engines-order @as  org.freedesktop.ibus.general.hotkey disable-unconditional @as  org.freedesktop.ibus.general.hotkey disable-unconditional @as  org.freedesktop.ibus.general.hotkey disable-unconditional @as  org.freedesktop.ibus.general.hotkey enable-unconditional @as  org.freedesktop.ibus.general.hotkey enable-unconditional @as  org.freedesktop.ibus.general.hotkey enable-unconditional @as  evolution gnome-shell shotwell etc. Even with a brand new user account this happens. So either gsettings recursion is broken, schemas have double or tripple and more entries or some other nasty thing is going on.
Comment 1 Ali Akcaagac 2014-02-11 16:30:43 UTC
I checked it up with a brand new account and removed "dconf" file in .config/dconf when doing a recurisve list the same problem appears. "dconf dump /" seem to operate normaly.
Comment 2 Fedora End Of Life 2015-05-29 10:51:24 UTC
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Comment 3 Fedora End Of Life 2015-06-29 15:05:26 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.