Java Display Problem
Submitted by joe..@..me.com
Description
I apparently have something not set up correctly with sendmail, so I captured the image of the message from the spool file...
To: submit@bugs.gnome.org Cc: joework@home.com From: Joe Sokolosky joework@home.com Subject: Java Display Problem GNOME-Terminal X-Mailer: bug-buddy 1.0
Package: gnome-terminal Severity: normal Version: 1.2.1 Synopsis: Java Display Problem GNOME-Terminal Class: sw-bug
Distribution: Red Hat Linux release 6.2 (Zoot) System: Linux 2.2.14-5.0 i686 unknown C library: glibc-2.1.3-15 C compiler: egcs-2.91.66 glib: 1.2.8 GTK+: 1.2.8 ORBit: ORBit 0.5.1 gnome-libs: gnome-libs 1.2.1 libxml: 1.8.7 gnome-print: gnome-print-0.20 gnome-core: gnome-core 1.2.1
Description: Problem Description
I have recently upgraded to GNOME !.2 and have run into a problem when I launch a Java application from either a menu or a panel. However, if I first open a terminal window and run the same command from within this window, things work fine. Prior to downloading GNOME 1.2, I was using the version of GNOME that came on the RedHat 6.2 distribution. I was and am using the Sawmill window manager, version 0.2.27-2. My Java applications were running fine under the old GNOME version.
I downloaded the GNOME 12 packages from Helix and am running it under RedHat 6.2 Linux. I am running Java 1.2.2, and I have noticed this issue with both 3rd part tools (like Borland's JBuilder 3.5) as well as my own applications.
The problem is as follows: I have a launcher set up which executes a script that start JBuilder 3.5.
My launcher has the following properties:on the Basic tab
Name: JBuilder 3.5 Comment: JBuilder 3.5 Command: startJBuilder Type: Application Run in Terminal: Checked
and the following on the Advanced tab:(I am using <blank>
to indicate
there is nothing in that particular field/column):
Try this before using: <blank>
Documentation: <blank>
Language: <blank>
Name: JBuilder 3.5
Comment: JBuilder 3.5
Language: en_US.ISO8859-1 Name: JBuilder 3.5 Comment: JBuilder 3.5
The command, startJBuilder, is a simple BASH shell script which launches JBuilder; I have it installed in my /usr/local/bin directory and I have /usr/local/bin on my PATH. The startJBuilder has the following information (from ls -l):
-rwxrwxrwx 1 root root 84 May 30 19:58
/usr/local/bin/startJBuilder
The contents of this file is (I'm sending any output messages to a file called testlog in my home directory):
#!/bin/bash
cd /usr/local/jbuilder35/bin ./jbuilder > /home/jsokolos/testlog 2>&1
When I click on the launcher, it opens a terminal window and I see the standard font messages being kicked out of Java, the JBuilder 3.5 header/copyright information pops up and then the process dies and closes the terminal window. Because the window was closing on me is why I redirected the output to a file. The contents of the file follows:
Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific]
JBuilder 3.5 Foundation Copyright (c) 1996-2000 Inprise Corporation. All rights reserved.
SIGSEGV 11* segmentation violation si_signo [11]: SIGSEGV 11* segmentation violation si_errno [0]: Success si_code [0]: SI_USER [pid: 0, uid: 0] stackpointer=0xbfffe224
Full thread dump Classic VM (1.2.2-L, green threads):
"Image Fetcher 0" (TID:0x41af03e8, sys_thread_t:0x85d56e0, state:R)
prio=5
"AWT-Motif" (TID:0x41af45c0, sys_thread_t:0x856df28, state:R)
prio=5
"SunToolkit.PostEventQueue-0" (TID:0x41af4ed8,
sys_thread_t:0x835a9b0, state:R) prio=5
"AWT-EventQueue-0" (TID:0x41af4e40, sys_thread_t:0x84400a0,
state:CW) prio=6
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at java.awt.EventQueue.getNextEvent(EventQueue.java:204)
at
java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread.java:96)
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:88)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:79)
"Finalizer" (TID:0x41a0c320, sys_thread_t:0x810ace8, state:CW)
prio=8
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:108)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:123)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:170)
"Reference Handler" (TID:0x41a0c3b0, sys_thread_t:0x8105f98,
state:CW) prio=10
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:110)
"Signal dispatcher" (TID:0x41a0c3e0, sys_thread_t:0x81040e0,
state:CW) prio=5
"main" (TID:0x41a0c1e0, sys_thread_t:0x804cf00, state:R) prio=5
at sun.awt.motif.MToolkit.loadSystemColors(Native Method)
at java.awt.SystemColor.updateSystemColors(SystemColor.java:342)
at java.awt.SystemColor.<clinit>
(SystemColor.java:335)
at sun.awt.motif.MFramePeer.<init>
(MFramePeer.java:164)
at sun.awt.motif.MToolkit.createFrame(MToolkit.java:140)
at
com.borland.jbuilder.designer.toolkit.LMToolkit.createFrame(LMToolkit.java:51)
at java.awt.Frame.addNotify(Frame.java:270)
at
javax.swing.plaf.metal.BumpBuffer.createComponent(MetalBumps.java:233)
at javax.swing.plaf.metal.BumpBuffer.<init>
(MetalBumps.java:147)
at javax.swing.plaf.metal.MetalBumps.createBuffer(MetalBumps.java:61)
at javax.swing.plaf.metal.MetalBumps.setBumpColors(MetalBumps.java:96)
at javax.swing.plaf.metal.MetalBumps.<init>
(MetalBumps.java:53)
at
javax.swing.plaf.metal.MetalBorders$ToolBarBorder.<init>
(MetalBorders.java:277)
at
javax.swing.plaf.metal.MetalLookAndFeel.initComponentDefaults(MetalLookAndFeel.java:372)
at
javax.swing.plaf.basic.BasicLookAndFeel.getDefaults(BasicLookAndFeel.java:61)
at
javax.swing.plaf.metal.MetalLookAndFeel.getDefaults(MetalLookAndFeel.java:710)
at javax.swing.UIManager.setLookAndFeel(UIManager.java:359)
at javax.swing.UIManager.setLookAndFeel(UIManager.java:386)
at javax.swing.UIManager.initializeDefaultLAF(UIManager.java:846)
at javax.swing.UIManager.initialize(UIManager.java:922)
at javax.swing.UIManager.maybeInitialize(UIManager.java:944)
at javax.swing.UIManager.getLookAndFeel(UIManager.java:329)
at
com.borland.dbswing.IntlSwingSupport.localizeEnvironment(IntlSwingSupport.java:85)
at
com.borland.dbswing.IntlSwingSupport.setLocale(IntlSwingSupport.java:91)
at
com.borland.dbswing.IntlSwingSupport.<init>
(IntlSwingSupport.java:70)
at
com.borland.dbswing.IntlSwingSupport.<init>
(IntlSwingSupport.java:58)
at com.borland.jbuilder.IntlSwing.localizeSwingResources(Unknown
Source)
at com.borland.jbuilder.IntlSwing.initOpenTool(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at com.borland.primetime.PrimeTime.b(Unknown Source)
at com.borland.primetime.PrimeTime.initializeOpenTools(Unknown Source)
at com.borland.jbuilder.z.invokeCommand(Unknown Source)
at com.borland.primetime.PrimeTime.a(Unknown Source)
at com.borland.primetime.PrimeTime.start(Unknown Source)
at com.borland.jbuilder.JBuilder.main(Unknown Source)
Monitor Cache Dump:
java.lang.Class@41ABCC30/42060A88: owner "main" (0x804cf00) 1 entry
java.lang.ref.ReferenceQueue$Lock@41A0C338/41BA8690: <unowned>
Waiting to be notified:
"Finalizer" (0x810ace8)
java.lang.Class@41A65310/41D9F600: owner "main" (0x804cf00) 1 entry
java.lang.ref.Reference$Lock@41A0C3C0/41BA8188: <unowned>
Waiting to be notified:
"Reference Handler" (0x8105f98)
java.awt.EventQueue@41AF4DA8/41EAE338: <unowned>
Waiting to be notified:
"AWT-EventQueue-0" (0x84400a0)
java.awt.Component$AWTTreeLock@41AE48C8/41F9A588: owner "main"
(0x804cf00) 1 entry
java.lang.Object@41AD6320/420321B8: owner "main" (0x804cf00) 1
entry
Registered Monitor Dump:
utf8 hash table: <unowned>
JNI pinning lock: <unowned>
JNI global reference lock: <unowned>
BinClass lock: <unowned>
Class linking lock: <unowned>
System class loader lock: <unowned>
Code rewrite lock: <unowned>
Heap lock: <unowned>
Monitor cache lock: owner "main" (0x804cf00) 1 entry
Dynamic loading lock: <unowned>
Monitor IO lock: <unowned>
User signal monitor: <unowned>
Waiting to be notified:
"Signal dispatcher" (0x81040e0)
Child death monitor: <unowned>
I/O monitor: <unowned>
Alarm monitor: <unowned>
Waiting to be notified:
<unknown thread>
(0x8058368)
Thread queue lock: owner "main" (0x804cf00) 1 entry
Monitor registry: owner "main" (0x804cf00) 1 entry
Now, the weird part is if I first open a terminal screen (here I am using gnome-terminal version 1.2.0), and at the command prompt type startJBuilder, the program starts normally -- i.e., I end up in the JBuilder environment and I can do my thing. Here is a copy of the testlog file created when I run from an open terminal screen:
Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific] Font specified in font.properties not found [--symbol-medium-r-normal---%d---p--adobe-fontspecific]
JBuilder 3.5 Foundation Copyright (c) 1996-2000 Inprise Corporation. All rights reserved.
And that's it -- JBuilder starts and runs just peachy.
Frankly, I'm at a loss here and would appreciate any assistance, help, or ideas y'all can come up with. I can run my Java applications, but it's just not as convenient. I haven't run into any other programs with this particular problem: Netscape 4.73, StarOffice 5.1, PGAccess, JPilot, TheGimp, TK_Seti, WordPerfect, CBB, AcrossLite, XPenguins, etc. I have just encountered this with Java-based applications. (I am stressing the word 'application' here as I am NOT doing anything with applets.)
Let me know if there's any other information I can supply -- I am not getting core files out of this (at least that I've been able to find).
Thanks.
Joe Sokolosky joework@home.com
------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-27 15:17 ------- This bug was previously known as bug 13156 at http://bugs.gnome.org/ http://bugs.gnome.org/show_bug.cgi?id=13156 Originally filed under the gnome-core product and gnome-terminal component.
The original reporter (joework@home.com) of this bug does not have an account here. Reassigning to the exporter, debbugs-export@bugzilla.gnome.org. Reassigning to the default owner of the component, gnome-core-maint@bugzilla.gnome.org.
Version: 1.2.x
Resolution: RESOLVED DUPLICATE