X-Win32 Knowledge Base   >   Unable to type in Java Desktop Environment on Solaris 10

Search


About StarNet

StarNet Communications has been a leading developer of X Windows solutions since 1989. After establishing X-Win32 as the de facto standard in the higher education market during the early to mid-1990s -- 150 unlimited Campus Site Licenses worldwide -- X-Win32 has become of one the top three PC X servers in the government and commercial sectors as well.

Unlike its major rivals, Exceed (Hummingbird) and Reflection-X (WRQ/Attachmate), X-Win32 offers a highly focused PC X server that offers superior performance and productivity features, stability, ease of use and low cost (40% or better in most cases).

StarNet also delivers unequaled customer support. Our state-of-the-art engineering infrastructure allows us to fix problems and make a new release available quickly (overnight in many cases). As our testimonials page shows, StarNet customers consistently rate their X-Win32 experience as the best in the industry.




Unable to type in Java Desktop Environment on Solaris 10

When using an Xdmcp session in X-Win32 to login to a Sun Solaris 10 Java Desktop Environment (i.e. Gnome or JDE) session you may experience a problem with typing on the keyboard. This problem may also occur in rexec, rsh, and StarNetSSH sessions running other Gnome applications, such as gnome-terminal. You may also note that applications run under CDE do continue to work correctly. The symptom of the problem is that each time you press a key on the keyboard the cursor will flash, but no character will be sent to your remote applications.

This is actually a problem that can be fixed by simply editing a file on the Sun Solaris machine to prevent keys from being bound to the help, volume_down, volume_mute, and volume_up functions.

Steps to fix the problem

  1. Login to the Sun Solaris 10 system as root
  2. Edit the file /etc/gconf/gconf.xml.defaults/apps/gnome_settings_daemon/keybindings/%gconf.xml
  3. Place the text below into the file
  4. Save the file
  1. Start your X-Win32 Xdmcp session again, the problem should be fixed

    Text for keybindings/%gconf.xml

    ‹?xml version=”1.0”?›
    ‹gconf›
    ‹entry name=”volume_up” mtime=”1110896708” type=”string”›
    ‹stringvalue›‹/stringvalue›
    ‹/entry›
    ‹entry name=”volume_mute” mtime=”1110896705” type=”string”›
    ‹stringvalue›‹/stringvalue›
    ‹/entry›
    ‹entry name=”volume_down” mtime=”1110896702” type=”string”›
    ‹stringvalue›‹/stringvalue›
    ‹/entry›
    ‹entry name=”help” mtime=”1110896698” type=”string”›
    ‹stringvalue›‹/stringvalue›
    ‹/entry›
    ‹/gconf›

    Source: Sunsolve

    Category:Errors
    Category:Input -> Keyboard
    Category:Sessions -> Xdmcp