Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4398828

Swing conflicts with X11 forwarding from ssh

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: P3 P3
    • None
    • 1.2.2
    • client-libs
    • 2d
    • sparc
    • solaris_8



      Name: boT120536 Date: 12/15/2000


      java version "1.2.2"
      Solaris VM (build Solaris_JDK_1.2.2_05a, native threads, sunwjit)

      ssh is a secure replacement for telnet and rlogin. Besides that, it can provide
      a secure and transparent tunnel for X11, usually called forwarding. ssh does
      this by establishing some kind of X11 proxy on the remote system to catch all
      X11 communication and transfer it through the secure connection.

      This forwarding doesn't work with Swing applications (at least here). Windows
      stay empty first and start to fill with some garbage, when you try to hit the
      menubar blindly or move the mouse over a toolbar.

      Steps to reproduce:

      - log remotely into another system (Solaris 2.6 and 8 boxes here) with ssh.
      - ensure that the forwarding is active (the $DISPLAY environment variable should
      contain someting like rembox:10, where remotebox is the hostname of the distant
      machine)
      - start a simple application like xterm or dtterm to ensure the forwarding is
      working
      - start a java application which uses swing, e.g. SwingSet from the Java 1.2
      demo from Solaris 8 in /usr/demo/JAVA1.2/demo/jfc/SwingSet
      - The progress indicator is still working, but the main app doesn't do. If
      you're lucky, you see a part of the menu bar in the upper left corner, otherwise
      the windows stays empty. Click into the window randomly to see some action.

      AWT seems to work, at least the GraphicsTest demo applet (in
      /usr/demo/JAVA1.2/demo/applets/GraphicsTest) does.

      If you telnet from the remote system into another system (desktop -> rembox -
      anotherbox) and start you swing apps there, they work.
      I'm no Swing or Java GUI expert, but I guess the problem is about believing the
      ssh proxy to be a local display and trying to use shared memory instead of
      socket communications.
      (Review ID: 108625)
      ======================================================================

            tdv Dmitri Trembovetski (Inactive)
            bonealsunw Bret O'neal (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: