Hot answers tagged error
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.
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 ...
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 ...
Your best bet would be to do a clean install, presuming you have copies / licenses for any software you use on there. Backup any files you want to keep, and follow one of the many guides out there. For instance: http://mashable.com/2015/10/01/clean-install-os-x-el-capitan/ This could well take less time than figuring out what the IT guys did, and make your ...
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.
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. ...
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.
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.
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 ...
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 ...
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.
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.
It seems it's some kind of temporary glitch, as it usually helps to restart the machine. Other suggestions: Reboot into Safe Mode, then Verify and repair drive Reboot and hold the CMD+R keys Select Disk Utility Click on the image under my drive Verify and repair drive You may try to remove the cache files/folders located in /var/folders/ directory (not ...
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 ...
Signing in in my iPhone and enable iCloud Keychain did the trick to me. So I restored the keychain in my iPhone and then the keychain switch in my Mac changed to off state as magic
Going by the appearance of the dialog window, it looks like the school you got this Mac from was using JAMF Software's Casper Suite to manage their Macs. One of Casper's features is being able to prevent specified applications from launching, with the additional option of providing a message to the end-user. As you're receiving this message, it appears that ...
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 ...
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 ...
I wasn't able to get my network back by disabling and re-enabling TCP/IP or the Wi-Fi. It seems in my case the computer had gone to sleep with a Juniper VPN connection and when it woke back up the connection had timed out and the routes weren't cleaned up. For me, I had two computers, one working and one not, and so was able to identify the problem after ...
This error typically comes up when OSX is trying to access a file or folder on a remote server, but it cannot connect to that server. I have two examples to give an idea of where this can come from: You are able to have OSX connect to a remote folder automatically at login. Typically these are shown in the "Login Items" tab of the "Users & Groups" ...
Open Terminal and try entering following: df which will give a listing of your mounted volumes similar to: Filesystem 512-blocks Used Available Capacity Mounted on /dev/disk0s2 1951845952 1655141456 296192496 85% / devfs 477 477 0 100% /dev map -hosts 0 0 0 100% ...
I had exactly the same problem. I started Apache without DocumentRoot(s). It did the trick. sudo apachectl -T
I managed to unzip it with tar. tar xzvf 2015-09-24-raspbian-jessie.zip Requires no installation of additional software
This is the device trying to connect to the Apple updating server, but due to a network reason at your end, you are being prompted for your password, either for your network, proxy, or other reason. This is not asking for your Apple ID but rather whatever network connection authentication details you usually use to connect to your network.
The location of error_log is defined in /etc/apache2/httpd.conf. Run grep '^ErrorLog' /etc/apache2/httpd.conf to see the definition.
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 ...
Run the following, then log out and back in defaults write com.apple.CrashReporter DialogType none
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 ...
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.
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 ...
Only top voted, non community-wiki answers of a minimum length are eligible