jamdr said:
No offense, but why on earth would you install an OS update if you had deadlines? I know that they're "supposed to just work" but cmon, why take that chance? If it ain't broke...
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Java stopped working when I upgraded to OS X 10.3.9.
- Thread starter jamdr
- Start date
- Sort by reaction score
No offense, but why on earth would you install an OS update if you had deadlines? I know that they're "supposed to just work" but cmon, why take that chance? If it ain't broke...
gallivant said:
Okay, if you live deadline to deadline, and they're really important, why not wait to update and see if anyone has problems? That's what I do, and I don't even really have deadlines...
Someone on the discussion boards on apple's site reinstalled Security Update 2005-002 and his java came back. My java died and I re-applied this update and now it's back again.
http://discussions.info.apple.com/webx?14@748.XF4kaLK1Q0j.7@.68ac4201
http://discussions.info.apple.com/webx?14@748.XF4kaLK1Q0j.7@.68ac4201
chiapet said:
This worked for me too. In my case I updated two machines from 10.3.8 to 10.3.9, my new Powerbook and my old iBook. On the PB java worked fine after the upgrade, on the iBook I got the segfault.
I believe the iBook was likely running a java application (JPluck) at the time I did the upgrade, and this is the reason that it had the problem while the PB was ok - the 10.3.9 installer was unable to perform some process due to the existing java instance locking resources.
In any case, I've been reading various forums and have yet to find anyone report that reinstalling the Security Update 002 failed to solve the problem, so give it a go!
This should work: http://www.macfixit.com/article.php?story=20050416011813477
My problem was solved by installing the Security Update.
My problem was solved by installing the Security Update.
I was going to post about the fix (reinstalling the 2005-002 security fix, oddly enough), but I see that's been covered. This seems to have been quite a widespread problem, and many people aren't going to be reading online forums for a solution. Java will probably get blamed for "not working" and casual OS X users will have yet another reason to take issue with Java (now it'll be slower, more outdated, and more unreliable than Java for Windows and Linux ). This is quite a setback for Java developers on OS X. I hope Apple does something to fix this and not depend on users to reinstall the security update.
). This is quite a setback for Java developers on OS X. I hope Apple does something to fix this and not depend on users to reinstall the security update.
jamdr said:So, who's going to be installing Tiger now on a computer with important files?
I will, but not when I'm on deadline.
Someone in another thread suggested that this problem happens if you are actually running Java when you do the 10.3.9 update. Also, reinstalling the security update fixes the problem only because it does a pre-bind again, which you can do from the terminal directly: sudo update_prebinding.
daveL said:
Others' mileage may vary, but I tried updating prebinding manually (and then rebooting) as a first-try fix before re-applying the Security Update, and this didn't help..
I found another solution (easier)
Let me start out saying that this does work, but it does involve modifying a system file. go to /System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/. Now, here's the tricky part: get the info of version.plist. Check the preferences and change it from "system" to <administrator's name>. Now open version.plist with vim through Terminal. to do this type:
vim /System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/version.plist
You'll have to change it from:
...
<key>CFBundleShortVersionString</key>
<string>2.0.0</string>
<key>CFBundleVersion</key>
<string>2.0.0</string>
...
to:
...
<key>CFBundleShortVersionString</key>
<string>1.3.5</string>
<key>CFBundleVersion</key>
<string>1.3.5</string>
...
This change will enable you to run the Java 1.4.2 Update 2. Once you've run that and restart it, everything should be fine. (Note: you can change the version number anywhere from 1.3.2 to 1.4.1, but I personally put in 1.3.5 and that worked. If you put in any other value, you'll have the same problem. Also, I have not checked to see if changing the values back to what they should have been after that update would work. If it does, this would of course not involve a restart.)
if you don't know how to use vim, here's a quick run through:
the arrow buttons move the cursor (not the mouse-click)
<i> makes it possible to "insert" changes
hit <esc> when you have finished making the changes
type ":w" to save, ":w!" to force save
type ":q" to quit, ":q!" to force quit
Let me start out saying that this does work, but it does involve modifying a system file. go to /System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/. Now, here's the tricky part: get the info of version.plist. Check the preferences and change it from "system" to <administrator's name>. Now open version.plist with vim through Terminal. to do this type:
vim /System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/version.plist
You'll have to change it from:
...
<key>CFBundleShortVersionString</key>
<string>2.0.0</string>
<key>CFBundleVersion</key>
<string>2.0.0</string>
...
to:
...
<key>CFBundleShortVersionString</key>
<string>1.3.5</string>
<key>CFBundleVersion</key>
<string>1.3.5</string>
...
This change will enable you to run the Java 1.4.2 Update 2. Once you've run that and restart it, everything should be fine. (Note: you can change the version number anywhere from 1.3.2 to 1.4.1, but I personally put in 1.3.5 and that worked. If you put in any other value, you'll have the same problem. Also, I have not checked to see if changing the values back to what they should have been after that update would work. If it does, this would of course not involve a restart.)
if you don't know how to use vim, here's a quick run through:
the arrow buttons move the cursor (not the mouse-click)
<i> makes it possible to "insert" changes
hit <esc> when you have finished making the changes
type ":w" to save, ":w!" to force save
type ":q" to quit, ":q!" to force quit