In regard to: Re: Two additional X11 Forwarding questions..., Bob...:
>I've seen this problem with Java programs that use Swing. The AWT programs
>seem to work just fine.
That makes sense, and thanks for pointing it out! AWT uses the underlying
windowing API for a particular OS to paint/draw widgets, whereas Swing did
away with using the "native" widget drawing routines and rolled their own.
I believe that means that Swing just uses lots and lots of low-level X11
stuff, while AWT would use a "high level" toolkit like Xt, Motif, etc.
I'm no X god, so I might not be completely correct here.
> I find that if I 'force' the app to redraw part of
>its window, the buttons and text do show up.
>
>It's really annoying.
Agreed.
I've received responses from several other people, all indicating that
they've seen the same problem too.
This should probably go in the FAQ at www.tigerlair.com/ssh -- I did a
google search on "java ssh forward" and only got hits for Java ssh
clients. There's no mention in any document that I can find anywhere
that forwarding java X11 clients may partially break.
I had noticed that it's possible to sometimes get the widgets to paint
by forcing a redraw (expose events), and if I were desperate I would be
willing to deal with that to get a Java X11 client running over ssh X11
forwarding, but that's not going to be a very good solution for our
network services people. The app in question (Optivity's infocenter) often
gets obscured onscreen by other windows (terminal windows, HP's OpenView,
etc), and re-exposing infocenter's main frame doesn't always cause everything
to be redrawn again. That means that any time you lose part of the window,
you often have to spend some time "mousing around" and covering and revealing
those parts of the frame, to try to get them to finally redraw.
I would love to hear from an SSH and/or Java expert, that could explain
exactly where this problem really lies and if there's anything that can
be done about it. Mark Hahn suggested I try an X protocol debugger, and
posited that the problem could be related to the size of the X requests.
I've been using UNIX and X a long time, but I'm not sure I'm up to that
task yet... :-) It's good advice, though.
We're currently using ssh 1.2.31 on the two machines involved, and I'm
going to try to switch them to OpenSSH 2.9p2 and see if that helps. If
it does I'll certainly send a note back to the list. If not, I'll have
to try get our network services people to use Kerberized rlogin instead,
and see what I can do about setting the DISPLAY for them. I really hope
I don't have to return to the days of using the `xrsh' wrapper script...
Thanks for everyone's responses.
Tim
--
Tim Mooney [EMAIL PROTECTED]
Information Technology Services (701) 231-1076 (Voice)
Room 242-J6, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
