Hot answers tagged error
10
A BSOD is the equivalent of kernel panic in unix and unix-like OSes. From the wiki article:
In Unix-based operating systems, a similar term is kernel panic.
That said, I've seen the following image two times over the past 3-4 years. This is a kernel panic screen, as described in this support article.
9
From your screenshots, it looks like you had a kernel panic. A kernel panic is an action which an OS takes due to a fatal error. More info on Wikipedia about kernel panics.
From Apple's support doc about kernel panics:
In most cases, kernel panics are not caused by an issue with your Mac. They are most likely caused by an issue external to your Mac. If ...
7
Just change date to January 2012 or something, it will install just fine. The certificate expired in March.
Updated, steps:
turn off automatic synchronization of date & time
change actual date of the system to 01.01.2012 (for example, prior to
26.03.2012)
install the Xcode
turn the automatic synchronization back on.
5
The root of the cause
Time Machine backups are protected at kernel level -- on a verbose boot it's possible to spot in the first screenful of text a TMSafetyNet.kext extension being loaded.
This ensures the integrity of your backups. Access control provisions
are applied via a kernel extension located at
/System/Library/Extensions/TMSafetyNet.kext
...
5
Individual crash reports are stored in ~/Library/Logs/CrashReporter but there is a system wide log collection tool called sysdiagnose.
Once you start experiencing the issue, hold down the
4 control keys and then press the period "." key. shift+control+option+command+.
After about 15 seconds, a Finder window will open with a sysdiagnose file highlighted.
...
4
The error occurs when an application using Python symbol mappings in Mac OS X is not able to connect to a (previously) networked drive, Time Machine, Bonjour, shared or remote drives, etc. (nwnode). It's a depreciated method, which mostly is why Lion displays the error. Even if you don't use Time Machine, this error can occur, either from an os upgrade or ...
4
It's an old-style kernel panic report. When the kernel crashes, there's no way to log what happened ('cause logging requires a working filesystem, which is part of the kernel...), so OS X used to dump the crash info onto the screen buffer.
In OS X v10.2, they switched to a system where it stores the crash info into PRAM, and displays a message that "You ...
4
I use Alfred, a utility similar to Quicksilver. I had previously configured it to search /Volumes/Storage for apps, but never told it to stop trying to index that volume once I migrated to the new machine.
I removed the /Volumes/Storage entry from Alfred's list of directories to index, and now the console messages have stopped.
4
It could be a corrupt USB kernel extension. I'd try booting to Safe Mode:
Turn off your Mac.
Turn it back on and before you see the Apple logo on your screen, press and hold the Shift key until the Apple logo appears.
A progress bar should appear below the Apple logo - during this time your Mac is performing a directory check and loads only necessary ...
4
Generate a system report (in Lion: About this Mac-> More Info -> System Report, or do a Spotlight search for System Information if you allow Spotlight to index applications.)
Click on USB; then look for the bus ID mentioned. Under that bus, look through the Location IDs of each device; this field is "Addr" in the error logs. Note that location IDs are ...
4
I was experiencing the same problem: unable to purchase or update any items from the App Store, with an error code (13).
I came across another thread here - Cannot Install or Update Apps in App Store - Error 13 app-store-error-13 - which basically suggests deleting a cookie-preferences file for the App Store. I tried it, and it indeed worked for me.
The ...
4
Most of the time, this means there is something wrong with you creditcard information. So do as told and contact iTunes to get rid of the message.
With no screenshot or further information, it's hard for us to provide a solution.
4
This seems to be a problem with permissions in the bundle itself. Usually the execution flag doesn't get carried over from the DMG image.
Try, for the sake of curiosity to set the execution flag like this:
chmod +x /Applications/RubyMine.app/Contents/MacOS/<name of the app>
Note: replace <name of the app> with the name of the app (it will ...
3
According to this thread at Apple, this is a bug. This means it will hopefully be fixed in a coming update to OS X.
In the meantime, you have to relaunch the Finder, which you can do either through force quit (⎇⌘⎋, or through the menu), or by less violent means by quitting it normally, which you must first activate through the following command issued in ...
3
According to Apple's official documentation, it is by design that shell scripts invoked from AppleScript's do shell script action do not inherit the $PATH variable from your login shell's environment.
Accordingly, Apple instructs users to use full paths to commands when invoking shell scripts from AppleScript rather than relying on the $PATH variable in ...
3
Get into DFU mode and do a restore in iTunes.
For DFU mode:
Turn the iPhone off (not needed in this case :)
Push the sleep button for 3 seconds (Apple logo should appear)
Push both buttons for 10 seconds (Apple logo should disappear)
Release the sleep/wake button and hold the home button for at least 15 seconds.
Nothing will show up on the screen, but ...
3
There are various google results for ejecting volumes on sleep, which should solve this problem.
First, write yourself a shell script to eject the volume. You could avoid setuid bits by using apple script.
#!/usr/bin/osascript
tell application "Finder" to eject (disks where name = "VOLUME")
Next, install the SleepWatcher tool and configure ~/.sleep or ...
3
Yes. If you go to the Issue Navigator (cmd-4), you'll see a list of build warnings and errors. You can select one from the list and hit cmd-c. You'll get something like this:
/Users/dave/Developer/Cocoa/EmptyFoundation/EmptyFoundation.m:180:15:{178:2-178:6}{178:2-178:7}: warning: conversion specifies type 'unsigned long long' but the argument has type ...
3
I have received the same "[Application] is damaged and can’t be opened." error when trying to run unsigned applications in Mountain Lion. Notably Davmail.
Try the "Allow applications downloaded from: Anywhere" setting in the "Security & Privacy" System Preferences pane :
For whatever reason you may be running an old, unsigned version of the app.
3
This should be fairly easy to track down with the sysdiagnose tool.
When you get a browser wedged and spitting errors, open terminal and add the browser name as an argument to the script: (so if Safari is crashing)
sysdiagnose Safari
This tool will call sudo which needs you to type your password (it won't show to the screen, so type it slowly if you are ...
2
bckbck is correct in terms of the letter of the law. All sales are final. However, your friend may have some luck contacting iTunes customer service and explaining the situation. They're aware that mistakes happen, and are sometimes happy to rectify them for you - though they are not obliged to do so.
All iTunes customer service is carried out via email. ...
2
Open the AppleScript Editor found in /Applications/Utilities.
Paste in the following three lines:
tell application "Microsoft Outlook"
delete every message of outbox
end tell
Click the Run button at the top and this should delete every message in your Outbox.
2
This is a common error. The iCal auto setup has created an incorrect address for you. There should be no "slash" / at the end of the address i.e. it should be
/calendar/dav/youremail@domain.com/user
To fix it, go to Preferences / Accounts and change the address, removing the final / from the Server Path setting.
AFAIK Lion no longer has this bug.
2
If you can see it in a screenshot, it's likely something with the video signal being sent from the GPU. This could be a problem with the GPU itself or some kind of weird software issue. The best way to tell is to try booting to an external OS like your recovery partition or an OS on an external hard drive to see if it occurs there as well. If it does, it's ...
2
I just fixed this by deleting a large video from my iPhone.
Even though I still had about 3 GB left, it seems that iTunes wants there to remain some free space on the iPhone before syncing.
Once I had about 4 GB left, it started syncing again normally.
I hope this helps someone, and for god's sake Apple you could've included a less cryptic error message ...
2
The ssh tool stores known remote computer IP address and remote ssh key identification in the ~/.ssh directory.
You can read up on this by consulting the manual page on your mac man ssh or on the internet.
You may need to read the entire article and do some follow up research if this is your first exposure with ssh - but the relevant section for the ...
2
The Apple Support Page for this error, "iTunes: Error 13019 during sync," gives quite a few solutions. The first one is to make sure you're on the most recent version of iTunes (which you stated that you are). On that page, you'll notice that there are some drop-down arrows that reveal more suggestions. The second one tells you to disable Voice Memo syncing. ...
2
You can do either of
remove /usr/local/lib/libxml2.2.dylib, copy a working libxml2.2.dylib from another Mac with the same OS X version and recreate the symlinks to look like the directory listing below
reinstall OS X Lion on top of the existing installation and reapplying all the system updates.
get libxml2.2.dylib from your backup and apply option 1
PS: ...
2
For a similar problem, with the (Java) application Sawmill, it was sufficient to "Allow applications downloaded from: Anywhere." I got the "damaged" error when I tried to run it; then I changed that setting to Anywhere; and now I don't get that error anymore. Looks like a bug in Mountain Lion, sort of: the error message could be a lot better, e.g., ...
2
I had the same problem on my Mac running OS X Mountain Lion 10.8.2.
I tried:
Installing/updating to the newest version of Sun Java.
Re-downloading a different Eclipse Package.
Re-installing Eclipse.
None of these things worked.
I was using The Unarchiver 3.3 to unarchive the tar.gz archive—this was the problem. I right clicked the archive and selected ...
Only top voted, non community-wiki answers of a minimum length are eligible
