There seems to be an incompatibility between Eclipse-3.5.1 and GTK that ships with Fedora 12 Often buttons don't react on mouse click. When the botton is highlighted,hitting enter however works. Code: $ yum list installed | grep gtk2 gtk2.i686 2.18.3-21.fc12 @updates gtk2-engines.i686 2.18.4-4.fc12 @rawhide gtk2-immodule-xim.i686 2.18.3-21.fc12 @updates libcanberra-gtk2.i686 0.22-1.fc12 @rawhide pygtk2.i686 2.16.0-1.fc12 @rawhide pygtk2-libglade.i686 2.16.0-1.fc12 @rawhide Various other posts in eclipse bugzilla point out that there might be an incompatibility with gtk-2.17.x and above This issue seems to be fixed in eclipse-3.6M3 http://download.eclipse.org/eclipse/downloads/
For me it's a SELinux problem. Look in your logs and if it's there, follow the instructions to enable the libraries that comes with eclipse.
Are you using Eclipse from Fedora RPM? Or upstream download?
I have the same issue, it is with upstream download, and also with JBDS.
I used eclipse-3.5.1 from the eclipse download page. The same that worked for me on Fedora 11.
The problem is due to the way SWT makes some assumptions about gtk behavior. It is fixed in Fedora's Eclipse. Please either use Fedora's Eclipse or make a wrapper script with export GDK_NATIVE_WINDOWS=true to launch your download. There is nothing more that can be done on the Fedora's site.
Sorry, didn't read properly. Please disregard my comment. No problem with buttons in upstream eclipse and f12 though.
Experienced the problem now in f12 x86_64. Workaround from comment #5 works for me.
Hi All, I was experiencing issue when the eclipse directory was writeable by my user, along with little red icons in place of most of the eclipse icons, hence discovering this bug. Removing write permissions seemed to fix it; not sure why. Now not experiencing this issue, although I did chcon -t bin_t on eclipse and chcon -t lib_t on libcairo-swt.so in the /opt/eclipse folder. Also did a yum install eclipse-swt (SWT library for GTK) which wasn't installed by default. I don't have fedora-eclipse or any related packages installed other than eclipse-swt. Eclipse Version: 3.5.1.R35x_v20090811-9SA0FxVFqE70OL1ARMrfcO6e7BA6 Build id: M20090917-0800 uname -r: 2.6.31.6-166.fc12.x86_64 Might help, might not, thought it was worth sharing though.
Can also confirm that the work around in comment #5 fixes this issue for me, too.
This was clearly Eclipse/SWT problem and it has been fixed in both upstream 3.6 release and our packages. Closing.