[rhombus]

Hi,

When I restarted my MacBook after using bootcamp into Leopard, virtually every applications crashes on startup. Firefox works, but every Apple application crashes immediately after I open it. I have no idea why this problem occurred-is there any way of resolving without reinstalling Leopard (I am at university, I didn't bring my disk with me)? I cannot repair permission because disk utility doesn't work, but I have ran fsck and zapped the pram, with had no effect on the problem. Any ideas?

[rhombus]

Never mind, found another copy of Leopard. Reinstalling system software was the only way to solve the problem.

[Cold Warrior]

Probably a bad install. Glad your reinstallation fixed it.

[rhombus]

Reinstalling fixed that problem fortunately. I applied all current updates including 10.5.2 combo. No visible problems. Then today, I shut my computer down to campus and then, less than 24hrs after yesterday's reinstallation, my MacBook refused to start, just hangs at the grey screen. Tried hard reset several times, tried using verbose mode and running fsck-made no difference. So I've done another archive and install. Why does Apple release complete garbage like 10.5.2? I assume that must have been the cause of both problems, it appears they did not test it properly on enough configurations before releasing it. Wait for 10.5.3 I suppose.

[Cold Warrior]

Did/do you have any hacks installed?

What sort of non-Apple applications or self-installed drivers?

Did you install the graphics update available after updating to 10.5.2?

Have you checked your hard drive for corruption (different than fsck)?

[seanc]

What MacBook do you have? Sounds more like it could be a corruption issue to me, either with the hard drive or RAM. Have you upgraded the RAM recently? Have you run any 'cleaning' or 'space saving' programs?
10.5.2 has caused no such trouble for me, I've been running it since it came out and reboot between Windows and Leopard frequently.

[rhombus]

I have the original (late 2006) MacBook. No hacks, or third party applications installed that would affect start-up. No third party drivers installed. In answer to your question seanc, yes I installed the graphics update too (perhaps that was the cause of the startup problem). Never upgraded the RAM, never ran any space savings programs. I used the Applecare provided Techtool Pro today, negative results.

When the MacBook wouldn't start-up I was able to run fsck by starting in verbose mode. It said 'file system modified' the first time, then the second time I got the 'Macintosh HD appears to be OK' message. I tried resuming the boot sequence by the 'exit' command, but it didn't work-the system froze after lines of error reports came up. I looked in the system log, the same error messages appeared each time I tried to boot the computer, here's where the errors started:

Feb 23 12:01:10 Andrews-MacBook kernel[0]: Resetting IOCatalogue.
Feb 23 12:01:10 Andrews-MacBook kernel[0]: GFX0: family specific matching fails
Feb 23 12:01:10 Andrews-MacBook kernel[0]: display: family specific matching fails
Feb 23 12:01:10 Andrews-MacBook kernel[0]: Matching service count = 1
Feb 23 12:01:10 Andrews-MacBook kernel[0]: Matching service count = 3
Feb 23 12:01:10: --- last message repeated 4 times ---
Feb 23 12:01:10 Andrews-MacBook kernel[0]: display: family specific matching fails
Feb 23 12:01:10 Andrews-MacBook kernel[0]: Previous Shutdown Cause: 3
Feb 23 12:01:10 Andrews-MacBook kernel[0]: GFX0: family specific matching fails
Feb 23 12:01:11 Andrews-MacBook kernel[0]: ath_attach: devid 0x1c
Feb 23 12:01:11 Andrews-MacBook kernel[0]: mac 10.3 phy 6.1 radio 10.2
Feb 23 12:01:12 Andrews-MacBook kernel[0]: yukon: Ethernet address 00:16:cb:cd:b0:51
Feb 23 12:01:12 Andrews-MacBook kernel[0]: AirPort_Athr5424ab: Ethernet address 00:17:f2:4d:e0:46
Feb 23 12:01:12 Andrews-MacBook kernel[0]: AirPort: Link Up on en1
Feb 23 12:01:14 Andrews-MacBook ReportCrash[18]: Formulating crash report for process DirectoryService[11]
Feb 23 12:01:14 Andrews-MacBook com.apple.launchd[1] (com.apple.DirectoryServices[11]): Exited abnormally: Segmentation fault
Feb 23 12:01:14 Andrews-MacBook DirectoryService[22]: Launched version 5.2 (v514.4)
Feb 23 12:01:14 Andrews-MacBook mDNSResponder mDNSResponder-170 (Jan 4 2008 18:04:07)[16]: starting
Feb 23 12:01:15 Andrews-MacBook ReportCrash[18]: Formulating crash report for process DirectoryService[22]
Feb 23 12:01:15 Andrews-MacBook com.apple.launchd[1] (com.apple.DirectoryServices[22]): Exited abnormally: Segmentation fault
Feb 23 12:01:15 Andrews-MacBook com.apple.launchd[1] (com.apple.DirectoryServices): Throttling respawn: Will start in 9 seconds
Feb 23 12:01:15 Andrews-MacBook ReportCrash[18]: Saved crashreport to /Library/Logs/CrashReporter/DirectoryService_2008-02-23-120107_localhost.crash using uid: 0 gid: 0, euid: 0 egid: 0
Feb 23 12:01:15 Andrews-MacBook ReportCrash[18]: Saved crashreport to /Library/Logs/CrashReporter/DirectoryService_2008-02-23-120115_localhost.crash using uid: 0 gid: 0, euid: 0 egid: 0
Feb 23 12:01:23 Andrews-MacBook kextd[10]: writing kernel link data to /var/run/mach.sym
Feb 23 12:01:24 Andrews-MacBook DirectoryService[27]: Launched version 5.2 (v514.4)
Feb 23 12:01:25 Andrews-MacBook ReportCrash[26]: Formulating crash report for process ReportCrash[18]
Feb 23 12:01:25 Andrews-MacBook com.apple.launchd[1] (com.apple.ReportCrash.DirectoryService[18]): Exited abnormally: Segmentation fault
Feb 23 12:01:25 Andrews-MacBook ReportCrash[29]: Formulating crash report for process securityd[24]
Feb 23 12:01:25 Andrews-MacBook ReportCrash[26]: Saved crashreport to /Library/Logs/CrashReporter/ReportCrash_2008-02-23-120116_Andrews-MacBook.crash using uid: 0 gid: 0, euid: 0 egid: 0
Feb 23 12:01:25 Andrews-MacBook com.apple.launchd[1] (com.apple.SecurityServer[24]): Exited abnormally: Segmentation fault
Feb 23 12:01:25 Andrews-MacBook ReportCrash[29]: Saved crashreport to /Library/Logs/CrashReporter/securityd_2008-02-23-120125_Andrews-MacBook.crash using uid: 0 gid: 0, euid: 0 egid: 0
Feb 23 12:01:26 Andrews-MacBook ReportCrash[33]: Formulating crash report for process DirectoryService[27]
Feb 23 12:01:26 Andrews-MacBook com.apple.launchd[1] (com.apple.DirectoryServices[27]): Exited abnormally: Segmentation fault
Feb 23 12:01:26 Andrews-MacBook com.apple.launchd[1] (com.apple.DirectoryServices): Throttling respawn: Will start in 9 seconds
Feb 23 12:01:26 Andrews-MacBook ReportCrash[33]: Saved crashreport to /Library/Logs/CrashReporter/DirectoryService_2008-02-23-120125_localhost.crash using uid: 0 gid: 0, euid: 0 egid: 0
Feb 23 12:01:34 Andrews-MacBook sandbox-compilerd[23]: find_compiler pthread_cond_timedwait e=60 (Operation timed out)
Feb 23 12:01:34 Andrews-MacBook sandbox-compilerd[23]: bootstrap_look_up_per_user failure (kr=49, duration=19.002292) unknown error code
Feb 23 12:01:34 Andrews-MacBook mDNSResponder[16]: WARNING: sandbox_init error Cannot apply profile `(version 1)\n\n; WARNING: The sandbox rule...': Connection refused
Feb 23 12:01:35 Andrews-MacBook DirectoryService[35]: Launched version 5.2 (v514.4)
Feb 23 12:01:35 Andrews-MacBook mDNSResponder[16]: SessionGetInfo(0xffffffff) -> Mach 1102

[turtle777]

I doubt it's 10.5.2 in general, as it is running very smoothly on many people's Macs.

HOW did you reinstall Leopard ? Just over th existing system, or a complete archive & reinstall ?

Yeah, and check the RAM.

-t

[rhombus]

Originally Posted by turtle777 

I doubt it's 10.5.2 in general, as it is running very smoothly on many people's Macs.

HOW did you reinstall Leopard ? Just over th existing system, or a complete archive & reinstall ?

Yeah, and check the RAM.

-t

When I experienced the first problem, I did an archive and install, reapplied 10.5.2 combo, graphics update, so it was a vanilla installation. The second problem occurred 24hrs later after I had shut down my MacBook, and then tried to start it when I arrived on campus. I've subsequently done another archive and install, which fixed the booting problem and I haven't installed any updates. I've checked the RAM using Techtool, negative. I suspect the problem was caused by 10.5.2 or the Leopard Graphics update as I've noticed today similar problems to mine have been reported on Apple.com Discussions.

[seanc]

Feb 23 12:01:10 Andrews-MacBook kernel[0]: GFX0: family specific matching fails
Feb 23 12:01:10 Andrews-MacBook kernel[0]: display: family specific matching fails

Could be a graphics issue. What happens if you don't install the graphics update?

The only other thing I can think of is the hard drive. The original and some later MacBooks had Seagate HDDs which would fail due to the read/write head eventually breaking off although I would have thought it wouldn't work at all if it had this problem.

What manufacturer of HDD do you have and if it's a Seagate, what revision is it?

[rhombus]

The HDD is a 80GB Seagate ST98823AS if that helps. I think I will refrain from installing the graphics update for now, in case it was the cause of the problem. I've seen quite a few reports on the internet today of similar startup problems specifically after installing the Leopard Graphics update.

[disposable]

Wow, I think I have the same problem. Leopard will not show my login and won't let me boot in, all I see is a Grey screen. Fortunately I have Windows XP installed through bootcamp or else I would have lost everything. I believe either the graphics update or the MacBook keyboard update seemed to have triggered my problems. I'll have to wait until I order my terabyte external hard drive to back everything up and re-install Leopard from scratch.

Good luck, I hope you find a fix or Apple fixes this problem.

[rhombus]

You could try using one the recommendations in this thread Apple - Support - Discussions - 10.5.2 Updated and now won't Re-Boot .... Someone suggests disabling mDNSresponder-might work for you.