I noticed the problem start after installing 10.4.3. I have used Eclipse on all the Java 1.5 versions Apple has released. I checked all permissions for every imaginable file all the way up to root. I did a disk repair permissions because Apple has in the past suggested I do that to fix seemingly unrelated problems and it has worked. I didn't have anything else I could think of, so I tried it. I looked for every file that I thought could be related to Eclipse on the entire disk (I used find from root) and removed it.
Nothing worked. And then you suggested trying it on a different user account. I hadn't thought of that, and wouldn't you know, it WORKED!
But I don't know why. There must be a file or configuration or cache or something that Eclipse uses (that I missed).
Is there a way to monitor the files a program opens during startup?
Oh, and Greg, Thank you very much, you've put me onto a path for a solution. I know of another person here with an identical system that is having problems as well.
duane
On Thursday, January 12, 2006, at 02:03PM, Greg Guerin <email@hidden> wrote:
>Duane and Julie wrote:
>
>>I have a 2.7GHz Dual G5, 4GB RAM, OS X 10.4.4 (the problem started with
>>10.4.3).
>
>What do you mean by "the problem started with 10.4.3"?
>
>Do you mean you had 10.4.3 installed, where you first observed the Eclipse
>problem, then you updated to 10.4.4 and it didn't solve the Eclipse problem?
>
>In short, exactly what have you done to your machine since you FIRST
>observed the Eclipse problem?
>
>
>>I have Java 1.5 installed.
>
>Exactly which version of Java 1.5? One of the DP's?
>
>
>>If I read this right, it looks like it can write a file to the
>>configuration directory. Interestingly enough, that's where the log file
>>shows up. I checked the permissions everywhere and all is good.
>
>What are the permissions and ownership of:
> /Users/dvs/Desktop/eclipse 3.2 M4/configuration/
>
>and the directories leading up to it?
>
>
>>I went to the 3.1.1 version and tried that. Same result.
>>I removed every trace of Eclipse I could find on my hard drive and
>>reinstalled 3.2 M4. Same result.
>>I repaired my disk permissions. Same result.
>
>Repairing disk permissions won't normally change anything in a user-account
>directory. That is, there are no "correct permissions" in that area, so
>repairing can't and won't see anything it can fix.
>
>Try creating a new user-account and running Eclipse under it. If it still
>fails, then it's probably not a file-permission problem, or at least not a
>simple one. It could be a file-permission problem in Eclipse itself, which
>I don't know if Disk Utility can repair the permissions of or not. In any
>case, that's just a guess.
>
>Does Eclipse store any config files for global use? Could be the problem
>lies there. Check in /Library/ for such things. Or find out all the files
>Eclipse reads and writes during startup, and check each one of them for
>permissions.
>
> -- GG
>
>
> _______________________________________________
>Do not post admin requests to the list. They will be ignored.
>Java-dev mailing list (email@hidden)
>Help/Unsubscribe/Update your Subscription:
>http://lists.apple.com/mailman/options/java-dev/email@hidden
>
>This email sent to email@hidden
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
