Bug#976366: Upgrade to 247 broke keyboard input on Wayland session

[Michael Biebl]

Am 08.12.20 um 16:07 schrieb Michael Biebl:
> Am 08.12.20 um 06:14 schrieb Marc Dequènes (duck):
>> I was wondering what make my system so peculiar and stumbled onto this 
>> bug report:
>>    https://github.com/ckb-next/ckb-next/issues/671
>>
>> I haven't tried the ckb-next git version yet but it seems strange that 
>> simply presenting a device's features differently would break things. 
>> If there is a problem in udev or libinput I think it would be good to 
>> track before jumping to an easy workaround. So I'm not reassigning yet 
>> and I'd be happy to have your input.
>>
> 
> Interesting find. That might indeed explain why I was not able to 
> reproduce the issue (and why we were not flooded with bug reports from 
> other users).
> I'm not too familiar with the input stack myself, to conclude where this 
> should be handled.
> One significant change in systemd 247 is
> https://lwn.net/Articles/837033/
> 
> It might be, that ckb-next is affected by this, especially when it deals 
> with handling/creating (input) devices.

I'm inclined to reassign this to ckb-next. WDYT?