Neither Mail nor Safari will open after 10.4.6 update

mousemen

Registered
Client's Ibook was running Jaguar 10.2.8, and Mail was locking up as it was overstuffed. Upgraded to 10.4.3 to fix the problem, and it did, in fact, fix it.

Was then prompted to install all available updates, which I thought I would do as a courtesy before returning the system to the client.

Now, after the updates, neither Mail nor Safari opens. I get no spinning beach ball...just no response. Other programs, including IE, MS Office programs, and System Preferences are working fine. Starting in Safe Boot makes no difference.

I have done both clicking the dock's icons and clicking the actual application itself.

Upon clicking the application, there is that quick app launch "animation", but nothing happens. Mail simply does not open, and there is no spinning beach ball. When Get Info on it, it says the last time the program was opened was the last time I attempted opening it...the time is accurate.

The EXACT same behaviour is occurring with Safari.

Hope this helps.

Kind of at a loss and all help is appreciated...thanks in advance!
 
Installed the combo update.

Now, half the time, Safari will open but be sort of unresponsive...i.e. the program opening but no browser window, and Mail stalls out after receiving 2 msgs.

The problem appears to be shared among the programs. Here is a snippet of my console which I obviously need help in interpreting. Should I start a new thread?:

2006-05-04 07:48:03.369 Mail[347] +[NSObject(LockingAdditions) clearLocks]: object 0x4ddb90 still holds lock (count=1) in thread 0x188fe00
2006-05-04 07:52:31.036 Mail[347] *** +[WebGraphicsBridge sharedBridge]: selector not recognized
2006-05-04 07:52:31.045 Mail[347] *** -[NSPlaceholderMutableArray initWithObjects_ex:count:]: attempt to insert nil
2006-05-04 07:53:11.855 Mail[347] *** +[WebGraphicsBridge sharedBridge]: selector not recognized
2006-05-04 07:53:11.856 Mail[347] Exception raised during monitored invocation of reallyDeleteMessages:allowMoveToTrash:retainingStores:, exception: *** +[WebGraphicsBridge sharedBridge]: selector not recognized
2006-05-04 07:53:11.856 Mail[347] +[NSObject(LockingAdditions) clearLocks]: object 0x4ddb90 still holds lock (count=1) in thread 0x18f6c00
2006-05-04 07:53:21.774 Mail[347] *** +[WebGraphicsBridge sharedBridge]: selector not recognized
2006-05-04 07:53:21.775 Mail[347] exception raised in routeMessages: *** +[WebGraphicsBridge sharedBridge]: selector not recognized
2006-05-04 07:53:22.601 Mail[347] *** +[WebGraphicsBridge sharedBridge]: selector not recognized
2006-05-04 07:53:22.602 Mail[347] Exception raised during monitored invocation of routeQueuedMessages, exception: *** +[WebGraphicsBridge sharedBridge]: selector not recognized
2006-05-04 07:53:22.602 Mail[347] +[NSObject(LockingAdditions) clearLocks]: object 0x4ddb90 still holds lock (count=2) in thread 0x18c8600
2006-05-04 08:00:03.012 Safari[320] *** +[WebGraphicsBridge sharedBridge]: selector not recognized
2006-05-04 08:00:03.013 Safari[320] *** +[WebGraphicsBridge sharedBridge]: selector not recognized
2006-05-04 08:00:13.963 Safari[320] *** +[WebGraphicsBridge sharedBridge]: selector not recognized
2006-05-04 08:00:14.066 Safari[320] *** +[WebGraphicsBridge sharedBridge]: selector not recognized
2006-05-04 08:00:30.694 Safari[320] *** +[WebGraphicsBridge sharedBridge]: selector not recognized
2006-05-04 08:00:30.694 Safari[320] *** +[WebGraphicsBridge sharedBridge]: selector not recognized
 
Have you tried trashing their .plist preference files? They are located in Users/[Username]/Library/Preferences

On 10.4, you can also press Apple-Space bar and type in Safari. Soon, com.apple.safari.plist will show up. Click "Show all" then click once on com.apple.safari.plist. Then press Apple-delete (the one that should say backspace). That will trash it.

Do the same for Mail.

Empty the trash and then try running them. I hope that works.

Doug

P.S. The system logs are really cool and amazingly good for troubleshooting, but I've started to think how much time it takes to write to the logs for every single action. Does anyone think that may affect performance? Just an idle thought.
 
Back
Top