Bug 450326

Summary: hal/ Fixing non-mapped vendor buttons
Product: Red Hat Enterprise Linux 5 Reporter: ritz <rkhadgar>
Component: halAssignee: Richard Hughes <rhughes>
Status: CLOSED ERRATA QA Contact: desktop-bugs <desktop-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2CC: cbolz, cmeadors, jfeeney, martinez, mgordon, rhughes, syeghiay, tao, zcerza
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: hal-0.5.8.1-36 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-30 08:32:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 490507    
Bug Blocks: 445871, 447321, 486024    
Attachments:
Description Flags
update spec for BuildRequire
none
patch hal to support keymapping none

Description ritz 2008-06-06 17:34:09 UTC 
Description of problem:
The Dell Latitude has a hotkey Fn+F1 to suspend. This doesn't work.

How reproducible:
always

Steps to Reproduce:
Press Fn+F1

Actual results:
nothing happens
On Text Console you see the following messages:
atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.

Expected results:
Machine should go to suspend mode

Additional info:
I have backported keyboard quirk from upstream, patch attached. Additionally,
user would need to induce fdi for dell keyboard mapping[1].

[1]
http://gitweb.freedesktop.org/?p=hal-info.git;a=blob_plain;f=fdi/information/10freedesktop/30-keymap-dell.fdi
Comment 1 ritz 2008-06-06 17:34:09 UTC 
Created attachment 308549 [details]
update spec for BuildRequire
Comment 2 ritz 2008-06-06 17:39:12 UTC 
Created attachment 308550 [details]
patch hal to support keymapping 

this patch updates hal to support key mapping. 

add originating_device property to input device to enable matching keyboard
mapping rules against atkbd.

installs hal-setup-keymap which maps keymapping.

finally, install rules for handling keymapping.
Comment 3 Richard Hughes 2008-07-14 16:01:37 UTC 
Nice one Ritesh, I was going to do this tomorrow! I'm going to pull all the
30-keymap-* files into hal also, as hopefully the thinkpad bits can be pulled in
also.

+1 from me.
Comment 4 John Feeney 2008-07-24 17:23:22 UTC 
Ritesh,
I was wondering if you could provide x86_64 hal rpms similar to i386 ones you
provided on your people page. Thanks if you can. In case you were wondering,
I would like to test them on a laptop that only supports x86_64.
Comment 5 ritz 2008-07-25 17:13:35 UTC 
_TEST_ packages uploaded to http://people.redhat.com/rkhadgar/work/bz45036/

-- ritz
Comment 7 Cameron Meadors 2009-03-18 16:41:44 UTC 
This looks like it would affect *many* if not all laptops.  Is this a new feature (that laptop keyboards work)?  Is there a specific set of laptops that the keymapping was broken and is now fixed by this change?
Comment 25 errata-xmlrpc 2010-03-30 08:32:36 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0256.html