GNOME Bugzilla – Bug 668525
[PATCH] numlock state tracking wakes up the disk too much
Last modified: 2012-01-24 16:53:39 UTC
Created attachment 205912 [details] [review] Describe the attachment briefly. Following the fix for bug #631989, hitting any lockable modifier (capslock, for example) will cause the numlock state to be written to disk. Wouldn't be so bad except that means fsync() which means spinning up the platter if it's asleep. Attached patch makes my Thinkpad's disk light stop flashing when I hit capslock. I think it still does the right thing for numlock too.
Created attachment 205915 [details] [review] keyboard: Don't save num-lock when caps-lock changes The code would write the num-lock state even if it didn't change.
Does that patch work for you? I think that there were some wrong assumptions about the value of the enum (off == 2, not 0).
Pushed, let me know if I broke something. Attachment 205915 [details] pushed as 89b476e - keyboard: Don't save num-lock when caps-lock changes