Comment 4 for bug 1235782

From a user perspective the commands plugin could be described as 'fragile'. I've found in compiz 0.9.x that user set commands have have a lifetime of several days or so during which they just disappear & need to be reset over & over again.

However an integrated command seems to be very solid & persistent once set which seemed to be the issue here.
( for myself took the change as an opportunity to integrate a command I do want without much work & it has been fine ever since, both for orig. user & any add. users.

So to test current state booted to todays image -
In live session on ubuntu user sys mon was opened from binding
Set up a new user, logged in, sys mon was opened ^

Installed 13.10 from the image, rebooted & when logged in sys mon was opened from the intended binding.

So atm all seems well, what was happening before on new installs doesn't seem to be anymore
(the command & binding where set but not active for the orig. user of that new install

I've no doubt that if your colleague either did a new install or unset & reset the binding back to the default in dconf it would work as Design intends & remain working.

What could happen to upgraders with the current setup I've no clear idea, one would have to try..