Community
Participate
Working Groups
Bugzilla – Bug 288909
[Widgets][GTK2.18] No toolbars in Console and Search View in GTK 2.17.x
Last modified: 2010-01-18 14:15:10 EST
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-3.1 Firefox/3.5.2 Build Identifier: I20090611-1540 Launching Eclipse in KDE 4.3.1 on OpenSUSE 11.2 Factory Milestone 6+, configuration see below: Very often I do not get the toolbar in the Console and Search View, but only a white space in that place, which doesn't respond on mouse clicks. These toolbars worked without problems in Eclipse 3.4.x and earlier versions. Sometimes restart helps. The kind and number of view concerned by this change sometimes after restarting Eclipse. At the moment I use a VESA graphics driver on an Intel chipset, which is quiet slow, if this plays a role. Please ask for details, if you need some more. -- Configuration Details -- Product: Eclipse 1.2.0.20090619-0620 (org.eclipse.epp.package.java.product) Installed Features: org.eclipse.platform 3.5.0.v20090611a-9gEeG1HFtQcmRThO4O3aR_fqSMvJR2sJ Reproducible: Sometimes *** Platform Details: *** System properties: eclipse.application=org.eclipse.ui.ide.workbench eclipse.buildId=I20090611-1540 eclipse.commands=-os linux -ws gtk -arch x86 -showsplash /home/rkrell/tools/eclipse//plugins/org.eclipse.platform_3.3.200.v200906111540/splash.bmp -launcher /home/rkrell/tools/eclipse/eclipse -name Eclipse --launcher.library /home/rkrell/tools/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.200.v20090520/eclipse_1206.so -startup /home/rkrell/tools/eclipse//plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar -product org.eclipse.epp.package.java.product -data /home/rkrell/workspace -vm /usr/lib/jvm/java-1.6.0-sun-1.6.0/jre/bin/../lib/i386/client/libjvm.so eclipse.home.location=file:/home/rkrell/tools/eclipse/ eclipse.launcher=/home/rkrell/tools/eclipse/eclipse eclipse.p2.data.area=@config.dir/../p2/ eclipse.p2.profile=epp.package.java eclipse.product=org.eclipse.epp.package.java.product eclipse.startTime=1252480634447 eclipse.vm=/usr/lib/jvm/java-1.6.0-sun-1.6.0/jre/bin/../lib/i386/client/libjvm.so eclipse.vmargs=-Dosgi.requiredJavaVersion=1.5 -XX:MaxPermSize=512m -Xms80m -Xmx512m -Djava.class.path=/home/rkrell/tools/eclipse//plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar file.encoding=UTF-8 file.encoding.pkg=sun.io file.separator=/ http.nonProxyHosts=localhost|127.0.0.1 http.proxyHost=proxy http.proxyPort=3128 http.proxySet=true https.nonProxyHosts=localhost|127.0.0.1 https.proxyHost=proxy https.proxyPort=3128 https.proxySet=true java.awt.graphicsenv=sun.awt.X11GraphicsEnvironment java.awt.printerjob=sun.print.PSPrinterJob java.class.path=/home/rkrell/tools/eclipse//plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar java.class.version=50.0 java.endorsed.dirs=/usr/lib/jvm/java-1.6.0-sun-1.6.0/jre/lib/endorsed java.ext.dirs=/usr/lib/jvm/java-1.6.0-sun-1.6.0/jre/lib/ext:/usr/java/packages/lib/ext java.home=/usr/lib/jvm/java-1.6.0-sun-1.6.0/jre java.io.tmpdir=/tmp java.library.path=/usr/lib/jvm/java-1.6.0-sun-1.6.0/jre/lib/i386/client:/usr/lib/jvm/java-1.6.0-sun-1.6.0/jre/lib/i386:/usr/lib/xulrunner-1.9.1.2:/usr/lib/xulrunner-1.9.1.2:/usr/java/packages/lib/i386:/lib:/usr/lib java.runtime.name=Java(TM) SE Runtime Environment java.runtime.version=1.6.0_15-b03 java.specification.name=Java Platform API Specification java.specification.vendor=Sun Microsystems Inc. java.specification.version=1.6 java.vendor=Sun Microsystems Inc. java.vendor.url=http://java.sun.com/ java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi java.version=1.6.0_15 java.vm.info=mixed mode java.vm.name=Java HotSpot(TM) Client VM java.vm.specification.name=Java Virtual Machine Specification java.vm.specification.vendor=Sun Microsystems Inc. java.vm.specification.version=1.0 java.vm.vendor=Sun Microsystems Inc. java.vm.version=14.1-b02 line.separator=
I tried this already with the following JDKs: java-1_5_0-sun-1.5.0_update19 java-1_6_0-sun-1.6.0.u15 java-1_6_0-openjdk-1.6.0.0_b16 The problem is always the same.
Created attachment 146732 [details] Search View example without toolbar (button Next Match etc. not shown)
(In reply to comment #2) > Created an attachment (id=146732) [details] > Search View example without toolbar (button Next Match etc. not shown) You seem to still have the view's menu though (the inverted triangle on the top right). I have seen a screenshot where someone's 'Breakpoints' view was missing the toolbar in its entirety (it wasn't even being drawn).
Created attachment 146739 [details] Console View example without toolbar
(In reply to comment #3) > (In reply to comment #2) > > Created an attachment (id=146732) [details] [details] > > Search View example without toolbar (button Next Match etc. not shown) > > You seem to still have the view's menu though (the inverted triangle on the top > right). I have seen a screenshot where someone's 'Breakpoints' view was missing > the toolbar in its entirety (it wasn't even being drawn). Yes, but incomplete. Addditionally, see my second attachment with the Console View, with the tooolbar totally missing. Are you sure whether the recent assignment of this bug to the Debug component was right? It seems to be a general UI problem IMHO.
(In reply to comment #5) > Are you sure whether the recent assignment of this > bug to the Debug component was right? It seems to be a general UI problem IMHO. I wasn't even aware that it was reassigned (though I do now from looking at this bug's history), I just saw a new bug and clicked on it. Ultimately, I think this is a GTK+ bug/feature/whatever. I've never seen this problem on my Linux notebook. What version of GTK+ are you on? 2.17.7? I guess 2.17.x anyway.
(In reply to comment #6) > (In reply to comment #5) > > Are you sure whether the recent assignment of this > > bug to the Debug component was right? It seems to be a general UI problem IMHO. > > I wasn't even aware that it was reassigned (though I do now from looking at > this bug's history), I just saw a new bug and clicked on it. > > Ultimately, I think this is a GTK+ bug/feature/whatever. I've never seen this > problem on my Linux notebook. What version of GTK+ are you on? 2.17.7? I guess > 2.17.x anyway. I use GTK 2.17.9, right. Anyway, it would be fine to see Eclipse in newer distributions without this bug, again :-) Do you have any recommendations?
Note that Steffen did bring up a toolbar repainting problem in bug 286687 comment 11. Whether that's been fixed or not, I do not know off-hand. (In reply to comment #7) > I use GTK 2.17.9, right. > Anyway, it would be fine to see Eclipse in newer distributions without this > bug, again :-) Do you have any recommendations? I would probably downgrade GTK+ to 2.16.x (or lower).
(In reply to comment #8) > Note that Steffen did bring up a toolbar repainting problem in bug 286687 > comment 11. Whether that's been fixed or not, I do not know off-hand. > > (In reply to comment #7) > > I use GTK 2.17.9, right. > > Anyway, it would be fine to see Eclipse in newer distributions without this > > bug, again :-) Do you have any recommendations? > > I would probably downgrade GTK+ to 2.16.x (or lower). Ok, this might be a workaround, but no solution, of course. Although the GTK is given in most cases and you can't quickly change within a distribution without recompiling many other packages (which are usually pre-compiled). BTW: Even removing the QtCurve style and the appropriate KCM module in KDE (using GKT clear look) doesn't help Does anyone know a similar problem with GTK 2.17.x and different applications?
After compiling and installing GTK 2.16.1 and recompiling gkt2-engines and qtcurve for OpenSUSE 11.2 M6+ I can confirm, that the problem reported here disappears. The reason seems to be definitely in an incompatibility between Eclipse 3.5 and GTK 2.17.x.
... even 2.17.10 did not help solving this for GTK 2.17.x.
(In reply to comment #9) > Ok, this might be a workaround, but no solution, of course. Although the GTK is > given in most cases and you can't quickly change within a distribution without > recompiling many other packages (which are usually pre-compiled). Yes, I figured this would be non-trivial for most major distributions. I use Gentoo myself so it's not a big deal, but anyway, thank you for your investigations, René. SWT, please advise...
We are aware of some big changes in GTK 2.17.x around the way windows are created. I'll see if I can see this with our latest 2.17.11 library.
(In reply to comment #13) > We are aware of some big changes in GTK 2.17.x around the way windows are > created. I'll see if I can see this with our latest 2.17.11 library. For me, this problem ist still present and unchanged in GTK 2.17.11 (openSUSE Factory packages).
(In reply to comment #14) > For me, this problem ist still present and unchanged in GTK 2.17.11 (openSUSE > Factory packages). Same problem here, also I can't switch perspective with a single click anymore, I have to either double-click or keep the mouse pressed a long time. I hope there'll be a Qt version of SWT soon so I can finally fully remove GTK from my system.
(In reply to comment #15) > I hope there'll be a Qt version of SWT soon so I can finally fully remove GTK > from my system. See bug 20486.
Looks like a straight dup of bug 287307
Same Problem OpenSuse 11.2 RC1 Eclipse 3.5 *vote for QT port* ;-)
Reproducable with galileo sr1 on Mandriva 2010.0 RC2 (64 bit). Ganymed seems not to be affected. +1 for a native Qt port :-)
(In reply to comment #19) > Reproducable with galileo sr1 on Mandriva 2010.0 RC2 (64 bit). Ganymed seems > not to be affected. +1 for a native Qt port :-) I was wrong, Ganymed is affected, too.
(In reply to comment #17) > Looks like a straight dup of bug 287307 Yes it seems so. Eclipse 3.6 M2 got this problem already fixed and works fine with GTK 2.17.x an 2.18.x. Hopefully this fix will occur soon in the 3.5 series. Thanks.
BTW, did you try setting the following env var: GDK_NATIVE_WINDOWS=true? Should fix things with 3.5.x in GTK versions greater than 2.17.11.
Bogdan, this bug is probably a duplicate of the Z-order problem that was fixed buy calling the new window restack GDK API. That fix has to be back ported to 3.5.2.
*** Bug 294101 has been marked as a duplicate of this bug. ***
*** Bug 295215 has been marked as a duplicate of this bug. ***
Setting the GDK_NATIVE_WINDOWS=true environment variable worked for me. I'm running on Kubuntu AMD 64 and Ganamede *** System properties: eclipse.application=org.eclipse.ui.ide.workbench eclipse.buildId=M20090917-0800
*** Bug 299879 has been marked as a duplicate of this bug. ***
Closing as duplicate. *** This bug has been marked as a duplicate of bug 287307 ***