Appletviewer works on my X-server under 1.1.5, but not under 1.1.6 or 1.2beta3-G.

Note: The X-server is unchanged, I merely changed the JDK in my path...

The window comes up (sized too small to be usable, I have to resize it) and does not update to show its contents.

My X-server is MacX Version 1.5 (running on a Macintosh 7600/120, MacOS 8).
The problem is even worse on a Pentium II, Windows/NT X-server I tried , Exceed, (version unknown).

Note: This bug affects all Java applications and applets, not just appletviewer.

N/A

  xxxxx@xxxxx   1998-02-17
I brought up appletviewer on a regression test:

	test/java/awt/LightweightComponent/LightweightTest/LightweightTest.html

In both 1.1.5 and 1.1.6 (using /usr/local/java/jdk*), the appletviewer
comes up a reasonable size (apparently, the same size on both). Note that
this applet tests a font problem fixed in 1.1.6, so the contents of the
appletviewer in 1.1.6 use a larger (correct) font.

Any easy way to run the test is to run the attached scripts
(test1.1.5.csh and test1.1.6.csh).

  xxxxx@xxxxx   1998-02-18
I removed the keyword based on Jeff's evaluation that this is not a regression:

"I spent a good deal of time with the submitter of 4112070, and
his mac has suddenly stopped displaying all java apps run on 
a sparc machine and xhosted to his mac. The beanbox and other test apps
work fine on every other machine (unix, pcs running PC-X and
Hummingbird exceed). At this point, I would chalk this problem
up to his macintosh having a net or X problem, rather than
the JDK.
We may want to leave the bug open, but take away the 116regress
keyword."

We tried to reproduce this problem under 1.1.6 and did not find the problem to occur.  We are moving it to incomplete and will wait for verification from submitter that the bug no longer exists.

  xxxxx@xxxxx   1998-06-11

The bug still persists. I have been able to work around it by running the xserver in full screen root mode, as opposed to the problematic "rootless"
mode refered to in this bug.
In rootless mode, *sometimes* it works partially (the windows content region is null and only the menus work ). Sometimes it works not at all (the JVM hangs before the first window is ever displayed). Extremely rarely , it works correctly. 
I have physically changed the computer I was using since the original bug report. No change...
I will see if I can get someone elses Mac in here, with a different copy
of the x-server software ASAP.

FYI - Please note again, only Java applications are affected. The X-server shows no signs of any other misfuntion with any other x-client.

JDK 1.1.6 is the test reference.
=======
I have enlisted the help of other MacUsers to see if they have the same trouble.
If they can get it to work, then we need to figure out why it no longer works
on my machine, at least in so far as to exclude the awt as the culprit.
If they cannot get it to work, then we can assume the bug is in MacX or the network and can close this bug against the awt.
Stay tuned. I am waiting for responses.

  xxxxx@xxxxx   1998-06-24

Oh happy day! I have a reproducible case in my office.
I set my path to JDK1.1.3, its works great.
I set my path to JDK1.1.6, I get empty content regions.

So ... whats next?

------------------

This must be a bug in the MaxX X-Server. Will not fix.

  xxxxx@xxxxx   1999-06-22

I would not be so quick to chalk this problem up
to anything.  It's been reproduced on several
machines using multiple X servers.  How could it
be a net problem?  (The net doesn't know whether
we're using JDK 1.1.5 or 1.1.6.)  Sure it's an X
problem, but is the problem with the server or
the client?  Having reproduced the bug with two
presumably independent servers, I'd look to the
client.

Just wanted to let you know that we are having this problem too!
I'm sorry to say that I have not found been able to find a workaround.
We are also trying to use JDK 1.1.6 under the MacX X-server and getting the
blank (blue) screen.
Similar details are:
* Unix machine is a DEC alpha
* Worked fine using JDK 1.1.5
* Works fine using the DEC window manager
* Works fine using Exceed X-server for the PC
It seems very unlikely that MacX or eXodus is the 
problem when everything worked fine before we 
installed JDK 1.1.6

Hi all:
We are trying use the JDK 1.1.6 runtime 
under an X-server (eXodus and MacX) on a
Macintosh platform, and we can't get 
anything java-based (applets/applications)
to run at all (we just get a blue screen).
Here are some details:
* The Unix machine is a Sun box running Solaris 2.6.
* Everything runs fine under Open Windows
* Everything runs fine under JDK 1.1.5
I can't believe Sun would let this happen,
since there are many people out there not 
sitting directly on the server.
Any help would be greatly appreciated.
	Albert 

Hi,
Ours don't work either!
We are using Chameleon Unixlink97.
It was fine with jdk1.1.5.

I've encountered the same bug using the latest
release of eXodus: all Swing apps I tried  under 
jdk116/Swing 102 work with the rooted screen, but
fail as described with the rootless screen. This 
occurs with both linux and Solaris clients.
 
I submitted this as a bug report to White Pine,
who are investigating. But for now the only
workaround is to use the rooted screen.

I think this is related to Bug# 41771579. We can
not get any JDK1.2b4 applications to display
remotely on any other platform. This makes it
very difficult to develop in Java, as not everyone
here has a Sun on their desk!

2rad is refering to bug 4171579.

I believe I've seen the same bug Solaris_JDK_1.2.1_02
I can run a simple GUI on the sun on my desk:
Machine hardware:   sun4m
OS version:         5.6
Processor type:     sparc
Hardware:           SUNW,SPARCstation-4
but on a remote machine acting as an X client
the frame appears but there is nothing in it.
( remote machine = 
Machine hardware:   sun4u
OS version:         5.6
Processor type:     sparc
Hardware:           SUNW,Ultra-5_10 
)
it works with java 1.1.7 both ways

How can it be a bug in the MacX X-Server when
White Pine eXodus, eXceed, Chameleon Unixlink97
and pretty much every other X-Server have the
same problem ? Are they all wrong ?
Albert Balcells
Software Engineer
Optimum Group

How can this be closed based on "must be a bug in the MacX X-Server".
 That is so lame and further, simply NOT true.  This bug was very clearly
visible with _MULTIPLE_ X-servers running on MULTIPLE platforms - in my own
case I saw it using Hummingbird eXceed on Windows NT.  The common denominators
when the problem has occurred are:
X-Server in _Rootless_ mode.
Problem does not occur prior to JDK 1.1.6.
Problem does not occur with any other X-clients.
Problem is typically that the windows are too small and have to be manually
re-sized.
I can't believe you have marked this 'closed - will not fix'.  That is so lame
and arrogant.
Dr. Mel Martinez
Applications Architect
WebCentric, Inc.
mem@jhu.edu