Quack,
On 2020-12-10 07:39, Michael Biebl wrote:
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?
Indeed it seems the change described in this article would affect
ckb-next.
I made the fix on my system but it did not solve anything. Then I looked
deeper and it seems there is a syntax error in the rule, so I fixed it
too. The resulting file is:
--------------------------------------------------
ACTION=="remove", GOTO="ckb_end"
# Mark ckb devices as not a joystick and create symlinks to the virtual
input devices
SUBSYSTEM=="input", ATTRS{name}=="ckb[0-9]: [A-Za-z0-9]*",
ENV{ID_INPUT_JOYSTICK}="", PROGRAM="/usr/bin/env sed 's/[0-9]: /-/'
/sys/class/input/%k/device/name", ENV{.INPUT_NAME}="%c",
SYMLINK+="input/by-id/%E{.INPUT_NAME}-event"
LABEL="ckb_end"
--------------------------------------------------
But if the symlinks look better (there was some kind of underscore or
something before "-event"), that does not solve anything. In fact it
seems these rules are really not that important to make the device work.
So we're back to square one, there is no reason to think the bug is in
ckb-next, so I would wait a bit more before reassigning. Also if you
don't mind I'd be happy to get your help some more :-).
If the comments in the upstream ticket are right, is it not strange that
the way you present available keys affect its availability?
Regards.
\_o<
--
Marc Dequènes
