My Apple computer hardware has recently been bothered by several unrelated germ — ranging from merry sound loss on my Mac Pro to free space mysteriously go away from my iPad . While I ’ve figured out satisfactory employment - arounds for most of these symptoms , they still defy a unadulterated and permanent solution . Here are a quartette of the unity that have frustrated me the most :
Alert sound loss
Periodically , my 2009 Mac Pro appear to stop recreate snappy well-grounded issue . I typically first take notice of the job because Office for Mac ’s Outlook stops playing the speech sound that accompany sent or receive mail . Finder alerting sound similarly vanish . Sounds in most other position , such as euphony in iTunes , continue to play just fine . Of possible relevance , I have extraneous speakers connected to my Mac via Line Out .
When this sound loss pass off , I can get things work again via the following mend :
1 . Go to Sound System Preferences . Switch the source for “ Play legal effects through . ” In my case , I switch from Line Out to Display Audio and then back to Line Out .
2 . If demand , lower or raise the Alert Volume , as a terminal bitch in the trouser .
now after doing this , the Mac ’s warning signal sounds reappearance . Oddly , the first thing that go on is that a long drawstring of alerts plays — which is the backlog of all the alarum that had not act as during the menses of silence .
A web search turned up onerecommended alternative solution : Launch Activity Monitor , settle the coreaudiod process and quit it . The process will immediately relaunch . Your sound should now be back . I suspect that my System Preferences work - around and take leave coreaudiod are attain the same endpoint , but from different directions .
Unfortunately , within the next calendar week or two , the symptom invariably returns on my Mac . web reports substantiate that this reappearance also occur for other users plagued by the bug . There is likely no surefire permanent fix .
One Apple Support Communities threadsuggests that putting the Mac to catch some Z’s may trigger the symptom . Of course , not everyone who puts their Mac to sleep has this problem . The ultimate movement , like the ultimate fix , remains unknown .
Trailer movie downloads fail
I wish to carry through my favorite movie dawdler to my hard parkway , for loose later access . To do so , I go toApple ’s Movie Trailers webpage , select the desired movie and call up the menu that lists the Download items . After I select a single file to download , the trailer opens up in QuickTime Player , where I can export the file cabinet to my driveway .
At least that ’s how thing worked until last week . Now , whenever I select a prevue to download , QuickTime Player opens but the trailer never shows up . This happens with every trailer on Apple ’s site . It happen whether I get at the trailer from Safari or Firefox .
Searching online for answers , I found a few suggestions . One threadsaid to make certain that “ Enable Plug - Hoosier State ” was checked in the Security yellow journalism of Safari ’s Preferences . Another order to make indisputable that no Safari extension that had any “ click - to - load ” function was enable . Given that the symptom is not restrict to Safari on my drive , you should n’t be surprised to learn that neither of these solutions put to work for me .
Still , I was able to make out up with a workplace - around . While it ’s less convenient than just clicking the item in the webpage fare , at least it works :
1 . From the menu that shows the download data file options , control - click the want item to bring up its contextual carte du jour .
2 . From the contextual bill of fare , select Copy Link .
3 . Launch QuickTime Player . From the File menu , select Open Location . glue the simulate link and click Open .
The trailer should open and play . you’re able to now save it via the File menu ’s Export command , just as you do if the preview had unfold straight from the web web web browser .
iOS device “over-capacity”
Last week , when I link up my iPad to iTunes , the Capacity graphic ( that you see at the bottom of the windowpane when the iPad is select ) astonishingly indicated the iPad was “ Over Capacity . ” It was over capacity by more than 11 GB ! I was surprised . antecedently , it had not even been close to content . As far as I knew , I had done nothing to importantly increase the iPad ’s data point storage .
In studying the Capacity graphic , I notice two unusual person . First , the Photos category ( which had held about 5 GB of data ) had disappear . Second , the Other category had balloon to more than 10 times its former size , all account for why the iPad no longer seemed to have any free infinite left .
A hunt of the vane break several possible fixes , ranging from simplyquitting and relaunching iTunesto a complete erase of the machine via the Restore option on the iPad ’s Summary silver screen .
When simple solution such as relaunching iTunes did not work for me , I opted for a middle primer coat : I choose Restore from Backup … via the contextual menu for the equipment ’s lean in the remaining - side pillar of iTunes . This avoids the more time - consuming utter restore that would have required a refreshing install of the firmware .
The middle ground mess work ! I did have some initial glitches get the iPad to resume after the restore ( I ’m going to gloss over the details here as I cogitate they are improbable to be common ) . When the iPad finally did dispatch its restart , the “ over capability ” error had vanished . Things were back to normal .
The consensus view is that data in the Other section mainly represents temporary file . Occasionally , something may go wrong and these single file stop getting removed when no longer needed . As the files accumulate , available free space declivity . Unfortunately , I could n’t find an account of what exactly go wrong or how to preclude it . So all I can do is hope that the problem does not repeat .
Unable to talk to lsboxd
Recently , when I happened to watch the Console log for my Mac Pro , I noticed a repeat serial of error messages that I had never seen before :
mdworker : ineffective to babble out to lsboxd
sandboxd : mdworker deny mach - lookup com.apple.ls.boxd
accord to several World Wide Web postings ( such as this one ) , these messages first started popping up after installing Mountain Lion 10.8.2 . Some drug user ( include myself ) have no symptom associated with these messages . Others account problems pasture from a failure of the Mac to wake from sleep to random re - indexing of Spotlight ( which is understandable , as mdworker is part of the underlying indexing software for Spotlight ) .
A mending that appear to eliminate ( or at least immensely reduce the frequency of ) these message is tostart up in Safe Modeand , when complete , restart again as normal . During a Safe Boot , the Mac pressure a directory bank check of your campaign , making repairs as needed — similar to what you could do from Disk Utility . A Safe Boot also deletes assorted irregular cache files . I ’m think that one of these action at law account for why a Safe Boot has a beneficial effect here .
As to the precise reason that the error notification come about in the first place , once again no one seems to have a hint .
