Not sure what the ultimate problem was, but I blew away my ~/.config/dconf directory, rebooted and caps lock started working again. Very odd failure case, and I have no clue what changed in my configuration to break things that utterly.

On 11/06/2012 04:39 PM, Luke Yelavich wrote:
On Tue, Nov 06, 2012 at 05:28:01PM EST, Nolan Darilek wrote:
How do I debug this?

I get that accessibility of 12.10 isn't guaranteed, but it seems
silly that it should work fine, then break utterly with no apparent
cause.
I'd be interested to know if this problem regularly appears after a restart, 
and then suspend/resume again. I was using 12.10 all of last week during UDS, 
and suspended and resumed regularly, with no ill effects with Orca usage and 
capslock. I also wonder whether capslock and insert behave normally under 
normal circumstances on the hardware you have.

If this has only recently started occurring, there is every chance that an 
update has broken something slightly somewhere, in which case I can only advise 
trying a live CD and suspending/resuming with the live CD, and observing 
behavior post resume.

Luke



--
Ubuntu-accessibility mailing list
Ubuntu-accessibility@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility

Reply via email to