I have Ubuntu 16.04 and Eclipse Oxygen 3.A installed on my machine. The Eclipse restart does not work. Eclipse closes but does not start again neither by 'Restart' menu nor if an application requires a restart.
Update: I cleared .metadata/.log and then restarted Eclipse from the menu. As usual Eclipse closed down but did not start again. I had to start it by clicking on the icon on my taskbar. Below is the logs generated when I started Eclipse.
!SESSION 2018-08-19 20:44:55.135 -----------------------------------------------
eclipse.buildId=4.7.3.M20180330-0640
java.version=1.8.0_181
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_IN
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
!ENTRY org.eclipse.ui 2 0 2018-08-19 20:45:05.372
!MESSAGE Warnings while parsing the images from the 'org.eclipse.ui.commandImages' extension point.
!SUBENTRY 1 org.eclipse.ui 2 0 2018-08-19 20:45:05.372
!MESSAGE Cannot bind to an undefined command: plug-in='org.eclipse.lsp4e', id='org.eclipse.lsp4e.togglehighlight'
!ENTRY com.genuitec.eclipse.theming.ui 1 0 2018-08-19 20:45:08.115
!MESSAGE A DevStyle Theme is being activated on this workspace; preparing colors and configuration
!ENTRY com.genuitec.eclipse.theming.ui 1 0 2018-08-19 20:45:09.652
!MESSAGE DevStyle has archived current color configurations to alternate preferences - will be restored when switching out of the DevStyle Theme
!ENTRY com.genuitec.eclipse.patches 2 0 2018-08-19 20:45:13.331
!MESSAGE Patches instrumentation extension PerformanceJavaNavigatorContentProviderPatch ([31078] [Angular] Webclipse UI freezes constantly after closing/reopening Angular 2 projects) has not weaved class org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider.
The issue was that the path set for --launcher.library argument in eclipse.ini file was incorrect. I found it out by comparing the ini files from another installation. The path for this argument was set as a relative path which I replaced with an absolute path as below.
/home/<username>/.p2/pool/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.700.v20180518-1200
Related
I'm trying to use the google apps script plugin for eclipse (https://developers.google.com/eclipse/docs/apps_script) When I follow the directions and try to import an apps script project, The import wizard does not appear to populate, and I end up with the error in the title . The logs have the following:
!SESSION 2017-09-06 20:41:42.028 -----------------------------------------------
eclipse.buildId=4.6.3.M20170301-0400
java.version=1.8.0_131
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86_64 -data file:/E:/EclipsePortable/Data/workspace/
!ENTRY org.eclipse.ui.navigator 2 0 2017-09-06 20:41:46.917
!MESSAGE Can't find Navigator Content Descriptor with id: org.eclipse.jst.servlet.ui.EnhancedJavaRendering
!ENTRY com.google.gdt.eclipse.drive 1 0 2017-09-06 20:42:16.644
!MESSAGE Connected to Drive service at https://www.googleapis.com/
!ENTRY com.google.gdt.eclipse.drive 4 0 2017-09-06 20:43:23.266
!MESSAGE Error reading contents of project from Drive; see Error Log.
!STACK 0
java.lang.NullPointerException
at com.google.gdt.eclipse.drive.wizards.ScriptProjectImportWizard$2.run(ScriptProjectImportWizard.java:162)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
How can I get this working?
From https://developers.google.com/eclipse/
The Google Plugin for Eclipse is deprecated and will be removed in January 2018. Migrate to Cloud Tools for Eclipse and/or the GWT Eclipse Plugin as soon as possible to avoid disruption.
When I want to open the eclipse. I get the error described below:
Do you have any idea how to resolve this problem?
!SESSION 2014-02-13 13:50:28.893 -----------------------------------------------
eclipse.buildId=M20120914-1540
java.version=1.6.0_37
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=pl_PL
Command-line arguments: -os win32 -ws win32 -arch x86_64
!ENTRY org.eclipse.core.resources 2 10035 2014-02-13 13:50:30.981
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
!ENTRY org.eclipse.osgi 4 0 2014-02-13 13:50:31.228
!MESSAGE An error occurred while automatically activating bundle org.eclipse.core.resources (40).
I found the resolution. I'm deleting the file .metadata/.plugins/org.eclipse.core.resources/.snap And it's works!
When i start eclipse, on splash loading window, eclise auto exit with error:
!SESSION 2013-09-05 14:52:04.771 -----------------------------------------------
eclipse.buildId=4.3.0.I20130605-2000
java.version=1.7.0_25
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
!ENTRY org.eclipse.ui.workbench 4 2 2013-09-05 14:52:09.260
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
!STACK 0
java.lang.NullPointerException
at org.eclipse.equinox.internal.p2.core.helpers.ServiceHelper.getService(ServiceHelper.java:74)
at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry.updateRoamingProfile(SimpleProfileRegistry.java:156)
at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry.updateSelfProfile(SimpleProfileRegistry.java:147)
at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry.getProfileMap(SimpleProfileRegistry.java:344)
at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry.internalGetProfile(SimpleProfileRegistry.java:248)
at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry.getProfile(SimpleProfileRegistry.java:178)
at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdateScheduler.earlyStartup(AutomaticUpdateScheduler.java:88)
at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:87)
at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2552)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
!ENTRY org.eclipse.ui.workbench 4 2 2013-09-05 14:52:09.264
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
!STACK 0
java.lang.NullPointerException
at org.eclipse.core.internal.runtime.InternalPlatform.getLog(InternalPlatform.java:354)
at org.eclipse.core.runtime.Plugin.getLog(Plugin.java:291)
at org.eclipse.ui.internal.WorkbenchPlugin.log(WorkbenchPlugin.java:830)
at org.eclipse.ui.statushandlers.StatusManager.logError(StatusManager.java:285)
at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:200)
at org.eclipse.ui.internal.progress.ProgressManager$2.done(ProgressManager.java:467)
at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39)
at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:96)
at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152)
at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647)
at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:70)
!ENTRY org.eclipse.core.jobs 4 2 2013-09-05 14:52:09.267
!MESSAGE An internal error occurred during: "Workbench early startup".
!STACK 0
java.lang.NullPointerException
at org.eclipse.core.internal.runtime.InternalPlatform.getLog(InternalPlatform.java:354)
at org.eclipse.core.runtime.Plugin.getLog(Plugin.java:291)
at org.eclipse.ui.internal.WorkbenchPlugin.log(WorkbenchPlugin.java:818)
at org.eclipse.ui.internal.EarlyStartupRunnable.handleException(EarlyStartupRunnable.java:81)
at org.eclipse.core.runtime.SafeRunner.handleException(SafeRunner.java:75)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:44)
at org.eclipse.ui.internal.Workbench$55.run(Workbench.java:2552)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
I've tried:
deleting workspace/.metadata/.lock
delete the file WORKSPACE/.metadata/.plugins/org.eclipse.core.resources/.snap
But didn't solve this problem.
Solved when I delete ".\workspace.metadata.plugins\org.eclipse.e4.workbench" folder.
Follow this.
Try to start with an empty workspace or a fresh Eclipse installation. If they work, you can reimport the contents of your workspace and transfer the installed plugins (File > Export... > Installed Software Items, then Import).
Just do this
rm -fr /worksapce/.metadata/.plugins/or.eclipse.e4.workbench/workbench.xmi
and then restart eclipse.
Navigate to your Java Workspace Folder --> .metadata --> .plugins --> org.eclipse.e4.workbench.... delete this folder.. it works for me, hopefully it will also work for you.
Step 1: Goto cd /opt/eclipse/
Step 2: then vim eclipse.ini
Step 3: Add this line at the end of the file
"-Dorg.eclipse.swt.internal.gtk.cairoGraphics=false"
Step 4: ./eclipse
Try the above 4 steps. Issue will be resolved for eclipse in linux environment
I'm trying to create a standard osgi bundle under Eclipse Helios.
To do so, I've configured my Target Platform like this:
Window -> Preferences -> Plug-in Development -> Target Platform -> Add
After I choose Template and Base RCP (Binary Only)
I changed the name and clicked Finish.
When I launch the platform using the Overview of my bundle, I've got this error printed in the console :
!SESSION 2010-07-16 15:44:37.987 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_18
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_FR
Command-line arguments: -dev file:C:/Documents and Settings/E364866/Desktop/calendar/antonio osgi tutorial/.metadata/.plugins/org.eclipse.pde.core/OSGI DynaResume/dev.properties -os win32 -ws win32 -arch x86 -consoleLog -console
!ENTRY org.eclipse.ui 4 4 2010-07-16 15:44:44.659
!MESSAGE Unable to load UI activator
!ENTRY org.eclipse.ui 4 4 2010-07-16 15:44:44.659
!MESSAGE Unable to load UI activator
!STACK 0
I've managed to make the platform run by deselecting the org.eclipse.ui plug-in in the platform configuration window, but I don't understand why this plug-in is selected by default.
Quoting the comments in org.eclipse.ui.internal.WorkbenchPlugin:
// The UI plugin needs to be initialized so that it can install the callback in PrefUtil,
// which needs to be done as early as possible, before the workbench
// accesses any API preferences.
org.eclipse.ui plugin needs to load before your plug-in. You may fix this problem by giving it a start level less than your bundle's start level (which is probably set at default 4).
I am trying to install the CDT plugin on an exisitng 32-bit installation of Eclipse on Ubuntu Jaunty. I've tried both web-update and standalone-package install and both fail with the following error-
Application Started: 4000
!SESSION 2009-10-05 21:24:55.947 -----------------------------------------------
eclipse.buildId=I20090611-1540
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86 -consolelog -debug
!ENTRY org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2009-10-05 21:25:28.172
!MESSAGE Error while loading manipulator.
!STACK 0
java.lang.IllegalStateException: !fwConfigLocation.equals(fwPersistentDataLocation)
!fwConfigLocation=/opt/eclipse-galileo/configuration
,fwPersistentDataLocation=/opt/eclipse-galileo/plugins/configuration
at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.checkConsistencyOfFwConfigLocAndFwPersistentDataLoc(EquinoxManipulatorImpl.java:65)
at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.loadWithoutFwPersistentData(EquinoxManipulatorImpl.java:360)
at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.load(EquinoxManipulatorImpl.java:331)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:50)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:108)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.uninstallBundle(UninstallBundleAction.java:74)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.execute(UninstallBundleAction.java:29)
at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:35)
at org.eclipse.equinox.internal.provisional.p2.engine.Phase.mainPerform(Phase.java:129)
at org.eclipse.equinox.internal.provisional.p2.engine.Phase.perform(Phase.java:72)
at org.eclipse.equinox.internal.provisional.p2.engine.PhaseSet.perform(PhaseSet.java:44)
at org.eclipse.equinox.internal.provisional.p2.engine.Engine.perform(Engine.java:54)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningUtil.performProvisioningPlan(ProvisioningUtil.java:389)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProfileModificationOperation.doExecute(ProfileModificationOperation.java:61)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningOperation.execute(ProvisioningOperation.java:37)
at org.eclipse.equinox.internal.provisional.p2.ui.ProvisioningOperationRunner$1.run(ProvisioningOperationRunner.java:94)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!ENTRY org.eclipse.equinox.p2.engine 4 4 2009-10-05 21:25:28.201
!MESSAGE An error occurred while uninstalling
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2009-10-05 21:25:28.202
!MESSAGE session context was:(profile=epp.package.java, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Uninstall, operand=[R]org.eclipse.ant.ui 3.4.0.v20090520 --> [R]org.eclipse.ant.ui 3.4.1.v20090901_r351, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction).
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2009-10-05 21:25:28.202
!MESSAGE Error while loading manipulator.
!STACK 0
java.lang.IllegalStateException: Error while loading manipulator.
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:54)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:108)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.uninstallBundle(UninstallBundleAction.java:74)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.execute(UninstallBundleAction.java:29)
at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:35)
at org.eclipse.equinox.internal.provisional.p2.engine.Phase.mainPerform(Phase.java:129)
at org.eclipse.equinox.internal.provisional.p2.engine.Phase.perform(Phase.java:72)
at org.eclipse.equinox.internal.provisional.p2.engine.PhaseSet.perform(PhaseSet.java:44)
at org.eclipse.equinox.internal.provisional.p2.engine.Engine.perform(Engine.java:54)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningUtil.performProvisioningPlan(ProvisioningUtil.java:389)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProfileModificationOperation.doExecute(ProfileModificationOperation.java:61)
at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningOperation.execute(ProvisioningOperation.java:37)
at org.eclipse.equinox.internal.provisional.p2.ui.ProvisioningOperationRunner$1.run(ProvisioningOperationRunner.java:94)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
This may be related to bug 285743: as explained in this thread
What happens is that P2 fails to correctly setup osgi.install.area, because it doesn't strip 'plugins' part from the path. I saw this happen when eclipse.ini file in target directory didn't have '-startup' option in it.
Take a look into your eclipse.ini file if it contains -startup option like this:
-startup
plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
Note: if this is the case, you can refer to "proper" eclipse.ini to avoid any settings-related problem (for eclipse3.4 or 3.5.x): see "good" eclipse.ini.