Bug 492258 - Preferences and Project Properties not responding to selections
Summary: Preferences and Project Properties not responding to selections
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.5.2   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: 4.6 M7   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2016-04-22 10:53 EDT by Antoun Kanawati CLA
Modified: 2016-05-03 15:01 EDT (History)
4 users (show)

See Also:

Attachments
Screen shot (107.05 KB, image/png)
2016-04-22 10:53 EDT, Antoun Kanawati CLA 		no flags Details
View All 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 Antoun Kanawati CLA 2016-04-22 10:53:38 EDT 
Created attachment 261176 [details]
Screen shot

After upgrading to ubuntu 16.04, Eclipse Preferences and Project Properties would not move from the "Resource" display.

Screen shot attached.

PS: Using SWT_GTK3=0 causes crashes, filing separately.
Comment 1 Brian de Alwis CLA 2016-04-25 11:30:59 EDT 
Can you try reproducing with a Neon build?  There are many GTK3 bugs that have been fixed there:

   https://www.eclipse.org/downloads/index-developer.php
Comment 2 Antoun Kanawati CLA 2016-04-26 10:56:11 EDT 
I have re-installed 16.04 from scratch.  No issues.  This may be some artifact of my particular upgrade combination of packages.

I will have to do some work to bring up the old environment, and attempt a repro.
Comment 3 Michael Vorburger CLA 2016-05-02 11:00:26 EDT 
FYI I can reproduce this one as well, on the environment described in my new bug 492829 (which is about another problem).  As stated there, if reproducing and trying out fixes helps, I'm happy to contribute in that form.
Comment 4 Michael Vorburger CLA 2016-05-02 11:57:03 EDT 
FYI I was able to verify that this is fixed in very latest Eclipse 4.6 Neon (at least M7, possibly earlier).  Thus OK to close this as... RESOLVED WORKSFORME ?