Previous 1 2 3 Next 44 Replies Latest reply: Oct 1, 2015 4:27 AM by 64Anthonyp Go to original post
  • Topher Kessler Level 6 (9,865 points)

    What type of Mac do you have (Model and year issued)?

  • Jerome Meyer Level 1 (0 points)

    It's a MacBook Air 13-inch, Mid 2012 (MacBookAir5,2).

  • Topher Kessler Level 6 (9,865 points)

    Jerome Meyer wrote:


    It's a MacBook Air 13-inch, Mid 2012 (MacBookAir5,2).


    Ok that suggests one other possibility. If the 10.8.2 combo update you have was downloaded before November 30 then you will have a version that will not run on some Mac models, so try re-downloading it to get a more updated build.


    Apple did issue a separate update for some of these systems (, but yours is not included in this list. You can try installing this one, but the installer may prevent you from doing so.


    Additionally, Apple has a supplemental update for OS X 10.8.2 that addresses some keychain accessibility issues, which while I do not suspect is at play here, could be involved. This update is available here:, and is separate from the main OS X 10.8.2 update.

  • rhangelxs Level 1 (0 points)

    I have the same issue. My logs may be usefull?

  • bassham Level 1 (0 points)

    Anyone find a solution to this? I have the same problem.


    I did - sudo launchctl unload -w /System/Library/LaunchDaemons/


    that stopped it for now, but it would be nice if location services would work too.

  • saringer Level 1 (10 points)

    After running into the same problem on a 2012 rMBP upgraded to 10.8.2 I seem to have found a solution. First, do not touch the /var/db/locationd folder or its contents. It only seems to store the System Preferences settings i.e. which apps are allowed to use locationd.


    I first stopped the service with: sudo launchctl unload -w /System/Library/LaunchDaemons/


    Then, I did: sudo rm -Rf /var/folders/zz/zyxvpxvq6csfxvn_n00000sm00006d


    (I got the path from the Console entries and ls -la showed it was owned by _locationd. I'm not certain this path is the same for everyone but it did match Jerome's log post above)


    Finally start the service: sudo launchctl load -w /System/Library/LaunchDaemons/


    This got rid of the errors in my logs and location services now seems to be working fine.


    Now just have to figure out all the "Unable to talk to lsboxd" errors!

  • Jerome Meyer Level 1 (0 points)

    This worked for me too!

    However it did not fix it entirely: the 'Enable Location Services' box won't stay checked, no matter how many times I try:

    2013-02-02 06.10.37 pm.png

  • Bertg Level 1 (5 points)

    I can confirm that deleting /var/folders/zz/zyxvpxvq6csfxvn_n00000sm00006d fixes this problem. Do note that a reboot afterwards is also needed.

  • Bertg Level 1 (5 points)

    I need to retract my statement.

    After an other reboot the "Enable location services" keeps getting unchecked. I'll post back if i figure something out.

  • Jerome Meyer Level 1 (0 points)

    I may have found a solution, thanks to this (seemingly unrelated) post.


    Bottom line: running the command below fixed the Location Services checkbox getting automatically unchecked.


    /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -seed -r
  • Jerome Meyer Level 1 (0 points)

    Spoke too fast... It was working fine yesterday but the issue reappeared today.

  • Bertg Level 1 (5 points)

    I finally got it working. After applying the fixes suggested in this thread I did 2 more things:


    • Install the latest combo update of the os
    • After seeing the message "could not open write stream for /var/db/locationd/clients.plist" I also fixed the permissions of the "/var/db/locationd/" fodler using the following command: "sudo chown -R _locationd:_locationd  /var/db/locationd/" (this command will ask for your administartor password)


    Has been running smooth for the last few hours

  • yorgerson Level 1 (0 points)

    Hi, I got working (at least for now), apparently the problem is with the client.plist file.  I did the following steps:


    1. stop location service --> sudo launchctl unload -w /System/Library/LaunchDaemons/
    2. chabge directory --> cd /var/db
    3. move the original locationd folder to locationd.old --> sudo mv -R ./locationd ./locationd.old
    4. copied back --> sudo cp -R ./locationd.old ./locationd
    5. change permision to locationd folder to delete client.plist file --> sudo chmod 755 ./locationd
    6. delete file --> sudo rm client.plist
    7. change permision back --> sudo chmod 750 ./locationd
    8. change ownership --> sudo chown -R _locationd:_locationd ./locationd
    9. start location services --> sudo launchctl unload -w /System/Library/LaunchDaemons/
    10. enable location services
    11. restart Mac
    12. check that location service still enbled and monitor with console just to make sure that locationd is not crashing


    I hope it helps.

  • yorgerson Level 1 (0 points)

    It's been 3 days and everythin still working... No more locationd error message repeating every few seconds and location service is working properly. 

  • 64Anthonyp Level 1 (0 points)

    Hey, after weeks of searching for weeks after El Capitan Beta upgrade, you've helped me fix the same problem of the location checkbox not staying checked for longer than 1/2-a-second! Thank you.

    Step 1 & 2 were fine, but Step 3 said it didn't recognise the location of the folder. I ignored that and went through all the steps, to no avail. So, to reload everything I changed the command for Step 9 to:

    sudo launchctl load -w /System/Library/LaunchDaemons/


    In other words, "unload" was changed to "load".


    Now, it works...finally! Thank you!

Previous 1 2 3 Next