Bug 380463

Summary: Keyboard model misdetected (live cd)
Product: [openSUSE] openSUSE 11.0 Reporter: Vincent Untz <vuntz>
Component: X.OrgAssignee: Stefan Dirsch <sndirsch>
Status: RESOLVED INVALID QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Beta 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Vincent Untz 2008-04-16 14:41:12 UTC
I've tried the latest GNOME live cd (what will be beta 1 in a few days), and the keyboard model that seems to be automatically detected is MS Natural Keyboard Pro (as far as I can see in gnome-keyboard-properties). I only have the laptop keyboard, so this looks a bit wrong.
Comment 1 Stefan Dirsch 2008-04-16 14:55:30 UTC
Please attach 

/var/log/SaX.log
/etc/X11/xorg.conf
/var/log/Xorg.0.log
Comment 2 Vincent Untz 2008-04-16 15:41:15 UTC
I attached them to bug 380462:

/var/log/SaX.log: https://bugzilla.novell.com/attachment.cgi?id=208360
/etc/X11/xorg.conf: https://bugzilla.novell.com/attachment.cgi?id=208359
/var/log/Xorg.0.log: https://bugzilla.novell.com/attachment.cgi?id=208361
Comment 3 Stefan Dirsch 2008-04-16 16:18:03 UTC
microsoftpro is the standard keyboard model, which is now used for everybody unless a different model is detected. ==> INVALID
Comment 4 Vincent Untz 2008-04-16 16:30:29 UTC
This sounds wrong to me: gnome-keyboard-properties can display the layout in a nice image and if microsoftpro is the keyboard model, I get a keyboard that doesn't look like mine because it's curved.
Comment 5 Stefan Dirsch 2008-04-16 16:49:01 UTC
This tool just scaled my Dualhead desktop with a 3360x1050 resolution to a singlehead desktop with a 640x480 resolution and then I even couldn't find this tool on this tiny desktop. I'm reluctant to run this tool any time soon again.

This might sound rude, but if you don't like this keyboard model as default for your laptop chose another one as your favorite. As it's mostly impossible to detect a keyboard we decided to chose one, which works best for all keyboards available. So consider it the best available technical solution for this case. Thanks.