Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 328164 - Eclipse.app won't launch anymore after update to Helios SR 1
Summary: Eclipse.app won't launch anymore after update to Helios SR 1
Status: CLOSED NOT_ECLIPSE
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.6   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-19 13:39 EDT by Olaf Groeger CLA
Modified: 2010-11-13 07:14 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olaf Groeger CLA 2010-10-19 13:39:50 EDT
Build Identifier: 20100917-0705

While updating a Helios distribution to the Service Release 1, the update requests to restart the workspace. After that, the application wont launch anymore. It doesn't launch when you double click Eclipse.app either. The reason is that the file Eclipse.app/Contents/MacOS/eclipse is missing the executable flag.

After you assign the flag using
    chmod +x eclipse
the .app launches again.

I could this reproduce with my Java, J2EE and RCP distrib.

Reproducible: Always

Steps to Reproduce:
1. Install Helios Release
2. Update to Helios Service 1 using the Help->Check for Updates
3. Let the update manager restart the application
4. .app doesn't launch anymore
Comment 1 Thomas Watson CLA 2010-10-19 14:50:20 EDT
Are you running 32 or 64 bit?  I just tried the Java EPP for Helios and it successfully updated and the eclipse exe had the correct executable flag set after update.
Comment 2 Olaf Groeger CLA 2010-10-19 14:58:37 EDT
(In reply to comment #1)
> Are you running 32 or 64 bit?  I just tried the Java EPP for Helios and it
> successfully updated and the eclipse exe had the correct executable flag set
> after update.

Sorry, i forgot to mention it: It is 64 bit.
Comment 3 Thomas Watson CLA 2010-10-19 16:45:46 EDT
I just tried the Java EPP 64-bit, it works for me.
Comment 4 Olaf Groeger CLA 2010-10-19 18:05:43 EDT
That's strange, Thomas. I checked it three more times:

1. I downloaded eclipse-java-helios-macosx-cocoa-x86_64.tar.gz (Build id: 20100617-1415)
2. I unpacked and launched by double clicking Eclipse.app
3. Help -> Check for Updates ...
4. ...next ... next ... accept ... Finish ... Restart? yes
5. Doesn't launch anymore

System is a MacMini 2GHz, OS X 10.6.4, German.
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02-279-10M3065)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01-279, mixed mode)
Comment 5 Thomas Watson CLA 2010-10-20 08:30:46 EDT
I'm going to move to p2 for comment.  If anything touches the permissions of file on update it would be p2.  I have basically the same environment except I am still running the older Leopard MaxOS 10.5.8.
Comment 6 Olaf Groeger CLA 2010-10-21 01:48:15 EDT
Additional info. I took a look into the Konsole application and found the following which occured during the update:

21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]	java.io.FileNotFoundException: /opt/public/technology/epp/epp_build/36/eclipse.S-3.6RC4-201006031500/artifacts.xml (No such file or directory)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at java.io.FileOutputStream.open(Native Method)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.save(SimpleArtifactRepository.java:951)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.save(SimpleArtifactRepository.java:932)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.<init>(SimpleArtifactRepository.java:322)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepositoryFactory.create(SimpleArtifactRepositoryFactory.java:129)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.factoryCreate(ArtifactRepositoryManager.java:60)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.doCreateRepository(AbstractRepositoryManager.java:284)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.artifact.repository.ArtifactRepositoryManager.createRepository(ArtifactRepositoryManager.java:48)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.touchpoint.eclipse.Util.getBundlePoolRepository(Util.java:87)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.touchpoint.eclipse.EclipseMarkSetProvider.getMarkSets(EclipseMarkSetProvider.java:41)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.garbagecollector.GarbageCollector$ParameterizedSafeRunnable.run(GarbageCollector.java:69)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.garbagecollector.GarbageCollector.contributeMarkSets(GarbageCollector.java:97)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.garbagecollector.GarbageCollector.traverseRegisteredProfiles(GarbageCollector.java:225)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.garbagecollector.GarbageCollector.runGC(GarbageCollector.java:163)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.garbagecollector.GarbageCollector.notify(GarbageCollector.java:148)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.core.ProvisioningEventBus.dispatchEvent(ProvisioningEventBus.java:108)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.core.ProvisioningEventBus.publishEvent(ProvisioningEventBus.java:85)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:94)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.p2.operations.ProvisioningSession.performProvisioningPlan(ProvisioningSession.java:174)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.p2.operations.ProfileModificationJob.runModal(ProfileModificationJob.java:79)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
21.10.10 07:42:18	[0x0-0x259259].org.eclipse.eclipse[15956]		at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 7 Alain CLA 2010-11-12 07:59:52 EST
Hi 

I just had about the same problem.
I was testing, if I'm able to update my demo(really small) eclipse product(containing RCP, PDE).
It was no problem with the x86 32bit version.
But with the x86_64 bit version, the exe (e.g. eclipse.exe) file was missing after updating my product.

Regards, Alain.
Comment 8 Olaf Groeger CLA 2010-11-13 07:14:42 EST
I think i found the reason which has absolutly nothing to do with Eclipse: I had an environment.plist file in the .MacOS directory which overrode the PATH variable, but missed some directories that are usually set, e.g. /usr/sbin (contains chown) and /bin (contains rm and chmod).
After adding those directories to the PATH in the environment.plist the update succeeds.

Sorry for the false alarm, i'm closing the ticket.