Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
WebHead said:
I don't mind starting this debate again. Mathematically, 10.3.10 is the equivalent of 10.3.1. But then the second decimal point is mathematically incorrect, so anything's possible ...

Open Mail. Check the version. It now says 1.3.11. Many more such examples exist. Consider version numbers simply a part of a product name, because that's what they are.

I'm currently using BitPim 0.7.30, which came after 0.7.29.
 
caution! my powerbook ti 1Ghz won't let me launch safari (thank god for firefox) after the update. i've rebooted and everything i'm now going to try to repair permissions. proceed with caution!!!
 
Fixed the height issue!

HOLY CRAP!

I never thought I'd see the day!

Safari 1.3 has fixed the 100% height issue in HTML, where a table using it only went down to cover the length of the content.

Now it goes ALL the way down to the bottom of the screen like it's supposed to.

THANK YOU APPLE!!!!!
 
Safari Crash Solved (I think)

I think I solved my safari crash. I noticed something suspicious in the crash log...

0x1000 - 0xccfff com.apple.Safari 1.3 (312) /Applications/Safari.app/Contents/MacOS/Safari
0x426000 - 0x427fff com.presenta.iGetterIMBundle 2.1 /Users/jmyers/Library/InputManagers/iGetterIMBundle/iGetterIMBundle.bundle/Contents/MacOS/iGetterIMBundle
0x430000 - 0x431fff com.presenta.iGetterSafariBundle 2.1 /Users/jmyers/Library/InputManagers/iGetterIMBundle/iGetterIMBundle.bundle/Contents/Resources/iGetterSafariBundle.bundle/Contents/MacOS/iGetterSafariBundle

So I deleted ~/Library/InputManagers/iGetterIMBundle/iGetterIMBundle.bundle , and Safari no longer crashes! Cool!

I hope this helps other people too.....
 
To all who have issues with Safari not starting up, I had to restart TWICE before safari (and mail too) would start up properly, not just once.
 
clusterman said:
At last, everyone else gets our deaf-node syndrome fix for the xserve:

Network Hardware

* Addresses on issue with Ethernet communication on Xserve hardware that could result in packet corruption.
What does this look like? We've been seeing some strange dropoffs, but have been focusing on wiring issues. I'm curious to see what your symptoms were...
 
Safari is busted

Just performed update. Safari bombed 1st 2 launches. Managed to stay afloat, linked to another page. Bomb.

I have killed Prefs and am repairing permissions right now. I am posting from Firefox :(
 
2nd reboot and repairing permissions did not help. safari continues to crash at launch. i am now about to download the cummulative update and try again. folks with a 15 in Ti powerbook (1Ghz), beware!!!
 
No Problem

No problems here, just finished both machines, Rev A PowerMac G5 Dual 2Ghz and a Rev C 12" PowerBook. In 14 days it will be time to wipe 'em clean and unleash Tiger.
:)
 
wdlove said:
Very interesting 14 days till Tiger and now we have Panther 10.3.9. I will wait until tomorrow just to see how it works for everyone.
If memory serves me, the last point upgrade of Jaguar came out after the Panther announcement, but before the release. The timing seems virtually the same. Of course, it may have something to do with new hw/sw coming in the days ahead, but who knows.
 
j-a-x said:
I think I solved my safari crash. I noticed something suspicious in the crash log...

0x1000 - 0xccfff com.apple.Safari 1.3 (312) /Applications/Safari.app/Contents/MacOS/Safari
0x426000 - 0x427fff com.presenta.iGetterIMBundle 2.1 /Users/jmyers/Library/InputManagers/iGetterIMBundle/iGetterIMBundle.bundle/Contents/MacOS/iGetterIMBundle
0x430000 - 0x431fff com.presenta.iGetterSafariBundle 2.1 /Users/jmyers/Library/InputManagers/iGetterIMBundle/iGetterIMBundle.bundle/Contents/Resources/iGetterSafariBundle.bundle/Contents/MacOS/iGetterSafariBundle

So I deleted ~/Library/InputManagers/iGetterIMBundle/iGetterIMBundle.bundle , and Safari no longer crashes! Cool!

I hope this helps other people too.....

Woohoo! Same sort of thing worked for me. I removed PithHelmet (0.7.3) manually and it's now working.

Like you the error report told me where to look for it.

Also tried had removed Sogudi, but put it back and it's still fine.
 
ifjake said:
2nd reboot and repairing permissions did not help. safari continues to crash at launch. i am now about to download the cummulative update and try again. folks with a 15 in Ti powerbook (1Ghz), beware!!!
I have the same PB, with no Safari problems to report after the update.
 
ChrisH3677 said:
Woohoo! Same sort of thing worked for me. I removed PithHelmet (0.7.3) manually and it's now working.

Like you the error report told me where to look for it.

Also tried had removed Sogudi, but put it back and it's still fine.

Glad it worked for you! Now if only I could figure out why Java isn't working ....
 
ifjake said:
2nd reboot and repairing permissions did not help. safari continues to crash at launch. i am now about to download the cummulative update and try again. folks with a 15 in Ti powerbook (1Ghz), beware!!!


Check the crash reporter. Are you running any third party input managers etc?

I had to remove PithHelmet (0.7.3) before I could even get Safari to start again.


PS Why would you think it's a hardware problem? Altho you do have the same computer as me.
 
Toe said:
What does this look like? We've been seeing some strange dropoffs, but have been focusing on wiring issues. I'm curious to see what your symptoms were...

Toe,

The "deaf node" syndrome is where a node will stop responding to ethernet traffic. Yet, if you log into the node via the console, you can see that everything APPEARS fine. If you shut down the interface, and bring it back up, all is well.

The bug has to do with corrupted frames being received, i.e. a 1504 byte frame when the node is expecting a 1500 byte frame, etc.

When things were REALLY bad, we could guarantee crash 1/2 of a rack of machines in 10 minutes.
 
Beware...

This update breaks PithHelmet. You might want to hold off until a PH update is out. I'll be using Firefox for now. :(

[edit]
I also don't appreciate the added commercial bookmarks. WTF is that all about? :mad: :mad: I hope this was a simple oversight; messing with the user's bookmarks is completely unacceptable.
 
Re: Java

I just upgraded, and Java is dying:
Code:
$ java -version
Segmentation fault
I checked Console, and this is what I'm getting:
Code:
Apr 15 22:39:40 localhost crashdump: Unable to determine CPSProcessSerNum pid: 632 name: java
Apr 15 22:39:40 localhost crashdump: Started writing crash report to: /Users/benfroman/Library/Logs/CrashReporter/java.crash.log
Apr 15 22:39:40 localhost crashdump: Finished writing crash report to: /Users/benfroman/Library/Logs/CrashReporter/java.crash.log
Apr 15 22:41:28 localhost crashdump: Unable to determine CPSProcessSerNum pid: 649 name: java
Apr 15 22:41:28 localhost crashdump: Started writing crash report to: /Users/benfroman/Library/Logs/CrashReporter/java.crash.log
Apr 15 22:41:28 localhost crashdump: Finished writing crash report to: /Users/benfroman/Library/Logs/CrashReporter/java.crash.log
Apr 15 22:41:32 localhost crashdump: Unable to determine CPSProcessSerNum pid: 652 name: java
Apr 15 22:41:32 localhost crashdump: Started writing crash report to: /Users/benfroman/Library/Logs/CrashReporter/java.crash.log
Apr 15 22:41:32 localhost crashdump: Finished writing crash report to: /Users/benfroman/Library/Logs/CrashReporter/java.crash.log
Apr 15 22:45:32 localhost crashdump: Unable to determine CPSProcessSerNum pid: 668 name: java
Apr 15 22:45:32 localhost crashdump: Started writing crash report to: /Users/benfroman/Library/Logs/CrashReporter/java.crash.log
Apr 15 22:45:32 localhost crashdump: Finished writing crash report to: /Users/benfroman/Library/Logs/CrashReporter/java.crash.log
Anyone have any ideas?

Thanks,
Ben
 
i got rid of iAlert input manager - but there is SIMBL in there too, can i get rid of that as well? Looks like its from Apple from the Info doc in there...

ugh...
 
Still cant cut and paste in the Fiinder ..... it has always baffled me why there is an option to cut (command-x) but it is always greyed out.
 
About the "Transparent Windows" in Safari... my guess is that they added that ability to Safari (Webkit? don't know the technical terms for Mac internals) so that Dashboard widgets can have transparency.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.