unity-system-compositor reacts to key codes instead of scan codes
Bug #1514059 reported by
Andreas Pokorny
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Undecided
|
kevin gunn | ||
Unity System Compositor |
Fix Released
|
Undecided
|
Unassigned | ||
unity-system-compositor (Ubuntu RTM) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Unity System Compositor handles Power Key and Volume keys. (Volume keys only by not resetting the inactivity timeout). But it tests for specific key codes instead of using the scan codes defined by the kernel. So it relies on mirserver doing a service side mapping. This only worked so far because the android input stack has a hard coded key map.
The upcoming evdev input and the new input stack will not provide that.
Related branches
lp:~andreas-pokorny/unity-system-compositor/fix-1514059-and-keep-display-on-for-key-presses
- Alexandros Frantzis (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 162 lines (+81/-14)2 files modifiedsrc/screen_event_handler.cpp (+20/-10)
tests/unit-tests/test_screen_event_handler.cpp (+61/-4)
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
Changed in unity-system-compositor: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix committed into lp:unity-system-compositor at revision None, scheduled for release in unity-system- compositor, milestone Unknown