5037 Views 12 Replies Latest reply: Apr 26, 2012 10:18 AM by Al Berman
Solved. I deleted the com.apple.batteryd.plist file and then did a Safe Boot to reset all caches and logs. I took the easy way out and migrated all of my stuff from my old computer to my new MBAir--and I knew I would be dealing with isolated issues like this.
Looking at some more of the console output, I'm going to have to trash a couple of additional system preference files. I wish Apple would provide an option to NOT migrate any system preferences when migrating info to new hardware. This certainly isn't the first time this has happened.
My parents new 13'' MacBook Air (late 2010) would not fall asleep. After resetting the SMC to no avail I checked the console and saw the exact same message. After deleting the plist and rebooting the machine it is falling asleep now.
I never installed any third-party program relating to the battery and there is a folder called /usr/local however there is no sub-folder libexec nor did a "locate" in Terminal find the daemon batteryd.
Came across a similar thread on the Japanese Apple discussion forum (clicky). Since I cannot read Japanese I can only guess at what the various posts say. There seems to be talk about it being an Apple software related issue specifically regarding the HAL.
I checked on my MacBook Pro (mid 2010) and there is no such plist. Will check another 13'' MacBook Air when I get the chance.
My MacBook Air out of the box: no software other than Microsoft Office 2011 installed, had this problem. The file to remove or delete is /System/Library/LaunchDaemons/com.apple.batteryd.plist.
In Terminal, type
sudo rm /System/Library/LaunchDaemons/com.apple.batteryd.plist
Then enter your login password, and then you will need to reboot in Safe Mode (hold down the Shift key while restarting).
The batteryd.plist file itself is clearly nonsense: the contents certainly don't make sense. I expect that it is Apple's mistake in the image that they put on new Macbook Airs.
I'm going to use this thread for a similar topic, but it regards iStat.
I'm getting this group of messages constantly repeating every 5 seconds in the Console:
3/16/11 5:03:17 AM com.apple.launchd (com.bjango.istatlocaldaemon) posix_spawn("/Library/Application Support/iStat local/iStatLocalDaemon", ...): No such file or directory
3/16/11 5:03:17 AM com.apple.launchd (com.bjango.istatlocaldaemon) Exited with exit code: 1
3/16/11 5:03:17 AM com.apple.launchd (com.bjango.istatlocaldaemon) Throttling respawn: Will start in 10 seconds
3/16/11 5:03:19 AM com.apple.launchd.peruser.501 (com.bjango.istatlocal) posix_spawn("/Library/Application Support/iStat local/iStatLocal", ...): No such file or directory
3/16/11 5:03:19 AM com.apple.launchd.peruser.501 (com.bjango.istatlocal) Exited with exit code: 1
3/16/11 5:03:19 AM com.apple.launchd.peruser.501 (com.bjango.istatlocal) Throttling respawn: Will start in 10 seconds
I used to have iStat on my machine, but I deleted it using AppZapper a while back. I repair disk permissions every so often, so I'm not sure if it's a permissions issue. Is there still a file on my hard drive that I need to delete?
Message was edited by: Mr. Magoo
I am having kernel panics on my new Macbook Air. I got one a week ago and it started with the panics and I got a replacement but now this one is also doing it. It happens when I try to wake it from sleep every morning. I don't seem to have this battery file on my system at all. When I run a console report, I get this same message you are talking about here. I was going to try deleting the plist file but it's simply not there at all. Could this be the problem? The report shows it keeps trying to access that file but it keeps erroring.
Are you sure you don't have that file on your system? For it to show up in a Finder "Find" you have to enable showing system files. Otherwise, you won't find it. It's been long enough that I can't remember the path to the file. Try looking in YourBootVolume/Library/Preferences and YourBootVolume/Library/Preferences/SystemConfiguration.
Also, you could try installing the combo update for 10.6.7.
If nothing works, reinstall the operating system from your USB Key and then install the 10.6.7 combo updater.