I am not sure that the answers to these questions adequately solve this problem. I found that with some of our RCP products with eclipse derivatives, which on some Linux machines, plugins will fail with log entries like this:
!ENTRY org.eclipse.equinox.p2.engine 4 4 2017-02-23 12:00:49.492 !MESSAGE An error occurred while installing the items !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2017-02-23 12:00:49.492 !MESSAGE session context was:(profile=TIBCOBusinessStudio-4.0, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]com.tibco.eclipse.p2.installer 1.1.3.20161130, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction). !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2017-02-23 12:00:49.492 !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:59) at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:108) at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.installBundle(InstallBundleAction.java:75) at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction.execute(InstallBundleAction.java:32) at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:38) at org.eclipse.equinox.internal.p2.engine.Phase.mainPerform(Phase.java:183) at org.eclipse.equinox.internal.p2.engine.Phase.perform(Phase.java:95) at org.eclipse.equinox.internal.p2.engine.PhaseSet.perform(PhaseSet.java:47) at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:75) at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44) at org.eclipse.equinox.p2.operations.ProvisioningSession.performProvisioningPlan(ProvisioningSession.java:159) at org.eclipse.equinox.p2.operations.ProfileModificationJob.runModal(ProfileModificationJob.java:79) at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
The reason I suspect is because the actual name of the configuration file is compared with the absolute name lazyloader. In my case, the home directory is a symbolic link, so the two names do not match. The permission was to edit eclipse.ini (or whatever you name) and make sure that all paths that link to the eclipse home directory are fully qualified and don't rely on symbolic links.
Wendell nichols
source share