Thank you Carl-Eric for your idea of monitoring what apps set gsettings and what do they do exactly. And also to Fred for indicating how to actually do this monitoring. Now my question is: how could we execute a shell with the "dconf watch" command early enough in the boot process so as to have monitoring as soon as possible and where should we place it? Inside the init folder or somewhere else? In other words, how could we trigger early monitoring that would catch the culprit or the possible race condition? Another question I have: is /org/gnome/desktop/wm/keybindings the only key that ultimately indicates the keybinding settings?
-- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1063617 Title: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1063617/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
