1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values

After restarting compiz/unity again, it works now. Lots of other things are broken (Ctrl+Alt+T, Windows+Up/Down, etc.), but at least this unnerving thing seems to have been an one-time issue.

It's back. It seems compiz randomly applies this or not on startup, depending on the moon phase or other unobvious circumstances.

After this morning's login, it's back. It set

  org.gnome.desktop.wm.preferences auto-raise true

to true again, although I never set that. Yesterday I "reset" the key, so that it was definitively not in my ~/.config/dconf/.

It also set the maximize/unmaximize keys back from my custom Super+Up/Down to the default:

org.gnome.desktop.wm.keybindings maximize ['<Control><Primary><Super>Up']
org.gnome.desktop.wm.keybindings unmaximize ['<Control><Primary><Super>Down']

I checked in dconf-editor, the keys are set in ~/.config/dconf, they did not get reset to the default.

Finally it keeps deleting my keybinding for

  org.gnome.desktop.wm.keybindings lower ['disabled']

when I set it back to Alt+B (for the umpteenth time) in control, center, this is how it should be:

  org.gnome.desktop.wm.keybindings lower ['<Alt>b']

Please note that the schema default is [], not ['disabled'], so once again it invents this "disabled" value or gets it from another migration source.

Where are these values copied or generated from at startup? I might have some other settings somewhere which did not affect compiz versions prior to 1:0.9.8+bzr3319-0ubuntu1, but now keep messing up my settings.

For the record, now I have the original problem again, I was not halucinating:

$ gsettings get org.gnome.desktop.wm.preferences auto-raise
false

but still compiz is auto-raising windows again. I don't know how to stop it from doing that..

Unsure if what I'm seeing is the same as pitti or not; but sounds similar.
manually unset "click to focus" via compizsettings/general/focus
click the back button
go forward to the focus page; and 'click to focus' is checked again.

Can't seem to convince things that I really want focus-follows-mouse.

quantal beta.

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

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

  * debian/control:
    - Add dependency on gnome-settings-daemon for compiz-gnome, since some
      tests need the g-s-d gsetting schemas
  * New upstream release.
    - FTBFS with -DCOMPIZ_BUILD_TESTING=OFF if libgtest-dev is not installed
      (LP: #1057421)
    - [performance] glXSwapIntervalEXT called every frame, which is very slow
      on Nvidia. (LP: #1051286)
    - opacify plugin: opacity isn't reset after switching window (LP: #1050757)
    - cmake fails on python 2.6 as sys.version_info does not contain
      major_version or minor_version (LP: #1048964)
    - scale mode is not visible if a fullscreen window is unredirected
      (LP: #1047168)
    - Unredirected fullscreen windows flicker briefly when another window
      (like a menu) opens above them (LP: #1046664)
    - Week33 - Grid highlight window appears while switching between workspaces
      (LP: #1037142)
    - gtk-window-decorator leaks large numbers of pixmaps and pixmap memory
      (LP: #1057263)
    - [fglrx] compiz crashed with SIGSEGV in glXDestroyContext()
      [/usr/lib/fglrx/libGL.so.1] from GLScreen::~GLScreen() (LP: #1054724)
    - Maximized window gets unredirected when it's not fullscreen
      (LP: #1053902)
    - Double shortcuts conflict with gnome-control-center ones (LP: #1050796)
    - gtk-window-decorator leaking window handles. Window operations become
      sluggish after a few days of usage (LP: #1050610)
    - [valgrind] Up to 520,000 bytes lost when running
      CCSGSettingsBackendConceptTest (LP: #1049169)
    - 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
      wrong values (LP: #1042041)
    - Compiz r3275 breaks VirtualBox Guest Additions: black screen or just
      wallpaper (LP: #1030891)
    - Incorrect (low/stuttering) refresh rate with NVIDIA driver (LP: #92599)
    - ARM build broken with 'swapInterval' is not a member of 'GL'
      (LP: #1056645)
    - compiz.fix_927168 broke ARM building (LP: #1052838)
    - compiz crashed with SIGSEGV in __strcasestr_ia32() from
      ccsStringToModifiers(binding=NULL) (LP: #1041535)
  * Cherry-picked from upstream:
    - ABI bump due to an ABI change in the composite plugin
    - Removed schema keys still used in keybindings and automated tests
      (LP: #1057955)
 -- Lukasz 'sil2100' Zemczak <email address hidden> Thu, 27 Sep 2012 15:43:59 +0200

This is still an issue, reported as bug 1063617.

I have the same problem, this bug is not fixed.

This bug is Fix Released. Please post new comments in the new bug; bug 1063617.