Bug 429640 - White content of all Views
Summary: White content of all Views
Status: CLOSED DUPLICATE of bug 421127
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.4   Edit
Hardware: PC Linux
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-05 04:06 EST by Karsten Schulz CLA
Modified: 2014-03-05 05:06 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karsten Schulz CLA 2014-03-05 04:06:47 EST 
Hi,

i test the new eclipse development builds at irregular intervals. Yesterday i download the current java bundle of eclipse. At the first start up i saw a several problem. All content of the Views (Editor, Outline, Package Explorer, etc.) is not available, or not visible. I changed the theme at Window -> Preferences -> General -> Appearance and i saw my projects in the Package Explorer. After i expand the Project these was invisible again.

Maybe the reason for the problem is the Linux Version (14.04 Kubuntu and Ubuntu) but with version 4.3.2 i don't have this problems on this Linux versions. I test eclipse 4.4 M5 on Ubuntu 12.04 LTS too, and the issue is not existing.

Maybe you can fixed this issue. If not, i will skip eclipse 4.4.
Comment 1 Thomas Schindl CLA 2014-03-05 04:14:02 EST 
Most likely an issue with gtk3, can you try launching with SWT_GTK3=0
Comment 2 Karsten Schulz CLA 2014-03-05 04:53:06 EST 
Ok, with SWT_GTK3=0 as environment variable works fine. Have someone a Launchpad account to notify the gtk3 developers for this issue? If not already done
Comment 3 Thomas Schindl CLA 2014-03-05 04:54:46 EST 
it's not a problem of the GTK3 but the one from the SWT implementation
Comment 4 Arun Thondapu CLA 2014-03-05 05:06:01 EST 
This is a problem with Eclipse/SWT on GTK 3.10. Please try the latest I-builds, there is a workaround available and you should not see this bug now.

*** This bug has been marked as a duplicate of bug 421127 ***