> Is there a way to trace the whole sequence done during boot-up?
Something like this. "udevadm test /devices/.../" (the sysfs path) will
show the matches and commands run.
Unfortunately the original lsinput/ udev dump logs don't match your
current USB setup any more (event7/event8), so I had to guess. But the
only other "MOSART" device is the "mouse" part of that device, so I
guessed it wouldn't be that. Just to cover all cases, does this work?
ENV{ID_VENDOR}=="MOSART_Semi.", ENV{ID_MODEL_ID}=="0102",
ID_CLASS=="mouse", RUN=+"keymap $name usb-mosart-0102"
if not, does this?
ENV{ID_VENDOR}=="MOSART_Semi.", ENV{ID_MODEL_ID}=="0102", RUN=+"keymap
$name usb-mosart-0102"
BTW, you don't really need to reboot after changing the rule. Either
just unplug/replug the keyboard, or do
sudo udevadm trigger --subsystem-match=input
--
X-Tension XK-200 Multimedia Keyboard: Media Player key wrong
https://bugs.launchpad.net/bugs/94366
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
