Description of problem:

I got used years ago to wake up my systems by pressing num lock twice

(because Linux systems do not like to be woken up with the mouse, and double num lock is a no-op on all operating systems)

With gnome3 that sends dconf and gsetting-daemon in a loop

(something gnome-side wants to interpret the num-lock, wakes up too late, and then tries desperately to reset a state which already changed)

The symptoms change over time but are all horrible:
- severe disk trashing as dconf state is rewritten serially (that seems to be mitigated by tmpfs on /tmp lately)
- input system too busy to accept new typing
- keyboard killed as the kernel inserts new numlock led state changes too fast for the usb queue to process

Nowadays when I log in on gnome3 I have to remember to open a term and kill dconf + gsettings-*  processes before the system gets totally un-responsive

Sometimes I also need to unplug the keyboard physically to force things to settle down long enough before the killing (if I just re-plug the keyboard the mess starts again)

I have to remember not to use the numlock keys as they are not reliable anymore – if I try to use during such an incident, bad things happen when . changes to del and 0 to insert randomly

This is quite broken. Please stop messing with num lock that didn't ask anything of gnome

Version-Release number of selected component (if applicable):
dconf-0.13.0-2.fc18.x86_64
kernel-3.5.0-0.rc7.git0.1.fc18.x86_64
glib2-2.33.4-1.fc18.x86_64

How reproducible:
Always

Steps to Reproduce:
Press num lock twice rapidly to wake up gdm or the lock up screen
  
Actual results:
A mess

Expected results:
Screen lits up because of keyboard activity (and nothing else)

Additional info:
$ setxkbmap -print | grep xkb_symbols
	xkb_symbols   { include "pc+fr(oss)+in(mal):2+us:3+inet(evdev)+terminate(ctrl_alt_bksp)"	};