Bug 34351 - [Patch] Expose & Dashboard keys don't work on Apple MacBook / MacBook Pro
Summary: [Patch] Expose & Dashboard keys don't work on Apple MacBook / MacBook Pro
Status: RESOLVED FIXED
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: xkb
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-16 10:33 UTC by Bryce Harrington
Modified: 2011-02-17 16:01 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Add-keycode-definitions-required-for-Apples-Expose-D.patch (2.71 KB, patch)
2011-02-16 10:35 UTC, Bryce Harrington
Details | Splinter Review

Description Bryce Harrington 2011-02-16 10:33:43 UTC
Forwarding this bug and patch from Ubuntu:

X.org keyboard database in Ubuntu Karmic doesn't provide keycode mappings nor keysyms for Apples Expose & Dashboard keys (F3/F4) although the Linux kernel's evdev layer reports correct keycodes. The attached patch adds the required keycode definitions to /usr/share/X11/xkb/keycodes/evdev as well as symbols to /usr/share/X11/xkb/symbols/inet (evdev section). Those symbols finally can be used to configure compiz.

Note: I assigned the symbols XF86LaunchA and XF86LaunchB due to a lack of better alternatives.

This is package version:
$ apt-cache policy xkb-data
xkb-data:
  Installed: 1.6-1ubuntu5
  Candidate: 1.6-1ubuntu5
  Version table:
     1.7-1ubuntu3 0
          1 http://de.archive.ubuntu.com lucid/main Packages
 *** 1.6-1ubuntu5 0
        500 http://de.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
Comment 1 Bryce Harrington 2011-02-16 10:35:10 UTC
Created attachment 43443 [details] [review]
Add-keycode-definitions-required-for-Apples-Expose-D.patch
Comment 2 Sergey V. Udaltsov 2011-02-17 16:01:40 UTC
Fair enough, committed. Thanks.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.