Thanks; seems the chromebook kernel keyboard driver isn't sending scan codes along, but the actual key codes seem correct (F1 to F10) *if* they are actually F keys. If they are supposed to do something else, then the kernel needs to be fixed first to report proper scan codes.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248808 Title: [keymap] volume and brightness keys on Samsung Chromebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1248808/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
