Bug 459174

Summary: Undefined keycodes in xev on US layout for HP Pavillion zx5000
Product: [openSUSE] openSUSE 11.1 Reporter: Leslie Smith <leslie>
Component: Mobile DevicesAssignee: Timo Hoenig <thoenig>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P3 - Medium    
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: openSUSE 11.1   
Whiteboard:
Found By: Community User Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Leslie Smith 2008-12-15 18:05:59 UTC 
Keycodes 187, 245, and 146 are noted by the xev program notes these keys as having nosymbol.  These keycodes are accessed by pressing the first of 3 programmable  quick launch buttons (it has a camera picture on it), the fn F1 key with a blue "?" on it, and the fn F6 with the blue lock on it.  The following output from the xev program is detailed for each key along witht he function of each key for windows.  These keys are intended to be programmable however.

1st of 3 (with camera picture) programmable quick launch button
Opens My Pictures folder and then launches the default photo and imaging software application.

KeyPress event, serial 34, synthetic NO, window 0x1a00001,
root 0x6a, subw 0x0, time 103132628, (860,333), root865,358),
state 0x0, keycode 187 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False


fn F1 ?
The Help and Support Center provides a comprehensive online
resource tool for contacting an HP support specialist, for
downloading the latest software driver updates and product
information, and for learning more about using and maintaining
your notebook.
Press the Fn+F1 hotkey to open the Help and Support Center
window.

KeyPress event, serial 34, synthetic NO, window 0x1a00001,
root 0x6a, subw 0x0, time 103116094, (860,333), root865,358),
state 0x0, keycode 245 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False



fn F6 Quick Lock Screen
KeyPress event, serial 34, synthetic NO, window 0x2000001,
root 0x6a, subw 0x0, time 14004101, (146,-505), root1243,30),
state 0x0, keycode 146 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False


This occured on opensuse 11.1 RC1.
uname -a
Linux linux-jce2 2.6.27.7-8-default #1 SMP 2008-11-25 00:02:37 +0100 i686 i686 i386 GNU/Linux
Comment 1 Danny Al-Gaaf 2009-01-08 12:22:31 UTC 
If there is a key event, it's not a HAL problem (HAL only set keys for unknown scancodes, nothing more).
Comment 2 Stefan Dirsch 2009-01-08 16:45:26 UTC 
Keycodes 187, 245, and 146 should return a keysymbol. Please add the output of

  setxkbmap -print  -v
Comment 3 Leslie Smith 2009-01-09 05:00:18 UTC 
I ran the above command and this is the output. 

setxkbmap -print  -v
Trying to build keymap using the following components:
keycodes:   xfree86+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc+us+inet(microsoftpro)
geometry:   microsoft(natural)
xkb_keymap {
        xkb_keycodes  { include "xfree86+aliases(qwerty)"       };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include "pc+us+inet(microsoftpro)"      };
        xkb_geometry  { include "microsoft(natural)"    };
};
Comment 4 Stefan Dirsch 2009-01-09 05:13:44 UTC 
Looks fine (xfree86 is used for keycodes). In your case Keycodes 187, 245, and 146
should map to

<I3B> =   187;
<I75> =   245;
<I12> =   146;

according to /usr/share/X11/xkb/keycodes/xfree86, but obviously this doesn't work. These key symbols then can be used for a inet keyboard layout (see /usr/share/X11/xkb/symbols/inet).

No idea what's going on here.
Comment 5 Stefan Dirsch 2009-01-09 05:24:12 UTC 
This issue is very similar to Bug #462878.

Reassigning to Mobile Devices team. Hopefully they've seen this before and know what's wrong here.
Comment 10 Stefan Behlert 2009-05-27 10:30:19 UTC 
Anything we can do here, or do we need to close the bug?
Comment 11 Timo Hoenig 2010-10-29 11:40:07 UTC 
No hardware available.  Closing.