Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: pup975
pup975 Author
User level: Level 1
8 points

Leopard Failing to shut down

Intermittently, I have been getting this message when I try to shut down my Core2Duo Macbook running Leopard 10.5.1: "Logout has timed out because the application 'X' failed to quit. Try again, quit 'X' and choose Log Out from the Apple menu," where "X" is a random program (although most of the time it is Preview). The problem is is that "X" application is not open or is running when I look at the Console. When I open application "X," quit the application, then try to Shut Down, I get the same message but with a different application. These applications are not running when I look at the Activity Monitor. I haven't found what the cause is and it doesn't occur every time. I have noticed that it will do it when I've had a problem waking up my Macbook from sleep mode (it will give me a black screen after logging-in but will awake from sleep if I close my Macbook and try again).

My event log shows the following:

12/24/07 9:34:15 AM com.apple.dyld[820] update dyld_sharedcache: warning can't use root /Applications/Safari.app/Contents/MacOS/Safari: can't open file, errno=2
12/24/07 9:34:15 AM com.apple.dyld[820] update dyld_sharedcache: warning can't use root /Applications/Mail.app/Contents/MacOS/Mail: can't open file, errno=2
12/24/07 9:34:15 AM com.apple.dyld[820] update dyld_sharedcache: warning can't use root /Applications/iChat.app/Contents/MacOS/iChat: can't open file, errno=2
12/24/07 9:34:19 AM loginwindow[39] ERROR | WSActivateApp | SetFrontProcess({0, 352342}) returned error -600. Unable to activate process.
12/24/07 9:34:24 AM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 51 seconds
12/24/07 9:35:02 AM loginwindow[39] ERROR | WSActivateApp | SetFrontProcess({0, 352342}) returned error -600. Unable to activate process.
12/24/07 9:35:09 AM bootpd[171] can't open /etc/bootptab
12/24/07 9:35:09 AM bootpd[171] server name Macbook.local
12/24/07 9:35:09 AM bootpd[171] interface en0: ip 192.168.2.1 mask 255.255.255.0
12/24/07 9:35:09 AM bootpd[171] interface fw0: ip 192.168.3.1 mask 255.255.255.0
12/24/07 9:35:09 AM bootpd[171] interface en1: ip 192.168.0.104 mask 255.255.255.0
12/24/07 9:35:09 AM bootpd[171] interface en2: ip 192.168.4.1 mask 255.255.255.0
12/24/07 9:35:09 AM bootpd[171] interface en2: ip 169.254.9.247 mask 255.255.0.0
12/24/07 9:35:09 AM bootpd[171] interface en3: ip 10.211.55.2 mask 255.255.255.0
12/24/07 9:35:09 AM bootpd[171] dhcp: re-reading lease list
12/24/07 9:35:15 AM com.apple.dyld[823] update dyld_sharedcache: warning can't use root /Applications/Safari.app/Contents/MacOS/Safari: can't open file, errno=2
12/24/07 9:35:15 AM com.apple.dyld[823] update dyld_sharedcache: warning can't use root /Applications/Mail.app/Contents/MacOS/Mail: can't open file, errno=2
12/24/07 9:35:15 AM com.apple.dyld[823] update dyld_sharedcache: warning can't use root /Applications/iChat.app/Contents/MacOS/iChat: can't open file, errno=2
12/24/07 9:35:15 AM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 60 seconds
12/24/07 9:36:04 AM natd[789] failed to write packet back (No route to host)
12/24/07 9:36:16 AM com.apple.dyld[824] update dyld_sharedcache: warning can't use root /Applications/Safari.app/Contents/MacOS/Safari: can't open file, errno=2
12/24/07 9:36:16 AM com.apple.dyld[824] update dyld_sharedcache: warning can't use root /Applications/Mail.app/Contents/MacOS/Mail: can't open file, errno=2
12/24/07 9:36:16 AM com.apple.dyld[824] update dyld_sharedcache: warning can't use root /Applications/iChat.app/Contents/MacOS/iChat: can't open file, errno=2

Anyone else with this problem or know why it is doing this?

Message was edited by: pup975

Macbook, Mac OS X (10.5)

Posted on Dec 24, 2007 7:37 AM

Reply
8 replies
User profile for user: Bill Backstrom
Bill Backstrom
User level: Level 1
110 points

Jan 14, 2008 6:13 PM in response to pup975

I’m having this exact same issue. I get the error message from loginwindow with the WSActivateApp. I don't get the other messages from your example. A -600 from SetFrontProcess() means “process not found”. I haven’t figured out how to map the arguments to a process id.

I did find that killing loginwindow does log you out. I presume you could reboot gracefully from there.
In my case, all I want to do is lock my screen while I’m away from my desk, so this workaround is a little much.

Here's a link to someone having the same issue:

http://blog.maccarocks.com/2008/01/14/os-x-finder-wont-quit-logout-timeout/
Reply
User profile for user: imac007
imac007
User level: Level 3
845 points

Jan 15, 2008 10:20 PM in response to pup975

It is likely that you are experiencing some conflicts.
The main conflicts are cache, permissions, fonts and login items.
If you did an upgrade of Leopard over Tiger you could have all 3.

The log seems to point to some cache problems.
So let's start with user cache.
In Finder click on Go>Home>Library and pull the Caches folder to the Trash.
Then click on the hard drive icon in the sidebar and double click on this Library and remove Caches here too.

Click on the apple>System Preferences>Accounts and unlock the lock.
Click on login items and remove all items from the window.

Then Go>Utilities>Disk Utility and select your hard drive volume then Verify Disk.
If the disk passes then Repair Disk Permissions.
Once any repairs are done, quit Disk Utility.

Click on Go>Applications>Font Book.
In Font Book choose All Fonts in the 1st column, then click into the second column.
Check for a black dot to the right of any of the fonts in the list in the second column.
If there are any dots the click on Edit>Select All.
Next Edit>Resolve Duplicates.
Next File>Validate Fonts.
Put a check mark in the box to the left of all fonts that shows problems and click on Remove Checked.

Next boot to the Leopard install disk >Utilities>Reset Password.
Click on your hard drive volume>home directory user name>Reset permissions and ACL's at the bottom.
Then restart your computer.

This will rebuild some Cache files so it will be slow on this startup.
Reply
User profile for user: hopkapi
hopkapi
User level: Level 2
150 points

Jan 20, 2008 10:55 AM in response to pup975

I've been experiencing some similar issues (occasional inability to shut down/wake from sleep etc.) with the same warnings from update dyld_sharedcache showing up in Terminal, a bit of Googling and I found a terminal command which forces the update, and then got the exact same warning from it about not being able to open the files.

Then it hit me, all of the applications that it was having trouble updating the caches for weren't in the root of the Applications folder as I'd moved them, so I dragged them back, re-ran the command, and it worked fine. It's too early to tell if this is going to fix it, but it does at least make some sense, and as an aside, Safari and Mail are launching way more quickly now.

"sudo update dyld_sharedcache" Is the command I used in Terminal, via Sun Baked's second reply in this thread: http://forums.macrumors.com/showthread.php?t=404147.
Reply

Leopard Failing to shut down

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up