Bug#527083: xkb as well...

[Chris Chiappa <chris@chiappa.net>]

Perhaps unsurprisingly, using xkb exhibits the same issue...

$ setxkbmap -option ctrl:nocaps
$ setxkbmap -print
xkb_keymap {
        xkb_keycodes  { include "evdev+aliases(qwerty)" };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include "pc+us+inet(evdev)+ctrl(nocaps)"        };
        xkb_geometry  { include "pc(pc101)"     };
};
...<time passes>...
$ setxkbmap -print
xkb_keymap {
        xkb_keycodes  { include "evdev+aliases(qwerty)" };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include "pc+us+inet(evdev)"     };
        xkb_geometry  { include "pc(pc101)"     };
};

Oddly, unplugging and replugging the keyboard doesn't exhibit this behavior
and I don't see any messages about USB devices being fiddled.

-- 

..ooOO chris@chiappa.net              | My opinions are my own  OOoo..
..ooOO chris.chiappa@oracle.com       | and certainly not those OOoo..
..ooOO http://www.chiappa.net/~chris/ | of my employer          OOoo..