This is the output of command "xinput list" for my latest Xephyr in multi-seat mode *without* this patch applied.
⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ SIGMACHIP Usb Mouse id=6 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ HID 04f3:0103 id=7 [slave keyboard (3)] In this scenario, when I toggle NumLock or CapsLock, the keyboard reacts as expected (I mean, I can enable CapsLock and start typing capital letters, and I can enable NumLock and start typing numbers in my num pad), but the keyboard LED's are always *off*. 2016-02-08 17:52 GMT-02:00 Adam Jackson <a...@nwnk.net>: > On Fri, 2015-12-11 at 11:43 -0200, Laércio de Sousa wrote: > > From: Mikhail Krivtsov <mikhail.krivt...@gmail.com> > > > > When one hits {Num,Caps,Scroll}Lock key on a Xephyr's keyboard, > > keyboard itself works as expected but LEDs are not updated > > and always stay in off. > > > > Currently logical LEDs are propagated to physical keyboard LEDs > > for "CoreKeyboard" only. All "kdrive" keyboards are not > > "CoreKeyboard" and LEDs of "kdrive" keyboards are always "dead". > > > > One possible solution is cloning "CoreKeyboard" LEDs to all > > "kdrive" keyboards. > > Can you describe this scenario better? What does the output of 'xinput > list' look like when you encounter this? > > - ajax > -- *Laércio de Sousa* *Orientador de Informática* *Escola Municipal "Professor Eulálio Gruppi"* *Rua Ismael da Silva Mello, 559, Mogi Moderno* *Mogi das Cruzes - SPCEP 08717-390* Telefone: (11) 4726-8313
_______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel