-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
P3
-
Affects Version/s: 9
-
Component/s: client-libs
-
Environment:
Ubuntu 16.04 Unity, dual-screen
This test is for a fix in b127 and it does pass with that build and 128, 129 as well -- but with b130 and later it fails on both my dual screen Ubuntu 16.04 systems with
java.awt.IllegalComponentStateException: component must be showing on the screen to determine its location
at java.awt.Component.getLocationOnScreen_NoTreeLock(java.desktop@9-ea/Component.java:2079)
at java.awt.Component.getLocationOnScreen(java.desktop@9-ea/Component.java:2053)
at CloseOnMouseClickPropertyTest.lambda$getClickPoint$2(CloseOnMouseClickPropertyTest.java:143)
Indeed, there's some painting problem. A component (this time a JMenuItem) is not visible on the screen.
Looks like it is the same issue asJDK-8164462.
java.awt.IllegalComponentStateException: component must be showing on the screen to determine its location
at java.awt.Component.getLocationOnScreen_NoTreeLock(java.desktop@9-ea/Component.java:2079)
at java.awt.Component.getLocationOnScreen(java.desktop@9-ea/Component.java:2053)
at CloseOnMouseClickPropertyTest.lambda$getClickPoint$2(CloseOnMouseClickPropertyTest.java:143)
Indeed, there's some painting problem. A component (this time a JMenuItem) is not visible on the screen.
Looks like it is the same issue as
- duplicates
-
JDK-8161910 [PIT] regression: HW/LW mixing seems broken on Unity
-
- Resolved
-
- relates to
-
JDK-8164462 Repainting issue on Linux
-
- Closed
-