Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 912174[details]
IntelliJ Idea bug
Description of problem:
Some Swing based Java application render incorrectly at times under Gnome Shell.
It seems like the component that need repainting doesn't get properly notified. This bug seems to be specific to Swing application and Gnome Shell, I was not able to reproduce this behavior under KDE or by installing Mate for example.
Version-Release number of selected component (if applicable):
* Red Hat Enterprise Linux Workstation release 7.0 (Maipo)
* gnome-shell-3.8.4-32.el7_0.x86_64
* java-1.7.0-openjdk-1.7.0.55-2.4.7.2.el7_0.x86_64
How reproducible:
Unfortunately, I wasn't able to really reproduce this bug consistently, it seems that most Swing based application tend to have some components with broken rendering, but IntelliJ Idea (community edition) seem to have this issue always in the same spot (a popup menu), I attach a screenshot that shows the issues. Other application had similar problems, although not limited to popups.
Non Swing applications (for example Eclipse) don't seem to have this issue, at least for what I can tell. I also wasn't able to reproduce this so far under KDE or other Desktop environments.
All the application I tried were based in some way on a Nimbus Look and Feel (either GTKLookAndFeel, or Nimbus itself). I didn't try any app based on MetalLookAndFeel.
Steps to Reproduce:
1. Start IntelliJ (for example, other Swing based application may work).
2. Click around, perhaps using autocompletition on a method to fire up the popup
3. Move the mouse over the method lists and see the issue (it may need some tries)
Actual results:
The popup is rendered incorrectly
Expected results:
Popup should be rendered correctly
Additional info:
I tried with various Java2D pipelines. I don't think this is a Java bug, but it maybe something related by the Gnome Shell *and* Java. AWT seems to notify the damaged area correctly though, although I wasn't yet able to isolate the issue with a smaller reproducer to be certain.
Comment 2George N. White III
2014-10-16 15:41:48 UTC
I have also encountered inconsistent problems using Scientific Linux 7 with rendering in a swing-based Java application (NASA SeaDAS 7.1) using Oracle Java 1.7 and 1.8. In some cases there were Java exceptions rendering jpeg or png images that seemed to be related to redrawing buttons in the empty gray box.
Today I tried running the application after doing "export _JAVA_AWT_WM_NONREPARENTING=1". Since this I have not yet encountered the problem. As the reporter mentions, this feels like a miscommunication between
Gnome Shell *and* Java.
Created attachment 912174 [details] IntelliJ Idea bug Description of problem: Some Swing based Java application render incorrectly at times under Gnome Shell. It seems like the component that need repainting doesn't get properly notified. This bug seems to be specific to Swing application and Gnome Shell, I was not able to reproduce this behavior under KDE or by installing Mate for example. Version-Release number of selected component (if applicable): * Red Hat Enterprise Linux Workstation release 7.0 (Maipo) * gnome-shell-3.8.4-32.el7_0.x86_64 * java-1.7.0-openjdk-1.7.0.55-2.4.7.2.el7_0.x86_64 How reproducible: Unfortunately, I wasn't able to really reproduce this bug consistently, it seems that most Swing based application tend to have some components with broken rendering, but IntelliJ Idea (community edition) seem to have this issue always in the same spot (a popup menu), I attach a screenshot that shows the issues. Other application had similar problems, although not limited to popups. Non Swing applications (for example Eclipse) don't seem to have this issue, at least for what I can tell. I also wasn't able to reproduce this so far under KDE or other Desktop environments. All the application I tried were based in some way on a Nimbus Look and Feel (either GTKLookAndFeel, or Nimbus itself). I didn't try any app based on MetalLookAndFeel. Steps to Reproduce: 1. Start IntelliJ (for example, other Swing based application may work). 2. Click around, perhaps using autocompletition on a method to fire up the popup 3. Move the mouse over the method lists and see the issue (it may need some tries) Actual results: The popup is rendered incorrectly Expected results: Popup should be rendered correctly Additional info: I tried with various Java2D pipelines. I don't think this is a Java bug, but it maybe something related by the Gnome Shell *and* Java. AWT seems to notify the damaged area correctly though, although I wasn't yet able to isolate the issue with a smaller reproducer to be certain.