Comment 28 for bug 460328

Why make g-s-d add defaults from console-setup to gconf? Add nothing until user applies something that differs from console-setup settings. Let the layouts gconf key be empty until needed otherwise.

I'm proposing the following g-s-d behavior:
1. setting present in gconf = use it
2. setting is empty in gconf = use corresponding setting from console-setup without writing anything to gconf.
3. user applies setting that differs from console-setup setting = write it to gconf and follow rule #1.

Current wrong behavior in karmic: when gconf layouts key is empty, g-s-d adds "us" layout to it on its startup, despite I have "us,ru" in console-setup. So switching breaks.
fix variants:
1. Add settings correctly.
2. Leave layouts key as it is (empty), use console-setup settings directly
(latter is preferable).

Current wrong behavior in lucid:
When I press "set defaults" in g-k-p, all corresponding gconf-keys are being emptied. But console-setup settings are not being read. I have "us,ru" in console-setup, also "terminate:ctrl_alt_bksp" parameter. But none of this is being reflected in g-k-p.
When gconf layouts key is empty, g-s-d acts as if layouts key is set to "us". When g-s-d is restarted, it adds "us" to gconf key. So switching is broken in two ways.
fix variants:
1. Make "set defaults" button set correct default settings (from console-setup),
2. Make "set defaults" button set empty gconf keys, but correct g-s-d to use console-setup settings _directly_ when there is no override in gconf)
(latter is preferable).