Just discovered that while can now change keyboard setup in kde  can no
longer  change sessions
with ctl-alt-f2 .

Verified that if I revert to the old xkb directory then ctl-alt-f2 works.

My guess its because sarge uses xfree86 and ltsp uses xorg.

Any ideas?

John


John McMonagle wrote:

>Works for me after I renamed the xkb directory and copied in the files
>from my debian sarge install.
>
>Have no clue how one one would change ltsp to fix this :-(
>
>In the simple case that ltsp is on the application server suppose one
>could copy the application servers xkb files.
>
>In my larger offices I have ltsp loaded on separate servers so that may
>not work as I probably do not X loaded on the server.
>
>As a worse case consider the case where xterminals connect to several
>application servers that have different X implementations. I do not do
>this but can imagine situations where one would want to do it.
>
>The only way out I can see is to have just one set of xkb files. I have
>no clue to what extent you can get away with this with various X
>implementations.
>
>John
>
>Leonid Dubinsky wrote:
>  
>
>>Ondrej Valousek wrote:
>>
>>
>>    
>>
>>>My LTSP4.2 works fine against FC5
>>>      
>>>
>>Ondrej, thank you for your reply - I was starting to worry. I tried the
>>change you suggested, but it did not work. Motivated by the fact that
>>keyboard switcher works for you, I decided to investigate further. See
>>[SOLUTION] below.
>>
>>First sign of problems I saw was: when I try to add a layout to the
>>keyboard switcher, a preview of the keyboard does not work, and I get an
>>error in the xorg.log on the terminal:
>>
>>(EE) Error loading keymap /usr/X11R6/lib/X11/xkb/compiled/server-0_0.xkm
>>
>>I found the following in the man page for setxkbmap:
>>
>>USING WITH xkbcomp
>>If you have an Xserver and a client shell running on different comput-
>>ers  and  XKB  configuration files sets on those machines are different
>>you can get problems  specifying  a  keyboard  map  by  model,  layout,
>>options  names.   The  thing  is the setxkbcomp converts these names to
>>names of XKB configuration files according to files  that  are  on  the
>>client side computer.  Then it sends the file names to the server where
>>the xkbcomp has to compose a complete keyboard map  using  files  which
>>the  server  has.   Thus  if the sets of files differ significantly the
>>names that the setxkbmap generates can be unacceptable  on  the  server
>>side.   You  can  solve  this problem running the xkbcomp on the client
>>side too.  With the -print option setxkbmap just prints the files names
>>in  an  appropriate  format  to its stdout and this output can be piped
>>directly to the xkbcomp input. For example, a command
>>       setxkbmap us -print | xkbcomp - $DISPLAY
>>makes both step on the same (client) machine and loads a  keyboard  map
>>into the server.
>>
>>On my Fedora Core 5 server, "setxkbmap us -print" produces:
>>
>>xkb_keymap {
>>      xkb_keycodes  { include "xfree86+aliases(qwerty)" };
>>      xkb_types     { include "complete"      };
>>      xkb_compat    { include "complete"      };
>>      xkb_symbols   { include "pc(pc105)+us"  };
>>      xkb_geometry  { include "pc(pc105)"     };
>>};
>>
>>Attempt to run this through xkbdcomp on the terminal does, indeed, fail.
>>
>>It turns out that the way xkb files are packaged on FC5 and LTSP are
>>different. For example, symbols/pc is a directory on LTSP, but a file
>>on FC5. I saw some messages in the Fedora lists that mentioned such a
>>change between FC5 Test2 and Final.
>>
>>[SOLUTION]
>>I replaced all the subdirectories and *.dir files in xkb in the LTSP's
>>tree with their analogues from the FC5 install. Keyboard switcher works.
>>This is not a real solution: it is ugly, breaks LTSP upgrade, can break
>>when OS is upgraded on the server etc., but it will have to do until
>>LTSP developers provide a better one :)
>>
>>Now I do not understand why does it work for you...
>>
>>    
>>
>
>  
>


-- 
John McMonagle
IT Manager
Advocap Inc.



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to