Bug 5252

Summary: Keyboard mapping sometimes switches to American
Product: LTSP Reporter: Bob <R.Vickers>
Component: local devicesAssignee: Jim McQuillan <jam>
Status: ASSIGNED --- QA Contact:
Severity: normal    
Priority: high    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Patch for /etc/rc.localdev to restrict size of Samba logs

Description Bob 2005-12-06 21:33:41 UTC 
Occasionally the X server on our LTSP terminals spontaneously switches keyboard
layout from  gb(pc105) to American so that, for example, the hash key (#) comes
out as backslash.

One one occasion when this had happened I discovered the following message in
Xorg.0.0.log:
  (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap

I have also noticed many files in /tmp/samba with names like ip.address.log.

My analysis of the problem (partly based on guesswork) is as follows:

(1) whenever the X server is reset it recompiles the keymap files into the
directory /usr/X11R6/lib/X11/xkb/compiled

(2) Because of links this directory is actually in the /tmp filesystem, so if
there is insufficient space in /tmp the keymap file cannot be recompiled.

(3) Whenever an SMB client attempts to connect then a log file is created in
/tmp/samba. This can happen a lot if you have a large network with many Windows
boxes, especially if their personal hygiene is imperfect.

My solution is to reconfigure Samba not to create unlimited log files, and I
will attach a patch to /etc/rc.localdev which does that.
Comment 1 Bob 2005-12-06 21:35:54 UTC 
Created attachment 4009 [details] [review]
Patch for /etc/rc.localdev to restrict size of Samba logs
Comment 2 chemtech 2013-03-15 14:10:21 UTC 
Bob 
Do you still experience this issue with newer drivers ?
Please check the status of your issue.
Comment 3 Bob 2013-03-15 15:01:27 UTC 
Sorry, we do not run LTSP any more so I am not in a position to test

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.