Version: svn from 12-14-2007 (using KDE Devel) Installed from: Compiled sources Compiler: gcc (GCC) 4.1.2 20061115 (prerelease) (SUSE Linux) I've compiled kde4 from sources, deleted the old ~/.kde4/ directory, started kde4, opened a window and enabled compositing and some effects, "mouse marks" and "present windows" between them. After playing with the mouse marks effect, the effects stopped being available through keyboard shortcuts: mouse marks were not erased on meta-shift-f11, ctrl-f10 did not present the windows (however, it is still available via mouse, going to top left corner toggles the effect). When the settings dialog of the respective effect is open, the shortcut works (but only the shortcut of the effect whose setting dialog is open, not of any other). Strange behaviour, the bugzilla found only bug 153915 for me, which is closed, but may be the same problem. I'll try to perform some more experiments to find the exact way to reproduce this behaviour.
OK, here's how it is reproducible for me: - start kde4 session - try some mouse marks, erase them with meta-shift-f11 - go to mouse marks settings dialog, cancel the dialog, cancel the configure window behaviour dialog - paint some mouse marks - try meta-shift-f11 and voila, it is not erased the other desktop effect (presence, grid) shortcuts work after these steps. To break the presence shortcut, repeat the previous steps with the presence settings dialog. After that, break the grid effect with the same algorithm, etc.
I can confirm that this issue is still present in the subversion revision 748761.
I just noticed a similar bug with the zoom effect (kde 4.0.2) : the defined shortcuts work only when the settings dialog is still open. I don't remember if that bug was there in 4.0.0 and 4.0.1.
*** This bug has been marked as a duplicate of 156120 ***
#156120 was fixed two months ago in the 4.0 branch ! If what I see came from the same bug, it should not be possible anymore in 4.0.2 ! I believe either #154092 is not a duplicate... or maybe the patch for #156120 does not fix the bug everywhere.