FS#60314 - [jre8-openjdk] UIManager.getSystemLookAndFeelClassName() doesn't return GTKLookAndFeel
Attached to Project:
Arch Linux
Opened by Peter Weber (hoschi) - Friday, 05 October 2018, 08:17 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 20 September 2023, 03:19 GMT
Opened by Peter Weber (hoschi) - Friday, 05 October 2018, 08:17 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 20 September 2023, 03:19 GMT
|
Details
Description:
Hello! When running a GNOME based environment, the static method UIManager.getSystemLookAndFeelClassName() shall return "GTKLookAndFeel", but it seems to fallback to MotifLookAndFeel. I noticed this issue in NetBeans, as well as in my own Java based applications. Additional info: * package version(s): 8.u181-1 * workaround: set property with option -D i.e. -Dswing.crossplatformlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel example: java -Dswing.crossplatformlaf=com.sun.java.swing.plaf.gtk.GTKLookAndFeel -jar foo.jar * workaround: set explicit LookAndFeel in program options, if possible * one of this conditions fails, but '-g' option wasn't used to compile the JRE: if ("gnome".equals(desktop) && toolkit instanceof SunToolkit && ((SunToolkit) toolkit).isNativeGTKAvailable()) { ... } Steps to reproduce: 1.) launch application written in Java on GNOME 2.) when it defaults to native look and not an explicit look, it will load MotifLookAndFeel Thank you PS: It not necessarily a bug in JRE, maybe a change in GNOME or some other side-effect. |
This task depends upon
Closed by Toolybird (Toolybird)
Wednesday, 20 September 2023, 03:19 GMT
Reason for closing: Upstream
Additional comments about closing: This looks pretty old and stale. If still happening, please report upstream because it doesn't appear to be an Arch packaging issue.
Wednesday, 20 September 2023, 03:19 GMT
Reason for closing: Upstream
Additional comments about closing: This looks pretty old and stale. If still happening, please report upstream because it doesn't appear to be an Arch packaging issue.
Comment by Peter Weber (hoschi) -
Friday, 05 October 2018, 08:18 GMT
Replace 'shall' by 'should', it's not a must.
Comment by
Buggy McBugFace (bugbot) - Tuesday,
08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2
years. Please reply if you still experience this bug otherwise
this issue will be closed after 1 month.