That is how far I get when trying to debug udev: ~$ /lib/udev/findkeyboards AT keyboard: input/event5
~$ sudo /lib/udev/keymap -i input/event5 Now the cursor runs down the terminal probably waiting for key-strokes. (By the way how can this be stopped properly?) Any keystroke on my keyboard seems to print the corresponding "scan code" in the terminal - lines are moving too fast for reading it but there is some output. However if I close my lid or if I unplug my AC-power then no "scan code" is printed in the terminal. I guess I am missing something here. Sorry, this is all new to me. Any hints? -- unplugging AC-power triggers "lid is closed" event https://bugs.launchpad.net/bugs/585601 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
