You are not logged in.
What GTK3 themes are you guys running?
Offline
I was using the oxygen-gtk3 theme. Now I use oxygen-gtk2 and it works fine.
Offline
Is it any different with the stock GTK3 theme?
Offline
Well, I don't know. I use a KDE desktop environment (I recently switched from KDE4 to Plasma5) and oxygen-gtk2/3 let me have a consistent look and feel for GTK applications. Newer GTK3 versions have some issues with C++ themes and the developers recommend using CSS, see https://bbs.archlinux.org/viewtopic.php … 8#p1546908. I think that this might be the problem, which could affect not only oxygen-gtk but all the C++ themes.
Offline
I saw in a thread that the gtk3 orion theme might work.
I know nothing about gtk3 theming but it seems to be a default theme.
https://bbs.archlinux.org/viewtopic.php?id=195960
Last edited by authentec (2015-10-29 19:05:49)
Offline
I hope this will be fixed. Downgrading eclipse and jdk didn't help in my case.
EDIT: GTK is ok, but speed is extremely slow.
Last edited by mirko28 (2015-10-31 23:22:00)
Offline
--launcher.GTK_version
2
This worked for me too.
Before knowing this fix I discovered that adding a console window helps too (so that eclipse uses the one half of the screen and the console window the other, splitted verticaly).
Last edited by zeilenleser (2015-11-13 16:09:07)
Offline
This workaround made a huge difference for me, but Mars still runs a lot slower than Luna.
I downgraded again.
Offline
After updating Eclipse from Luna to Mars, I have the same problem (LXDE, jdk8-openjdk, gtk2 2.24.28, gtk3 3.18.2). By forcing Eclipse to use GTK2 instead of GTK3 everything works: Add the following two lines before --launcher.appendVmargs in file /usr/lib/eclipse/eclipse.ini
--launcher.GTK_version 2
This workaround comes from Eclipse GUI broken.
This did the trick for me too... thanks!
Offline
Hi,
I tried gtk2 workaround, which didn't work for me. Change to Orion theme (using lxappearance) made it snappy enough, at least for now.
Before I had numix gtk3 theme... and am using openbox.
And it was in practice unusable before.
Last edited by aparaatti (2015-11-24 20:19:00)
Offline
Hello,
I am proudly using arch linux since two days and now I got a big problem. I installed jdk8-opnjdk in order to use Eclipse. Everything seemed to work fine. But when I try to do simple tasks like creating a Project oder building or setting preferences, eclipse is progressing something, and seem to hang. There is a progress indicator in the right corner, which won't stop. All in all I can't use eclipse. I removed the open jdk and installed the oracle jdk an re-installed eclipse. Nothing changed.btw: I'm using a Thinkpad x61s with 4gb ram.
Thank you very much for your help, I really need to use this IDE.
run eclipse like this:
SWT_GTK3=0 eclipse
Offline
The best fix is to of course shutt down Eclipse, than open terminal, and type emacs& , This solution fixes problem on my computer & runs magnitudes faster than any stock implementation fo Eclipse I have ever tryed .
Last edited by memory_leak (2015-12-28 20:43:48)
Offline
Can confirm that memory_leak's fix worked for me, but note that depending on your setup you may need to first run
alias emacs=vim
that's what worked for me at least.
Last edited by TheGuyWithTheFace (2015-12-28 20:48:17)
Offline
Can confirm that memory_leak's fix worked for me, but note that depending on your setup you may need to first run
alias emacs=vim
that's what worked for me at least.
Note to myself: I won't bite on this one :-).
Offline
Does anyone know what the difference is (if any) between setting "SWT_GTK3=0" in the environment and using "--launcher.GTK_version 2" in eclipse.ini?
Offline
I'd assume other SWT using programs will use GTK2 as well with the environment set while the other is eclipse launcher specific (can't name one on the top of my head, Azureus maybe?)
Last edited by V1del (2016-01-05 15:18:11)
Offline
Just wanna mention that
with gnome 3.20
1) the solution
--launcher.GTK_version 2
now produces bad behaviour (members in ctrl + o are now white on white),
2) using Eclipse with GTK 3 is still a pain.
Anyone has a fix for 1)?
Offline
@yupi: there is a upstream bug for the "white on white" problem (https://bugs.eclipse.org/bugs/show_bug.cgi?id=487687)
In my case though, I don't have white on white while running GTK 2? That bug report suggests it was white on white for GTK 3?
Interestingly enough, that bug was fixed for 4.5.2 running on GTK 3. However, in my case running 4.5.2 on GTK 3 is still buggy.
Offline
Just wanna mention that
with gnome 3.201) the solution
--launcher.GTK_version 2
now produces bad behaviour (members in ctrl + o are now white on white),2) using Eclipse with GTK 3 is still a pain.
Anyone has a fix for 1)?
@yupi: there is a upstream bug for the "white on white" problem (https://bugs.eclipse.org/bugs/show_bug.cgi?id=487687)
In my case though, I don't have white on white while running GTK 2? That bug report suggests it was white on white for GTK 3?
Interestingly enough, that bug was fixed for 4.5.2 running on GTK 3. However, in my case running 4.5.2 on GTK 3 is still buggy.
I'm getting the "white on white" issue in "Ctrl+O" using the GTK 2 workaround.
Does anyone know if there has been any progress on getting GTK 3 to work properly with Eclipse?
It's been over 6 months since this thread was started.
Offline
Does anyone know if there has been any progress on getting GTK 3 to work properly with Eclipse?
It's been over 6 months since this thread was started.
Eclipse Neon will be out this month. Have you tried Neon to see if GTK3 works with the RC?
Offline
alexdw wrote:Does anyone know if there has been any progress on getting GTK 3 to work properly with Eclipse?
It's been over 6 months since this thread was started.Eclipse Neon will be out this month. Have you tried Neon to see if GTK3 works with the RC?
Neon seems to be still broken with GTK 3.20.
Offline
twelveeighty wrote:alexdw wrote:Does anyone know if there has been any progress on getting GTK 3 to work properly with Eclipse?
It's been over 6 months since this thread was started.Eclipse Neon will be out this month. Have you tried Neon to see if GTK3 works with the RC?
Neon seems to be still broken with GTK 3.20.
Eclipse Neon still not working with GTK 3 for me, but the Ctrl-O background issue appears to have been fixed, so the previous workaround works well again.
Offline
Having the same problem. Also
--launcher.GTK_version
2
did not work for me. It's even worse. I'm running Jee version of eclipse frome the Arch repository. I run Xfce as my window manager...
Offline
did not work for me. It's even worse. I'm running Jee version of eclipse frome the Arch repository. I run Xfce as my window manager...
I'm running the eclipse-jee-neon-R-linux-gtk-x86_64.tar.gz version straight from the website with Sun JDK 8, using "--launcher.GTK_version 2" in eclipse.ini and that works fine in terms of UI responsiveness. I have noticed insane CPU usage after opening projects that use large jars (80MB) as libraries, which I think is new? But the UI itself does work with GTK 2. GTK 3 is better than on Mars, but significantly slower than on GTK 2.
Offline
michael_e wrote:did not work for me. It's even worse. I'm running Jee version of eclipse frome the Arch repository. I run Xfce as my window manager...
I'm running the eclipse-jee-neon-R-linux-gtk-x86_64.tar.gz version straight from the website with Sun JDK 8, using "--launcher.GTK_version 2" in eclipse.ini and that works fine in terms of UI responsiveness. I have noticed insane CPU usage after opening projects that use large jars (80MB) as libraries, which I think is new? But the UI itself does work with GTK 2. GTK 3 is better than on Mars, but significantly slower than on GTK 2.
Thank I will give this a try... however I today started eclipse everything runs fine with GTK3. I installed compiz before and emerald and played around with it a bit but finally decided to uninstall it again. During that I switch between
xfwm4 and compiz a few times with
xfwm4 --replace
and
compiz --replace
because I managed to break everything with compiz so the system was barely usable. I don't know if the switching between
the window managers did the job (I think not but wanted to mention it).
Furthermore I installed the nvidia propr. drivers from the Arch repo. Maybe that did the job. Just wanted to share this; unfortunately I was not able to recreate the unresponsiveness in eclipse so I cannot give you guys a clear hint...
Offline