[gsettings] Lots of warnings about key names >31 characters, which also causes CCSM crashes.

Bug Description

Using the gsettings backend for compizconfig I get far too many warnings. Either this situation needs to be fixed in the schemas, or the warning message hidden by default. It's making compiz and ccsm very hard to work with when all I see is this same warning.

GSettings Backend: Warning: key name maximize-window-horizontally-key is not valid in GSettings, it was changed to maximize-window-horizontally-ke, this may cause problems!
GSettings Backend: Warning: key name toggle-window-maximized-horizontally-key is not valid in GSettings, it was changed to toggle-window-maximized-horizon, this may cause problems!
GSettings Backend: Warning: key name toggle-window-maximized-vertically-key is not valid in GSettings, it was changed to toggle-window-maximized-vertica, this may cause problems!
GSettings Backend: Warning: key name horizontal-folds-zoom-to-taskbar is not valid in GSettings, it was changed to horizontal-folds-zoom-to-taskba, this may cause problems!
GSettings Backend: Warning: key name magic-lamp-wavy-open-start-width is not valid in GSettings, it was changed to magic-lamp-wavy-open-start-widt, this may cause problems!
GSettings Backend: Warning: key name background-gradient-highlight-color is not valid in GSettings, it was changed to background-gradient-highlight-c, this may cause problems!
GSettings Backend: Warning: key name background-gradient-shadow-color is not valid in GSettings, it was changed to background-gradient-shadow-colo, this may cause problems!
GSettings Backend: Warning: key name thumb-highlight-gradient-base-color is not valid in GSettings, it was changed to thumb-highlight-gradient-base-c, this may cause problems!

On 2012年6月28日, Daniel van Vugt wrote:

> ** Changed in: compiz

I think we need to check with desrt to see if this limitation still
exists - I remember there was talk about lifting it.
> Assignee: (unassigned) => Daniel van Vugt (vanvugt)
>
> --
> You received this bug notification because you are a member of Compiz
> Maintainers, which is subscribed to Compiz.
> https://bugs.launchpad.net/bugs/1018730
>
> Title:
> [gsettings] Lots of warnings about key names >31 characters
>
> Status in Compiz:
> Triaged
>
> Bug description:
> Using the gsettings backend for compizconfig I get far too many
> warnings. Either this situation needs to be fixed in the schemas, or
> the warning message hidden by default. It's making compiz and ccsm
> very hard to work with when all I see is this same warning.
>
> GSettings Backend: Warning: key name maximize-window-horizontally-key is not valid in GSettings, it was changed to maximize-window-horizontally-ke, this may cause problems!
> GSettings Backend: Warning: key name toggle-window-maximized-horizontally-key is not valid in GSettings, it was changed to toggle-window-maximized-horizon, this may cause problems!
> GSettings Backend: Warning: key name toggle-window-maximized-vertically-key is not valid in GSettings, it was changed to toggle-window-maximized-vertica, this may cause problems!
> GSettings Backend: Warning: key name horizontal-folds-zoom-to-taskbar is not valid in GSettings, it was changed to horizontal-folds-zoom-to-taskba, this may cause problems!
> GSettings Backend: Warning: key name magic-lamp-wavy-open-start-width is not valid in GSettings, it was changed to magic-lamp-wavy-open-start-widt, this may cause problems!
> GSettings Backend: Warning: key name background-gradient-highlight-color is not valid in GSettings, it was changed to background-gradient-highlight-c, this may cause problems!
> GSettings Backend: Warning: key name background-gradient-shadow-color is not valid in GSettings, it was changed to background-gradient-shadow-colo, this may cause problems!
> GSettings Backend: Warning: key name thumb-highlight-gradient-base-color is not valid in GSettings, it was changed to thumb-highlight-gradient-base-c, this may cause problems!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/compiz/+bug/1018730/+subscriptions
>

I can't yet find any evidence the limitation exists.

the limitation was dropping that commit:
http://git.gnome.org/browse/glib/commit/?id=fe6dad271b06e6243d17137c2e0991f56a256cca

"GSettings: remove key length restrictions
The key length now stands effectively unlimited at 1024 characters.
https://bugzilla.gnome.org/show_bug.cgi?id=654536 "

"the limitation was dropped in that commit" rather

Raised to high, because without this fix compiz will install invalid schemas (truncated key names) and CCSM will crash trying to access them.

Fix committed into lp:compiz at revision 3263

This bug was fixed in the package compiz - 1:0.9.8.0-0ubuntu1

---------------
compiz (1:0.9.8.0-0ubuntu1) quantal-proposed; urgency=low

* debian/control, debian/rules:
- enable gles on armel and armhf
- use dh-translations rather than custom code

[ Sam Spilsbury ]
* Enable OpenGL ES building
- Refresh debian/patches/workaround_broken_drivers.patch
- Remove non-ported plugins from compiz-plugins
- Add FindOpenGLES2.cmake to compiz-dev

[ Timo Jyrinki ]
* New upstream release.
- Code to make compiz work on GLES. This includes several changes
to the compiz API. (LP: #201342) (LP: #901097) (LP: #1004251)
(LP: #1037710)
- Draft first 0.9.8.0 NEWS and bump VERSION
* debian/patches/compiz-package-gles2.patch:
- Remove, obsoleted by the upstream GLES work
* Disable plugins that don't work on pure GLES on armhf/armel:
- bench, firepaint, mblur, showmouse, splash, showrepaint, td, widget
-- Sebastien Bacher <email address hidden> 2012年8月31日 22:59:50 +0200