| Summary: | white screen at java application startup | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | csenkal |
| Component: | mutter | Assignee: | Florian Müllner <fmuellner> |
| Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | tpelka |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-01-15 07:28:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
csenkal
2016-11-22 13:27:23 UTC
(In reply to csenkal from comment #0) > This problem just occurs on redhat 7.2 and 7.3 version not 7.1 version. All RHEL 7.x versions use mutter/gnome-shell by default - are you sure your system is using metacity, or should we reassign the issue to mutter? (In reply to Florian Müllner from comment #1) > (In reply to csenkal from comment #0) > > This problem just occurs on redhat 7.2 and 7.3 version not 7.1 version. > > All RHEL 7.x versions use mutter/gnome-shell by default - are you sure your > system is using metacity, or should we reassign the issue to mutter? You are right, I have changed component to mutter To be more precise and spesific: Java version is 1.8_0_92 64 bit. The problem can be reproduced with any undecorated JFrame. The contents of the JFrame is not displayed. Only gray background is displayed. When frame is maximized contents are painted and displayed. After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |