JDK-8027541 : Fully transparent jframe becomes black.
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 8
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: linux
  • CPU: generic
  • Submitted: 2013-10-30
  • Updated: 2015-01-27
  • Resolved: 2013-11-19
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8 b119Fixed
Related Reports
Relates :  
Relates :  
Description
After calling jframe.setBackground(new Color(255, 0, 0, 0)), jframe becomes black.

JDK/JRE tested: 1.8.0_b112 (32/64 bits)
OS/architecture: Ubuntu 12.04, Intel
Reproducible: Always.
Is it a Regression: Yes, works correctly with b01, and fail with b60 (regression somewhere between these builds)
Is it a platform specific issue: Yes

Does not reproducible with 7.

To reproduce use attached file.
Comments
Release team: Approved for fixing
19-11-2013

8-critical-request justification: There is no workaround for this bug. The fix is available and has been reviewed (http://mail.openjdk.java.net/pipermail/2d-dev/2013-November/003922.html) The fix is small, low risk, and contained within the affected product area. Fixing this will improve the SQE test coverage pass rate.
18-11-2013

This is not a driver problem. Its a bug in our code where we incorrectly create a surface without alpha even though an alpha colour is specified.
18-11-2013

Good point. So before patching X11 we should try to reproduce this on (eg) 13.04 with & without the alpha fix as it may be a generic issue, not a driver bug. So is this a new test or is this one of the tests that previously were reported to fail because of the alpha bug ?
01-11-2013

Bug is reproducible with enabled xrender, but test works correctly with disabled xrender uname -a : Linux 3.5.0-42-generic #65~precise1-Ubuntu SMP Wed Oct 2 20:57:18 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
01-11-2013

Note that 8023098 which is related to the alpha composite is not integrated to the master.
01-11-2013

Is this a fresh install based on 12.04.03 ? And what does /etc/release or /etc/ubuntu-release show ? Maybe the kernel was upgraded but not the x-stack. What is the X11 version as shown by xdpyinfo ? Does upgrading X via 'sudo apt-get install xserver-xorg-lts-quantal' fix it ? For more info on that look here and follow links as desired .. http://askubuntu.com/questions/257617/how-can-i-upgrade-the-ubuntu-12-04-2-kernel-to-3-5-0-23
01-11-2013

Please explicitly test with -Dsun.java2d.xrender=false (note lower case) and -Dsun.java2d.xrender=True (note upper case). I'm asking because we should not be using xrender on 12.04 since b112 so I can't reconcile the different data being reported here. Please include the kernel version (uname -a) in the update.
31-10-2013

The bug was reassigned to Phil, because all related fixes are in 2d-team repo.
31-10-2013

these fixes were not integrated to b114, wait b116.
31-10-2013

Bug is reproducible with new build.
31-10-2013

build b114 has been promoted, please retest
31-10-2013

There are a few fixes in xrender area, which were pushed recently, we should wait b114 to retest.
30-10-2013

is it critical one?
30-10-2013

Same issue with shapped frames
30-10-2013