Community
Participate
Working Groups
0 down vote favorite Eclipse IDE for Java EE Developers and my java version is java version "1.8.0_131" . I'm using Ubuntu 14.04 (32-bit) and the JDK version is 1.8. The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized. Segmentation fault (core dumped) -This is the errror i am getting !!
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Please reopen if someone faced the issue recently.
I've been having it intermittently, running env GTK_IM_MODULE=ibus /opt/local/jee-2020-09/eclipse/eclipse
@Gayan, have you observed this anytime? Any inputs?
No @Sarika, not on windows or mac, I’m running the latest IBuilds without any issues. But i never had JEE package.
Hmmm, I just got the same thing with eclipse-java-2020-09-R-linux-gtk-x86_64.tar.gz.
Please attach the eclipse logs, it will help the devs to find whats going on. Also make sure - you are using Java11 or higher. - start eclipse with a clean workspace (preferably a new folder) - start eclipse with ./eclipse -clean If above doesn't solve you issue, please attach the log file.
Hi Gayan, 1. I took all three of your suggestions, and got this output: [rsigal@localhost eclipse]$ ./eclipse -clean org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized. org.eclipse.m2e.logback.configuration: Logback config file: /home/rsigal/workspace.new/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.16.0.20200318-1040.xml org.eclipse.m2e.logback.configuration: Initializing logback before specifying a new, empty workspace, but then eclipse started up. 2. When I did the same but with an existing workspace, I got the same output on the console, but eclipse didn't start. There are a lot of complaints, including OutOfMemoryErrors. 3. When I downloaded a maven project into a new workspace, I got the same console messages, but eclipse started and I have a usable workspace. Maybe I have problems in my existing workspaces (although everything worked fine until recently). But as long as I can create and use new workspaces, I should be ok. Thanks for your help. -Ron
I am having the same issue: I am using java org.eclipse.m2e.logback.configuration: Activated before the state location was initialized. Retry after the state location is initialized. Starting Groovy-Eclipse compiler resolver. Specified compiler level: unspecified 103 org.codehaus.groovy_3.0.10.v202204221856-e2112 STARTING 629 org.codehaus.groovy_2.5.16.v202204221856-e2112 STARTING Skipped bundle version 3.0.10.v202204221856-e2112 Stopped bundle version 2.5.16.v202204221856-e2112 Refresh bundles: 629 org.codehaus.groovy_2.5.16.v202204221856-e2112 UNINSTALLED org.eclipse.m2e.logback.configuration: Logback config file: /home/dan/eclipse-workspace/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.16.3.20211002-1029.xml org.eclipse.m2e.logback.configuration: Initializing logback SLF4J: No SLF4J providers were found. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#noProviders for further details. %java -version openjdk version "11.0.15" 2022-04-19 OpenJDK Runtime Environment (build 11.0.15+10-Ubuntu-0ubuntu0.20.04.1) OpenJDK 64-Bit Server VM (build 11.0.15+10-Ubuntu-0ubuntu0.20.04.1, mixed mode, sharing)
