gnome shortcuts not restored with session

This is most likely an issues only people using older versions of karmic will have at this point. Can you provide the output of `gconftool -g /apps/compiz/general/allscreens/options/active_plugins`? And, if you see gconf in that list, can you open up gconf-editor and remove it from the list and see if this continues to happen? After you remove gconf you'll have to restart compiz to get it saving things correctly again.

i've updated to latest version of Karmic by executing
# sudo aptitude update
# sudo aptitude safe-upgrade
--------
# gconftool -g /apps/compiz/general/allscreens/options/active_plugins

[core,gconf,move,resize,place,decoration,animation,ccp,dbus,mousepoll,gnomecompat,png,svg,imgjpeg,text,neg,video,wall,snap,scale,scaleaddon,expo,staticswitcher,regex,resizeinfo,workarounds,ezoom,vpswitch,extrawm,fade,session]

trying to remove "gconf" was unsuccessful. i tried it as you describe with gconf-editor, but after removing it from "edit key" dialog and pressing OK it appears aggain, automatically. maybe something is checking its presence.

is there any way how to edit it in console? so i can stop gdm and try to remove it without compiz started?

You can't remove it because compiz was told to use it on the command line so refuses to unload it. Please give the output of `CM_DRY=yes gnome-wm`. Also, please attach your /etc/xdg/compiz/compiz-manager and (if it exists) ~/.config/compiz/compiz-manager files.

$ CM_DRY=yes gnome-wm
prints out something in czech, i append translations signed "#". it's interesting that it mentions move_to_workspace... once i misslook when setting my favourite "switch_to_workspace" shortcut and edited "move_to_workspace", when i finded out i tried to put theese "moving" shortcuts to default (or mabye to none, i don't remember exactly)

Varování správce oken: "" nalezené v databázi nastavení není platnou hodnotou klávesové zkratky "move_to_workspace_1"
Varování správce oken: "" nalezené v databázi nastavení není platnou hodnotou klávesové zkratky "move_to_workspace_2"
Varování správce oken: "" nalezené v databázi nastavení není platnou hodnotou klávesové zkratky "move_to_workspace_3"
Varování správce oken: "" nalezené v databázi nastavení není platnou hodnotou klávesové zkratky "move_to_workspace_4"
#window manager warning: "" found in settings database is not valid value of a shortcut "move_to_workspace_X"
Varování správce oken: Obrazovka 0 na displeji ":0.0" již správce oken má; zkuste prosím nahradit aktuálního správce oken pomocí přepínače --replace.
#window manager warning: screen 0 on display ":0.0" has already window manager; please try to replace current window manager using --replace switch

$ cat /etc/xdg/compiz/compiz-manager
# Ubuntu specifc compiz-manager configuration file
# goes into /etc/xdg/compiz/compiz-manager
# works with git://anongit.compiz-fusion.org/fusion/misc/compiz-manager
COMPIZ_BIN_PATH="/usr/bin/"
PLUGIN_PATH="/usr/lib/compiz/"
COMPIZ_NAME="compiz.real"

file ~/.config/compiz/compiz-manager i don't have

Alright, just go to System->Preferences->Appearance and change Visual Effects to None then remove gconf from that list and change Visual Effects back to what it was before.

gconf successfully removed with effect disabled and didn't appear again when efects enabled. so i set the shortcuts and rebooted, shortcuts doesn't work and gconf is again loaded... maybe i missed something around restarting compiz. how did you mean it? i shouldn't reboot?

Now I have no idea what is going on, gnome-wm was patched to not load compiz with the gconf plugin and the only other thing that would make it load is custom modifications to the startup scripts which you don't seem to have. I guess we'll just have to remove the gconf plugin from the packages to clear this up 100%.

This should be fixed in the compiz packaging bzr repo. It will be in the next upload of compiz to karmic.

thank you, i'll confirm it if it would work

Travis,

I reviewed the compiz upload in unapproved. http://paste.ubuntu.com/294452/ is the effective diff

The code changes aren't exactly "small", but only affect bug fixes. How much was this package tested, and on how much hardware? Any regression potential there?

However, dropping the gconf backend seems like a very intrusive change now. Wouldn't that entirely ignore settings which users have made through gconf? How does this affect shared settings with metacity, such as keybindings or window focus behaviour?

The changes have all been written by one developer, reviewed by another, and tested by at least 3 people using intel and nvidia hardware. And, as you said, each change is meant to fix a known bug, it's not cleanup or feature work.

As for the gconf plugin, we haven't actually used this in Ubuntu since before hardy. We use the ccp plugin (libcompizconfig) which is what actually does the metacity integration. Anyone who has actually been editing /usr/bin/compiz to switch from ccp to gconf will be forced to use ccp at this point but it is a smooth transition as it uses all the same gconf keys anyway.

Travis, thanks for the heads-up. I don't think we need to be concerned about /usr/bin/compiz modifications (since they get overwritten by package upgrades anyway), but I was concerned about settings migration. By "we haven't actually used this in Ubuntu" does that mean "by default, and users could switch to it", or "it never worked at all"?

<pitti> Amaranth: is there a chance that some users actually use the gconf backend?
<Amaranth> pitti: the only way to use the gconf plugin has been to edit /usr/bin/compiz
<Amaranth> pitti: and none of the settings tools work when the gconf plugin is being used (they end up switching you back to the ccp plugin)
<pitti> Amaranth: so why exactly was it removed now?
<Amaranth> pitti: Because in the past if a user tried to load it (`compiz --replace gconf`) it would basically just ignore that because the ccp plugin was already being loaded. Now compiz loads all plugins specified on the command line and makes it impossible to unload them
<Amaranth> pitti: So now the gconf plugin is actively interfering with the ccp plugin and causing the issue mentioned in that bug report

OK, thanks. Ack'ed.

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

---------------
compiz (1:0.8.4-0ubuntu1) karmic; urgency=low

  * new upstream release: (LP: #451773)
    - cannot resize window taller than screen (LP: #221698)
    - moving a "always on visible workspace" window to another workspace
      makes it inaccessible (LP: #290079)
    - enabling "always on visible workspace" for window on another
      workspace does not bring to current workspace (LP: #372626)
    - screenshot plugin gets confused by screenshot02.png.sig file (LP: #382969)
    - window moves when closed (LP: #444836)
    - translation updates
  * debian/compiz-gnome.install:
    - don't install the gconf plugin at all, it just causes problems with
      the ccp plugin (LP: #439287)
  * debian/watch:
    - updated for new release website

 -- Travis Watkins <email address hidden> Wed, 14 Oct 2009 14:55:25 -0500

The only way to use the gconf plugin is to edit /usr/bin/compiz. The configuration tools don't work with the gconf plugin either (at least ccsm and simple-ccsm, I believe gnome-appearance-properties as well) so in that sense it has been broken as well.

i confirm, that it's working now, thank you all