Basically, your fix is to run the X server in a mode that doesn't freak
out the Java AWT. Many X servers support a "-bpp" option that sets bits
per pixel:
Xvnc -bpp 8 ...
There's also been some past discussion in this group recommending a
value of 15, although I can't vouch for that one.
If you run at 8 bpp and it's still unhappy, it may be choosing a default
8-bit visual the AWT doesn't like. That's unlikely, but the -cc option
is useful if that occurs.
As for the missing dingbats, that's had lots of discussion in past mail.
I suggest you dive into the archives for the details. Basically, the
solution involves acquiring some fonts and making some configuration
changes to use those fonts. It's an annoying, but not fatal, problem.
Nathan
Brandon Anderson wrote:
>
> Here is the results from xdpyinfo...
>
> screen #0:
> dimensions: 1024x768 pixels (260x195 millimeters)
> resolution: 100x100 dots per inch
> depths (1): 16
> root window id: 0x25
> depth of root window: 16 planes
> number of colormaps: minimum 1, maximum 1...
>
> As you can see, the depth is really only 16 bits. But one thing that might be
> important to mention is that I'm not actually running X. I'm running Xvnc.
> I've tried the same program on an actual X console(just a second ago), and it
> seems to work. Any ideas on how I can get this to work in Xvnc, or does it
> sound like I'm just going to be screwed? Oh by the way, on a side not,
> everytime I run any program that uses awt classes I get the following warning a
> whole bunch of time. It doesn't seem to cause any problems but its starting to
> get annoying.
>
> Font specified in font.properties not found [--zapf
> dingbats-medium-r-normal--*-%d-*-*-p-*-adobe-fontspecific]
>
> I'd prefer to fix without having to comment out the 20-30 lines in the
> font.properties, but if that's the only solution....
>
> On Wed, 21 Jul 1999, Nathan Meyers wrote:
>
> > There are a lot of X server display depths and visuals that the AWT
> > doesn't support, because they don't happen to exist on Solaris boxes
> > :-(. But do you *really* have a 1024-bit deep display??? Could you post
> > the results of running xdpyinfo? This I gotta see :-).
> >
> > Nathan
> >
> >
> > Brandon Anderson wrote:
> > >
> > > I've been trying to get Java 1.2 pre v2 to run on my Redhat 5.2 box. I
> > > evidently have run into some problems that make no sense to me at all, and
> > > was wondering if anyone else had any suggestions.
> > >
> > > The application that I'm trying to get to run connects to another machine
> > > and then should show a simple login screen. It connect to the other
> > > machine just fine, but when it goes to display the login screen all I get
> > > is blackscreen with a menubar across the top. After about 15 sec of total
> > > cpu usage I get the following error message:
> > >
> > > Exception occurred during event dispatching:
> > > java.lang.InternalError: Unsupported 1024-bit depth
> > >
> > > at sun.awt.motif.X11Graphics.X11LockViewResources(Native Method)
> > > at sun.awt.motif.X11Graphics.lock(X11Graphics.java:797)
> > > at sun.java2d.loops.LockableRaster.lock(LockableRaster.java:163)
> > > at
> > > sun.java2d.loops.RasterOutputManager.convertFrom(RasterOutputManager.java:1414)
> > > at
> > >
>sun.java2d.loops.RasterOutputManager.performOpaqueBlit(RasterOutputManager.java:979)
> > > at
> > >
>sun.java2d.loops.RasterOutputManager.compositeSrcDst(RasterOutputManager.java:654)
> > > at
> > > sun.java2d.loops.RasterOutputManager.renderImage(RasterOutputManager.java:472)
> > > at
> > > sun.java2d.SunGraphics2D.renderingPipeImage(SunGraphics2D.java:2040)
> > > at sun.java2d.SunGraphics2D.drawImage(SunGraphics2D.java:1634)
> > > at sun.awt.motif.X11Graphics.drawImage(X11Graphics.java:583)
> > > at javax.swing.JComponent.paint(JComponent.java:536)
> > > at java.awt.Container.paint(Container.java:770)
> > > at javax.swing.JFrame.update(JFrame.java:255)
> > > at
> > > sun.awt.motif.MComponentPeer.handleEvent(MComponentPeer.java:248)
> > > at java.awt.Component.dispatchEventImpl(Component.java:2429)
> > > at java.awt.Container.dispatchEventImpl(Container.java:1032)
> > > at java.awt.Window.dispatchEventImpl(Window.java:714)
> > > at java.awt.Component.dispatchEvent(Component.java:2289)
> > > at java.awt.EventQueue.dispatchEvent(EventQueue.java:258)
> > > at java.awt.EventDispatchThread.run(EventDispatchThread.java:68)
> > > SIGSEGV 11* segmentation violation
> > > stackpointer=0x416f4e7c
> > >
> > > Full thread dump Classic VM (Linux_JDK_1.2_pre-release-v2, green threads):
> > > "AWT-Finalizer" (TID:0x404c55f8, sys_thread_t:0x8681d98, state:CW)
> > > prio=9
> > > at java.lang.Object.wait(Native Method)
> > > at java.lang.Object.wait(Object.java:424)
> > > at sun.awt.AWTFinalizer.run(AWTFinalizer.java:46)
> > >
> > > The Full Thread dump continues on for several screens and I'll omit that
> > > from here. I'm using the Green Threads and the JIT is disabled. Any
> > > suggestions on what this problem is?
> > >
> > > Thanx in advance
> > >
> > > ----------------------------------------------------------------------
> > > To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> >
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
