caps lock now a per-top-level-window "setting"? :-)

I don't know what to say to this bug, other than that a) I've verified its
existence, b) I'm sort of glad I generally use ctrl:nocaps, and c) FSVO 'cool'.

(In reply to comment #1)
> I don't know what to say to this bug, other than that a) I've verified its
> existence, b) I'm sort of glad I generally use ctrl:nocaps, and c) FSVO 'cool'.

I got interested in this bug because I was originally assigned it, just to be
unassigned 5 mins later. :(

The behavior itself isn't really a bug though, is it? The same thing works with
num lock and probably other keys as well. The bug is not having a GUI to control
the behavior. It can get annoying when Num Lock keeps going off..

Whoohoo, another GNOME bug.
14:56 < Treenaks> jdub: try unchecking the "per window" stuff in the gnome
keyboard layout manager app
14:56 < Treenaks> jdub: that "fixes" it for me

... and here too. Surely this should be off by default, mimicking not only
standard behaviour, but what people expect?

that's not a bug, that's a feature :) What do you want to change about it ? the
default config ?

Yes. This is a highly unexpected feature, and may catch some Ubuntu users
off-guard, putting them into precarious situations at home, in the car, or in
the workplace.

Most misguided feature ever; I believe the default changed from off to on
recently. Can we change it back to off? Cheers.

I was wondering why my Num Lock kept going off.

The upstream bug about this is http://bugzilla.gnome.org/show_bug.cgi?id=161343

Could you go here to argues guys ? :)

 control-center (1:2.9.91-0ubuntu1) hoary; urgency=low
 .
   * New upstream release:
     - check for xmodmap files, and offer to load them.
     - changing the default value for "handleIndicators" to false
       (Hoary: #5763).