Community
Participate
Working Groups
java.lang.NullPointerException at org.eclipse.swt.graphics.Device.<init>(Device.java:129) at org.eclipse.swt.widgets.Display.<init>(Display.java:333) at org.eclipse.swt.widgets.Display.<init>(Display.java:330) at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385) at org.eclipse.core.internal.boot.InternalBootLoader.run (InternalBootLoader.java:775) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462) at java.lang.reflect.Method.invoke(Native Method) at org.eclipse.core.launcher.Main.basicRun(Main.java:247) at org.eclipse.core.launcher.Main.run(Main.java:703) at org.eclipse.core.launcher.Main.main(Main.java:539)
Please provide steps to reproduce this problem.
this exception occurs during startup - so there aren't really any steps. I just run "eclipse" on the command line and see the stack trace provided on initial bug report. This is on a sun ultra-1 machine.
Moving to SWT for comment.
GG to fix.
This has been reported before. It's a problem with determining your system font, which is taken to be the font of a motif Label. The inability to determine this indicates a font path setup problem on your end. See http://dev.eclipse.org/bugs/show_bug.cgi?id=19209 . Changing the report title to reflect the specific problem. We should either handle this case better or FAQ it.
Eduard This should not happen on startup anymore (builds > 20021031), but it can still happen any time getFontData() is called on a system font that is not a complete XLFD. Please could you run the attached java class (next) and add the output to this bug? We are not able to reproduce this problem and I want to gather more info. Thanks! Silenio
Created attachment 2294 [details] java class that outputs system font
Edward, any update? Can we close this PR?
Edward, I am going to change the severity of this bug report from blocking to major since the problem no onger occurs on startup. Please let us know if you are still experiencing the problem and if you have been able to run Silenio's test case. Thank you.
Marking as duplicate since we are able to reproduce this problem using the locale of the other report. *** This bug has been marked as a duplicate of 35657 ***