You are not logged in.
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.
Offline
I installed Luna via the eclipse installer. That solved the problem for now. Thanks anyway
Offline
Same for me. I see one of the CPU cores continuously at 100%. Eclipse freezes with almost any action (for instance trying to delete a file from within Eclipse, or trying to compile and run a Java program), and I have to kill it.
The previous version was working fine.
Last edited by rokidakota (2015-10-11 12:21:18)
Offline
Hi, I hate to say "mee too" but... mee too. I waited for 4.5.1 since I had great problems with eclipse-cpp 4.5.0: super-laggy UI with a broken look in KDE, indexer which failed at indexing my projects, plugins which stopped working etc. Today I tried 4.51 and I see that things improved a lot, but Mars is still a brick compared to Luna. Launching a debug session requires ages, the build console update is very slow and the launch process seems to get stuck until I do some manual action like changing perspective.
I'm rolling back to Luna again since I need Eclipse at work, but it seems that we have a problem. It seems that on the web there are not many reports about such problems with Mars, so maybe it is the ArchLinux packaging that is somewhat broken? It seems impossible to me that heftig pushed such a broke version of Eclipse into the official repo, so I guess that at least for him Mars was working fine. It looks then more like a configuration/environment problem: maybe it is due to integration with KDE/Qt? Which desktop environment do you use?
Offline
I have reported another sort of problem on this forum with eclipse-cpp 4.5.1. Version 4.5.0 of eclipse-cpp seems to work good enough though.
bing different
Offline
I'm using i3wm.
I try to revert the package to 4.4.2, but I don't know what to answer to
:: eclipse and eclipse-java are in conflict. Remove eclipse-java? [y/N] ^C
Offline
I'm using i3wm.
I try to revert the package to 4.4.2, but I don't know what to answer to
:: eclipse and eclipse-java are in conflict. Remove eclipse-java? [y/N] ^C
Say Y, eclipse 4.4.2 provides the java development environment, like eclipse-common + eclipse-java for 4.5.x
Offline
Say Y, eclipse 4.4.2 provides the java development environment, like eclipse-common + eclipse-java for 4.5.x
Thanks! To avoid existing-file conflicts I had to first uninstall both new packages, and then install 4.4.2.
Offline
I experienced this issue as well, reverted back to 4.4.2 and everything was fine.
Offline
I've been running this in an Arch VMWare machine and haven't seen anything like this.
Offline
IMBJR, could you share some details about your system? Which desktop environment did you use? Did you use Mars for Java development or c++?
Offline
IMBJR, could you share some details about your system? Which desktop environment did you use? Did you use Mars for Java development or c++?
XFCE and it was Java with glassfish.
Offline
I'm beginning to suspect that the real issue is with eclipse-cpp. In fact, most of my problems are related to c++ activities like code indexing and debug sessions. Is anyone else experiencing problems with Java, or really everybody having troubles are working with eclipae-cpp?
Offline
I had the same problem, using eclipse-java on i3 wm. Downgrading to the 4.4.2 version from the backup server helped.
http://ala.seblu.net/packages/e/eclipse/
I never had eclipse-cpp installed.
Last edited by PhilippD (2015-10-19 10:59:54)
Offline
I confirm that with parte.1 eclipse is impossible to work in debug then really slow. Use jre8 oracle and I use it only for java development packages without c ++
Offline
mars.1...
Offline
Yeah, I'm also about to downgrade to Luna.
Eclipse Mars.1 is basically unusable for me because it's so slow.
Debugging is impossible and that's something I usually want to use Eclipse for.
Forget about using the "refactor" feature or even starting a build from eclipse. Too slow.
I'm using eclipse-cpp and the Xfce desktop.
EDIT: Had to downgrade to 4.4.1 and CDT 8.7 (this is before eclipse-common, eclipse-cpp etc) to get better performane.
Eclipse-4.4.2 is very fast. No issues there.
But now indexing is completely broken and it has underlined almost every single type or function.
This might be because I didn't have a workspace backup and Luna is having issues with the Mars version.
I'll have to use Vim and get used to another debugger while Eclipse Mars is broken.
Last edited by authentec (2015-10-24 14:37:51)
Offline
I was thinking about opening a bug in the Eclipse bug tracker, but I feel that I don't understand the issue enough to write a meaningful report since I played with Mars just a bit before reverting to Luna, since I need Eclipse at work. Is there anyone who can afford staying on Mars and providing testing and feedback to the developers which is willing to file a bug report? Thanks.
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.
Offline
Thanks, that did the trick.
I also have a sensible selection color again.
Offline
It works also for me. By the way, if one does not want to modify eclipse.ini then GTK2 can be forced also from command line:
$ eclipse --launcher.GTK_version 2 &
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.
Thanks for posting - this appears to have fixed the issues I was having with Eclipse Mars.1 as well (mostly with the EGit plugin).
Offline
Since GTK3 creates so many issues, should we open a bug report on the Arch bug tracker asking the packager to patch /usr/lib/eclipse/eclipse.ini in order to make GTK2 the default?
Offline
Since GTK3 creates so many issues, should we open a bug report on the Arch bug tracker asking the packager to patch /usr/lib/eclipse/eclipse.ini in order to make GTK2 the default?
Might be a good idea until Eclipse/GTK3 is fixed upstream.
Offline
Added to bug tracker:
https://bugs.archlinux.org/task/46885
Let's hope the packager agrees with patching the package...
Offline