Bug 121995

Summary: German keyboard not set-up correctly (Emacs displays "M-7" instead of "{")
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Ulrich Windl <Ulrich.Windl>
Component: Update ProblemsAssignee: Stefan Dirsch <sndirsch>
Status: RESOLVED INVALID QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: alexanderwitzel, ms, nordhaus
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Y2logs

Description Ulrich Windl 2005-10-10 15:20:12 UTC
After update from 9.2 to 10.0, the German keyboard did not work correctly. The
keyboard section had to be fixed manually. Before update the keyboard did work.
Comment 1 Stefan Hundhammer 2005-10-10 15:27:34 UTC
What exactly did you do to change this? 
AFAIK the X keyboard configuration should not have changed - it should be 
something like this 
 
Section "InputDevice" 
  Driver       "kbd" 
  Identifier   "Keyboard[0]" 
  Option       "Protocol" "Standard" 
  Option       "XkbLayout" "de" 
  Option       "XkbModel" "pc105" 
  Option       "XkbRules" "xfree86" 
  Option       "XkbVariant" "nodeadkeys" 
EndSection 
 
Are you sure there was no KDE keyboard applet involved? I had problems with that 
one interfering with my Emacs keys some releases ago, too. 
Comment 2 Michael Radziej 2005-10-10 17:33:51 UTC
Can you please attach the /var/log/YaST2 directory (as a tar file)?
Please take a look at http://www.opensuse.org/Bug_Reporting_FAQ#YaST
if you have any problems.

Comment 3 Ulrich Windl 2005-10-11 06:14:38 UTC
Until I can represent more details, what is the likelyhood that
"XkbRules" "xorg" did work in 9.2, but
"XkbRules" "xfree86" is required for 10.0?
Comment 4 Stefan Hundhammer 2005-10-11 09:38:42 UTC
Hm - good point. 
Marcus? 
Comment 5 Stefan Nordhausen 2005-10-11 19:21:52 UTC
Had the same problem: After update from 9.2Pro to 10.0 (box) the keyboard did
not work correctly. Keys like $%&/ were ok, but German Umlaute like üäö did not
work, neither did switching to text mode via CTRL+ALT+F1. Tried to fix that via
language settings in YaST, but that didn't help.
Comment 6 Stefan Nordhausen 2005-10-11 19:25:00 UTC
Created attachment 53765 [details]
Y2logs
Comment 7 Stefan Nordhausen 2005-10-12 08:03:07 UTC
Got it to work after beeing inspired by Ulrich ;) The line

  Option       "XkbRules" "xfree86" 

was missing in my xorg.conf file. I added it and everything was fine! 

Interestingly, there are also the files

- xorg.conf.saxsave (created 18:21)
- xorg.conf.install (created 18:02)
- xorg.conf.post_xorg-x11-server (from 2004)

in wich this line is still present. To give you a point of reference, my
/etc/SuSE-release shows 18:22 as modification time. So the line must have been
lost somewhen during the update process.
Comment 8 Marcus Schaefer 2005-10-12 10:31:34 UTC
In case of update I did not touch the xorg.conf file. Stefan do you know 
what the post install script does ? 
Comment 9 Marcus Schaefer 2005-10-12 10:32:06 UTC
*** Bug 127519 has been marked as a duplicate of this bug. ***
Comment 10 Alexander Witzel 2005-10-12 11:27:57 UTC
The line "XkbRules" "xfree86" was not missing here, but i have the same   
problems with the german keyboard (special characters and german "Umlaute"    
and sz)(Report: 127519). Tried to fix the problem with the   
y2logs-attachment....now there are a lot of special characters usable but the   
german "Umlaute" and some other s.c. are missing   
   
at sax2 i can't choose the keyboard assignments like Latin etc.  
   
   
   
Comment 11 Stefan Dirsch 2005-10-12 12:11:56 UTC
Indeed, the rules files have changed for 10.0.

SL <= 9.1: only xfree86* exists
9.2/9.3: xfree86* --> xorg*
10.0: xfree86* --> base* (xorg* does *not* exist)

Marcus, did SaX2 ever wrote 

  XkbRules" "xorg"

???
Comment 12 Stefan Dirsch 2005-10-12 13:06:54 UTC
Marcus just told me that SaX2 never did write XkbRules" "xorg". Probably you did
used a 3rd party tool (which is not supported by us) to configure your gfx board.

--> INVALID

Trying to close as INVALID.