10.8.2 - mdworker: Unable to talk to lsboxd

[EmpyreanUK]

Kevin

Safe Boot your machine - do nothing until complete -restart as normal - see if that helps with console errors - may even help the sleep issues.

Mac

iMac-iPad-iPhone

Thanks for taking the time to post this advice, whiskymac. I just tried to safe boot my Mac —*I have File Vault enabled, so I had to log in before the OS loaded. As the OS loaded, I got the spinning pin wheel as normal, only it remained on that screen for longer than normal. The system then restarted itself, without the OS progressing beyond the loading screen and displaying the desktop. Is this normal?

 

[netnothing]

So far so good after the safe boot. The only message related to lsboxd is:

Sep 25 18:09:29 lsboxd[218]: @AE relay 4755524c:4755524c

Doesn't happen as frequently as the other message.

I never seemed to have the sleep or spotlight issues, so will be interested if someone who had those can see if the safeboot fixes it or not.

-Kevin

 

[Joesg]

I'll add my name to the list that this bug affects. I first noticed this when going through my console logs to figure out why it takes so long to wake from power nap. I'm not sure if this is part of the reason or not.

I get 100s of these every time I wake from power nap:
mdworker[2357]: Unable to talk to lsboxd
sandboxd[2359]: ([2357]) mdworker(2357) deny mach-lookup com.apple.ls.boxd

 

[whiskymac]

Thanks for taking the time to post this advice, whiskymac. I just tried to safe boot my Mac —*I have File Vault enabled, so I had to log in before the OS loaded. As the OS loaded, I got the spinning pin wheel as normal, only it remained on that screen for longer than normal. The system then restarted itself, without the OS progressing beyond the loading screen and displaying the desktop. Is this normal?

Hi EmpyreanUK

If at all possible - could you disable FV and then try a safe boot.

Mac

iMac-iPad-iPhone

 

[flazcano]

Reinstalling does not work

yesterday i reinstall ML, and after many hours, the problem is back:

Sep 26 13:50:09 flazcano mdworker[2093]: Unable to talk to lsboxd
Sep 26 13:50:09 flazcano sandboxd[2098] ([2093]): mdworker(2093) deny mach-lookup com.apple.ls.boxd
Sep 26 13:50:10 flazcano kernel[0]: Sandbox: sandboxd(2098) deny mach-lookup com.apple.coresymbolicationd

 

[netnothing]

So yesterday after my safe boot......I only had 1 instance of the Unable to talk to lsboxd message.

This morning it occurred again but just twice in the morning. None since.

So clearly something is still causing it....it's just not as frequent.

-Kevin

 

[Joesg]

I'll add my name to the list that this bug affects. I first noticed this when going through my console logs to figure out why it takes so long to wake from power nap. I'm not sure if this is part of the reason or not.

I get 100s of these every time I wake from power nap:
mdworker[2357]: Unable to talk to lsboxd
sandboxd[2359]: ([2357]) mdworker(2357) deny mach-lookup com.apple.ls.boxd

So I booted into safe mode, as was suggested, and these no longer show up in my console logs. I haven't seen a single instance since rebooting. Additionally, my wake times are much improved. I'll keep an eye out in case these return.

 

[EmpyreanUK]

Hi EmpyreanUK

If at all possible - could you disable FV and then try a safe boot.

Mac

iMac-iPad-iPhone

Hi Whiskymac, thank you very much for taking the time to reply!

I retried booting into safe mode, with File Vault still enabled, and the same thing happened: during boot up, while the pinwheel was spinning with the progress bar underneath, the system reset itself. After it had completed booting, I checked the system log, and there were lots of messages regarding safe boot. I didn't have time to try disabling FV and then safe booting at that time, so I left the computer. When I came back, the system log was still open, and I noticed that there were no lsboxd-related messages. After two days, there had only been a couple, so I think whatever was causing it to report these messages so persistently has been resolved by my presumably un- or half-successful safe boot.

At first I thought this had also resolved the issues I was having with the system not going to sleep correctly. However, over the past day or so I have been monitoring the logs and have concluded that the system is in fact still not sleeping, but is just not filling the logs with anything during this idle 'awake' time. I now suspect that the lsboxd issue was not causing the system to remain awake, but because it was anyway awake, the lsboxd problem was able to keep on repeating itself, thus filling the log with error messages.

Regarding the non-sleeping issue, I just used the pmset command in Terminal to review the power settings and to check the status of the so-called 'assertions'. pmset reported that there was one process with an assertion set to 'PreventUserIdleSystemSleep', which is what I presume to be happening with my Mac's sleep problems. Believe it or not, the process in question was iTunes. I've since quit iTunes, and the assertion is no longer reported by pmset.

I'll report back on whether this works or not, but in the meantime, should I make a new thread regarding this? I'm no-longer convinced that at the very least my sleep problems are being caused by lsboxd, which is after all the topic of this discussion.

 

[cetesse]

MacPro 24GB of ram OS X Mountain Lion 10.8.2

Also have the dreaded freeze daily.

I have disconnected USB external hard drive.
Removed SoundFlower extension
And today got the longest usage by not using Chrome

Last set of messages were:

(Any other solutions to try????)

9/27/12 6:51:07.000 PM kernel[0]: Sandbox: sandboxd(20612) deny mach-lookup com.apple.coresymbolicationd
9/27/12 6:51:07.657 PM sandboxd[20612]: ([20611]) mdworker(20611) deny mach-lookup com.apple.ls.boxd
9/27/12 6:51:12.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 890 wr: 890 q_size: 1024 flags: 0x1
9/27/12 6:51:16.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 635 wr: 635 q_size: 1024 flags: 0x1
9/27/12 6:51:17.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 380 wr: 380 q_size: 1024 flags: 0x1
9/27/12 6:51:22.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 125 wr: 125 q_size: 1024 flags: 0x1
9/27/12 6:51:22.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 894 wr: 894 q_size: 1024 flags: 0x1
9/27/12 6:51:32.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 639 wr: 639 q_size: 1024 flags: 0x1
9/27/12 6:51:34.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 384 wr: 384 q_size: 1024 flags: 0x1
9/27/12 6:51:34.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 129 wr: 129 q_size: 1024 flags: 0x1
9/27/12 6:51:38.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 898 wr: 898 q_size: 1024 flags: 0x1
9/27/12 6:51:39.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 643 wr: 643 q_size: 1024 flags: 0x1
9/27/12 6:51:45.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 388 wr: 388 q_size: 1024 flags: 0x1
9/27/12 6:51:49.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 133 wr: 133 q_size: 1024 flags: 0x1
9/27/12 6:51:49.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 902 wr: 902 q_size: 1024 flags: 0x1
9/27/12 6:51:54.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 647 wr: 647 q_size: 1024 flags: 0x1
9/27/12 6:51:54.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 392 wr: 392 q_size: 1024 flags: 0x1
9/27/12 6:51:59.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 137 wr: 137 q_size: 1024 flags: 0x1
9/27/12 6:52:07.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 906 wr: 906 q_size: 1024 flags: 0x1
9/27/12 6:52:08.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 651 wr: 651 q_size: 1024 flags: 0x1
9/27/12 6:52:11.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 396 wr: 396 q_size: 1024 flags: 0x1
9/27/12 6:52:12.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 141 wr: 141 q_size: 1024 flags: 0x1
9/27/12 6:52:16.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 910 wr: 910 q_size: 1024 flags: 0x1
9/27/12 6:52:21.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 655 wr: 655 q_size: 1024 flags: 0x1
9/27/12 6:52:21.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 400 wr: 400 q_size: 1024 flags: 0x1
9/27/12 6:52:26.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 145 wr: 145 q_size: 1024 flags: 0x1
9/27/12 6:52:28.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 914 wr: 914 q_size: 1024 flags: 0x1
9/27/12 6:52:32.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 659 wr: 659 q_size: 1024 flags: 0x1
9/27/12 6:52:36.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 404 wr: 404 q_size: 1024 flags: 0x1
9/27/12 6:52:36.000 PM kernel[0]: [ffffff807e272800][AppleMultitouchDevice::willTerminate] entered
9/27/12 6:52:36.000 PM kernel[0]: [ffffff807e272800][AppleMultitouchDevice::stop] entered
9/27/12 6:52:36.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 149 wr: 149 q_size: 1024 flags: 0x1
9/27/12 6:52:45.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 918 wr: 918 q_size: 1024 flags: 0x1
9/27/12 6:52:46.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 663 wr: 663 q_size: 1024 flags: 0x1
9/27/12 6:52:49.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 408 wr: 408 q_size: 1024 flags: 0x1
9/27/12 6:52:53.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 153 wr: 153 q_size: 1024 flags: 0x1
9/27/12 6:52:53.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 922 wr: 922 q_size: 1024 flags: 0x1
9/27/12 6:53:00.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 667 wr: 667 q_size: 1024 flags: 0x1
9/27/12 6:53:00.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 412 wr: 412 q_size: 1024 flags: 0x1
9/27/12 6:53:05.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 157 wr: 157 q_size: 1024 flags: 0x1
9/27/12 6:53:09.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 926 wr: 926 q_size: 1024 flags: 0x1
9/27/12 6:53:25.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 671 wr: 671 q_size: 1024 flags: 0x1
9/27/12 6:53:33.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 416 wr: 416 q_size: 1024 flags: 0x1
9/27/12 6:53:39.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 161 wr: 161 q_size: 1024 flags: 0x1
9/27/12 6:53:45.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 930 wr: 930 q_size: 1024 flags: 0x1
9/27/12 6:53:50.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 675 wr: 675 q_size: 1024 flags: 0x1
9/27/12 6:54:01.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 420 wr: 420 q_size: 1024 flags: 0x1
9/27/12 6:54:04.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 165 wr: 165 q_size: 1024 flags: 0x1
9/27/12 6:54:08.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 934 wr: 934 q_size: 1024 flags: 0x1
9/27/12 6:54:12.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 679 wr: 679 q_size: 1024 flags: 0x1
9/27/12 6:54:16.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 424 wr: 424 q_size: 1024 flags: 0x1
9/27/12 6:54:20.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 169 wr: 169 q_size: 1024 flags: 0x1
9/27/12 6:54:24.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 938 wr: 938 q_size: 1024 flags: 0x1
9/27/12 6:54:25.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 683 wr: 683 q_size: 1024 flags: 0x1
9/27/12 6:54:31.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 428 wr: 428 q_size: 1024 flags: 0x1
9/27/12 6:54:39.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 173 wr: 173 q_size: 1024 flags: 0x1
9/27/12 6:54:42.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 942 wr: 942 q_size: 1024 flags: 0x1
9/27/12 6:54:42.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 687 wr: 687 q_size: 1024 flags: 0x1
9/27/12 6:54:47.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 432 wr: 432 q_size: 1024 flags: 0x1
9/27/12 6:54:52.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 177 wr: 177 q_size: 1024 flags: 0x1
9/27/12 6:54:54.571 PM mdworker[20619]: Unable to talk to lsboxd
9/27/12 6:54:54.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 946 wr: 946 q_size: 1024 flags: 0x1
9/27/12 6:54:55.000 PM kernel[0]: Sandbox: sandboxd(20620) deny mach-lookup com.apple.coresymbolicationd
9/27/12 6:54:55.516 PM sandboxd[20620]: ([20619]) mdworker(20619) deny mach-lookup com.apple.ls.boxd
9/27/12 6:55:01.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 691 wr: 691 q_size: 1024 flags: 0x1
9/27/12 6:55:05.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 436 wr: 436 q_size: 1024 flags: 0x1
9/27/12 6:55:07.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 181 wr: 181 q_size: 1024 flags: 0x1
9/27/12 6:55:17.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 950 wr: 950 q_size: 1024 flags: 0x1
9/27/12 6:55:19.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 695 wr: 695 q_size: 1024 flags: 0x1
9/27/12 6:55:21.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 440 wr: 440 q_size: 1024 flags: 0x1
9/27/12 6:55:25.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 185 wr: 185 q_size: 1024 flags: 0x1
9/27/12 6:55:26.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 954 wr: 954 q_size: 1024 flags: 0x1
9/27/12 6:55:30.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 699 wr: 699 q_size: 1024 flags: 0x1
9/27/12 6:55:33.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 444 wr: 444 q_size: 1024 flags: 0x1
9/27/12 6:55:35.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 189 wr: 189 q_size: 1024 flags: 0x1
9/27/12 6:55:39.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 958 wr: 958 q_size: 1024 flags: 0x1
9/27/12 6:55:43.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 703 wr: 703 q_size: 1024 flags: 0x1
9/27/12 6:55:49.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 448 wr: 448 q_size: 1024 flags: 0x1
9/27/12 6:55:52.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 193 wr: 193 q_size: 1024 flags: 0x1
9/27/12 6:55:53.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 962 wr: 962 q_size: 1024 flags: 0x1
9/27/12 6:55:57.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 707 wr: 707 q_size: 1024 flags: 0x1
9/27/12 6:55:58.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 452 wr: 452 q_size: 1024 flags: 0x1
9/27/12 6:56:03.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 197 wr: 197 q_size: 1024 flags: 0x1
9/27/12 6:56:07.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 966 wr: 966 q_size: 1024 flags: 0x1
9/27/12 6:56:08.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 711 wr: 711 q_size: 1024 flags: 0x1
9/27/12 6:56:12.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 456 wr: 456 q_size: 1024 flags: 0x1
9/27/12 6:56:13.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 201 wr: 201 q_size: 1024 flags: 0x1
9/27/12 6:56:17.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 970 wr: 970 q_size: 1024 flags: 0x1
9/27/12 6:56:25.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 715 wr: 715 q_size: 1024 flags: 0x1
9/27/12 6:56:27.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 460 wr: 460 q_size: 1024 flags: 0x1
9/27/12 6:56:30.000 PM kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 367) rd: 205 wr: 205 q_size: 1024 flags: 0x1
9/27/12 6:56:52.686 PM mdworker[20622]: Unable to talk to lsboxd
9/27/12 6:56:53.109 PM sandboxd[20623]: ([20622]) mdworker(20622) deny mach-lookup com.apple.ls.boxd
9/27/12 6:56:53.000 PM kernel[0]: Sandbox: sandboxd(20623) deny mach-lookup com.apple.coresymbolicationd

 

[MacInMotion]

I'm having similar problems with my Retina MBP (first edition).

Seeing stuff in the logs like:

sandboxd[9950]: ([9949]) mdworker(9949) deny mach-lookup com.apple.ls.boxd
mdworker[9960]: Unable to talk to lsboxd
kernel[0]: Sandbox: sandboxd(9985) deny mach-lookup com.apple.coresymbolicationd

Then when the screen saver tried to kick in:

9/26/12 4:49:48.236 PM WindowServer[83]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
9/26/12 4:49:48.237 PM loginwindow[57]: find_shared_window: WID -1
9/26/12 4:49:48.237 PM loginwindow[57]: CGSGetWindowTags: Invalid window 0xffffffff
9/26/12 4:49:48.237 PM loginwindow[57]: find_shared_window: WID -1
9/26/12 4:49:48.237 PM loginwindow[57]: CGSSetWindowTags: Invalid window 0xffffffff
9/26/12 4:49:48.241 PM coreservicesd[28]: Application App:"loginwindow" [ 0x0/0x1001]  @ 0x0x7f8cd3d05860 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x6b66b6:) ), so denying.
9/26/12 4:49:48.241 PM WindowServer[83]: [cps/setfront] Failed setting the front application to loginwindow, psn 0x0-0x1001, securitySessionID=0x186a5, err=-13066
9/26/12 4:49:48.973 PM WindowServer[83]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x042803c0 device: 0x10e7e7320  isBackBuffered: 1 numComp: 3 numDisp: 3
9/26/12 4:49:49.000 PM kernel[0]: NVDA(OpenGL): Channel exception! exception type = 0xd = GR: SW Notify Error
9/26/12 4:49:49.000 PM kernel[0]: IOVendorGLContext::ReportGPURestart

And then the screensaver froze (just the background image came on) and the pointer turned into the spinning beach ball and there was nothing I could do but hard power-down.

I submitted a support request to AppleCare, they said it was "probably a corrupt screen saver plist" and had me delete it. Yeah, right.

Anyway, since then I've noticed spotlight is almost always re-indexing.

This all started immediately after updating to OS 10.8.2:

MyMac.local installd[25879]: PackageKit: packages=(
	    "PKLeopardPackage <file://localhost/Library/Updates/041-7512/OSXUpd10.8.2Patch.pkg>",
	    "PKLeopardPackage <file://localhost/Library/Updates/041-7512/RemoteDesktop.pkg>",
	    "PKLeopardPackage <file://localhost/Library/Updates/zzzz041-6901/MobileDevice.pkg>",
	    "PKLeopardPackage <file://localhost/Library/Updates/zzzz041-6901/iTunesX.pkg>",
	    "PKLeopardPackage <file://localhost/Library/Updates/zzzz041-6901/CoreFP.pkg>",
	    "PKLeopardPackage <file://localhost/Library/Updates/zzzz041-6901/iTunesAccess.pkg>",
	    "PKLeopardPackage <file://localhost/Library/Updates/zzzz041-6901/iTunesLibrary.pkg>"
	)

I'll try removing

/Library/Caches/com.apple.coresymbolicationd
/System/Library/LaunchAgents/com.apple.afpstat.plist

and see if that helps.

 

[Shazaam!]

I removed Cocktail 6 from 10.8.2 and ran DiskWarrior.
No More mdworker: Unable to talk to lsboxd.

 

[MacInMotion]

I'll try removing

/Library/Caches/com.apple.coresymbolicationd
/System/Library/LaunchAgents/com.apple.afpstat.plist

and see if that helps.

Nope, that didn't help.

 

[Shazaam!]

Mak sure you use Cocktail's uninstaller.

 

[netnothing]

Well after the Safe boot....the messages went away for a week. However, as of this morning they are back.

Guess we'll have to wait until 10.8.3 for a fix.

-Kevin

 

[canhaz]

I've been having massively annoying issues like these on ML.

• 10 minutes to login after typing my password
• Black screen after wake (requires hard reset)
• Plugging thunderbolt display freezes everything (requires hard reset)
• lsboxd messages

FWIW I run FV enabled.

 

[petsounds]

If I filter system.log by 'lsboxd', I get the "unable to talk..." message basically every 2-4 minutes. Clearing caches, safe boot, none of that has worked. If anyone is on the OS X beta program, they might want to bring up the issue there to see if any engineers have input on this. Does anyone know what the lsboxd utility is responsible for?

 

[ernani]

Hi everyone,

I too have had most the problems mentioned in this forum, right after upgrading to ML 10.8.2, with the most prominent being the blank screen after wake, which occurred quite regularly. This made me start examining the Console log, where I found all those messages regarding lsboxd and coresymbolicationd.

I managed to make those messages disappear for about 5-6 days after performing a safe boot, as suggested here. Unfortunately, they did come back, but the system doesn't seem to be affected.

As for the "blank screen after wake" problem, I *may* have found a solution via the Hackintosh community. By a more thorough examination of the console log, you will notice that your mac wakes up more or less on a schedule to perform various "maintenance" chores, even if power nap is disabled or not supported, or simply because of power fluctuations or usb devices being (dis)connected. When this happens, it enters a "dark wake" state. The screen remains blank, the OS does what it is supposed to do, and then attempts to sleep again. All the affected systems remain in this "dark wake" state, not being able to either sleep or perform a regular wake.

What I did is to disable dark wakes all together, by editing /Library/Preferences/SystemConfiguration/com.apple.Boot.plist and entering the following kernel flag:

<key>Kernel Flags</key>
<string>darkwake=0</string>

Since then (almost a week), I found that my macbook did wake up a couple of times by its own, but it was a normal wake (the screen was on), so that I could easily put it back to sleep again, avoiding the hard reset.

Now my macbook never goes to sleep on its own (for instance when it is sleeping and I disconnect my iphone when it completes its charging cycle), which is somewhat inconvenient, but I don't have to do hard resets all the time.

If you guys try it, please let me know if it helps.

 

[murphychris]

re: Unable to talk to lsboxd

I'm seeing this on an index rebuild, on 10.7.5. And the estimate for the rebuild is 6 days for a paltry amount of data. So something is fakaked with Spotlight (yet again) I find spotlight beyond irritating. 6 days for a f'n index rebuild is insane.

 

[MarshallVillage]

Kevin

I had the same problem - Safe Boot is your friend.

Mac

-iMac-iPad-iPhone

Experienced issues after upgrading to OS X 10.8.2 and Mail.app 6.1...Safe Boot fixed my Mail.app extreme slowness...THANKS whiskymac!

Checking the Console.app I see one notable difference. The following item is now gone. [TIMESTAMP] mdworker[17194]: Unable to talk to lsboxd

 

[wprowe]

This appears to be related.

http://apple.stackexchange.com/ques...ght-and-time-machine-since-10-7-5/65667#65667

The Spotlight mdworker config files appears to be missing some entries. It does not eliminate the "Unable to talk to lsboxd" messages, but it does eliminate the ones associated with com.apple.ls.boxd.

I think Apple hasn't completely worked out all of the kinks with sandboxing and their own services getting the access they need (like Spotlight).

 

[netnothing]

Just to update.....after the safe boot, things were fine for about a week....now my console is littered with the Unable to talk to lsboxd messages.

I also notice that the /Library/Caches/com.apple.coresymbolicationd folder is back.

Guessing we have to wait for 10.8.3 to have Apple fix this mess.

-Kevin

 

[murphychris]

Yesterday, I posted a variation on the response below in the Apple Discussion Forums, where you can also read other user reports about this problem, and how well this "fix" I've come up with is working for others.
https://discussions.apple.com/thread/4322106?tstart=0

------

I might have a working "fix". Based on the constant stalling on sandbox-cache.db I decided to take a chance and delete all folders found in /var/folders. What I actually did, in order:

Quit all applications except Terminal, issued the following two commands:

sudo mdutil -i off /
sudo mdutil -E /
sudo rm -Rf /var/folders/*

Reboot.

sudo mdutil -i on /

There were no further stalls on sandbox-cache.db according to opensnoop, and no further lsboxd complaints in Console. mds and mdworker processes have been very busy, typically 40-100% CPU, unlike before. And now the index estimate is variably saying 6 to 19 minutes for completion instead of 3 days to 5 weeks. It ultimately completed indexing in 45 minutes, which is normal for my system. Previously it had been running for 3 days and was maybe 20% complete.

Now, blowing away the folders in /var/folders may have other consequences, possibly negative, for sandboxing. But the files therein appear to be recreated from scratch after reboot to no ill effect or complaints in Console. But let's just say, the suffering bleeding edgers may end up bleeding more by trying this. Any volunteers?

 

[ubergeek72]

Yesterday, I posted a variation on the response below in the Apple Discussion Forums, where you can also read other user reports about this problem, and how well this "fix" I've come up with is working for others.
https://discussions.apple.com/thread/4322106?tstart=0

------

I might have a working "fix". Based on the constant stalling on sandbox-cache.db I decided to take a chance and delete all folders found in /var/folders. What I actually did, in order:

Quit all applications except Terminal, issued the following two commands:

sudo mdutil -i off /
sudo mdutil -E /
sudo rm -Rf /var/folders/*

Reboot.

sudo mdutil -i on /

There were no further stalls on sandbox-cache.db according to opensnoop, and no further lsboxd complaints in Console. mds and mdworker processes have been very busy, typically 40-100% CPU, unlike before. And now the index estimate is variably saying 6 to 19 minutes for completion instead of 3 days to 5 weeks. It ultimately completed indexing in 45 minutes, which is normal for my system. Previously it had been running for 3 days and was maybe 20% complete.

Now, blowing away the folders in /var/folders may have other consequences, possibly negative, for sandboxing. But the files therein appear to be recreated from scratch after reboot to no ill effect or complaints in Console. But let's just say, the suffering bleeding edgers may end up bleeding more by trying this. Any volunteers?

Seems to have worked for me. Disk is now very busy and Spotlight says it can have the job done in 47 minutes.

 

[gwang73]

Just to update.....after the safe boot, things were fine for about a week....now my console is littered with the Unable to talk to lsboxd messages.

I also notice that the /Library/Caches/com.apple.coresymbolicationd folder is back.

Guessing we have to wait for 10.8.3 to have Apple fix this mess.

-Kevin

My system is the same as yours. I deleted the /Library/Caches/com.apple.coresymbolicationd folder again and restarted in safe-mode and it's temporarily fixed again. I may try modding the mdworker files as suggested in another post but I'm bit a hesitant modding system files at the moment.

 

[murphychris]

My system is the same as yours. I deleted the /Library/Caches/com.apple.coresymbolicationd folder again and restarted in safe-mode and it's temporarily fixed again. I may try modding the mdworker files as suggested in another post but I'm bit a hesitant modding system files at the moment.

#47 causes hidden cache files to be removed. They appear to be recreated upon restart. There are no modifications of files, just removal. So far there have been no negative consequences.