Tag Info

Hot answers tagged

29

In Terminal, run "xattr -rc /Volumes/Application.app", that should fix it (naturally, replace "/Volumes/Application.app" with your actual application path. No need to disable GateKeeper.


13

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 ...


12

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.


12

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 ...


11

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. ...


10

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.


10

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.


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

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.


6

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 ...


6

Apple sysdiagnose This shell script(on 10.8 and lower) and executable program by the same name on 10.9: gathers system-wide diagnostic information is integral to OS X Lion and greater is not available as a separate download is not open source (I have asked Apple to make it so). Preparing for the keyboard-only approach to sysdiagnose In Terminal, run ...


5

If you never want to see the crash report dialogs, there is a preference to disable them: defaults write com.apple.CrashReporter DialogType none Log out and back in to apply the changes.


5

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 ...


5

Too bad i was posting before doing my own checking. The solution was simple and shall be presented here for others who have the same issue: Simply launch Viber and go to Preferences, there, tell Viber not to launch on system startup. It will remove its LaunchDaemon entry and the error will disappear. Needless to say, Viber should address this issue in ...


4

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 ...


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

In my case one of the metal prongs (cut out of the metal casing on the side without the connection pins) inside a usb port had been bent and was touching the other side, once this was corrected with a small screwdriver all my USB ports worked again and this error message disappeared. This is probably the problem if you cannot fully insert a usb plug into ...


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

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

Looks like a kernel panic in Verbose mode.


4

/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/AlertStopIcon.icns


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

Run the following, then log out and back in defaults write com.apple.CrashReporter DialogType none


4

.zshrc is a file run when you start an interactive zsh shell, found in your home directory. The error message says you have an export command which is written incorrectly on line 48. not valid in this context means you're trying to export something that's not a variable. It looks like you're trying to add stuff to your PATH, but are substituting the current ...


3

This AppleScript will open the specified folder in VLC and begin to play the contents: tell application "VLC" OpenURL "file:///Users/grgarside/Desktop/test/" play end tell


3

The default behavior when receiving SIGQUIT is to dump core and exit; the crash reporter is triggered as a part of this process. Starting with 10.5(?) simply setting a signal handler for SIGQUIT should be sufficient to avoid the crash reporter; you will probably want the handler to also call exit. import signal, sys, os def sigquit_handler(signum, frame): ...


3

Your problems are entirely on Apple's end. The message indicates that Apple no longer signing that version of software. Yesterday, the code signing servers would sign the iOS 6 package you had downloaded on your Mac and let the device install that version of the OS. Today, Apple is no longer signing that version of the software for that device. I don't ...


3

Try starting up from the recovery partition (by holding command-R), in single user mode (by holding command-S), in safe mode (by holding shift), or in Internet recovery mode (by holding option-command-R). If you already have backups and you can start up from the recovery partition or in Internet recovery mode, try choosing the Reinstall OS X option. It ...


3

Problem identified. My machine only runs 32-bit at the moment. The latest versions of Tiled are 64-bit, and Gideros is all 64-bit. After a redownload and some minor glitches, Pixen seems to work fine. I downloaded an operational albeit outdated version of Tiled in the mean time. I really need to upgrade to 64-bit. I guess I overreacted when all three had the ...


3

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., ...



Only top voted, non community-wiki answers of a minimum length are eligible