Xcode keeps getting stuck on "Installing components...", it stops at around 40%. I've let it sit for a whole night, reinstalling it from the App Store and searching for solutions on the internet, but all with no succes.
When I Force Quit and restart Xcode, it does the same thing except that the progress bar immediately jumps to 100% but after that it won't budge. I can only get back to the 40% when i restart my computer.
I have Xcode version 9.4 and i'm running macOS High Sierra (10.13.5).
Question asked when starting the app
Installation stuck at 40%
Installation stuck at 100%
Edit: I've fixed it by deleting some .kext files that were messing things up. Found the following on an Apple Community post:
Open Terminal in /Applications/Utilities
Enter "system_profiler SPExtensionsDataType > ~/Desktop/kextList.txt" without the quotes and hit return(this will take a while to run).
There should now be a kextList.txt file on your desktop, open it and press both the "Apple(Command)" and "F" keys to bring up the find.
In the find field insert "Obtained from: Not Signed" Copy the destination to the .kext file to a list for use later.
Browse your drive to /System/Library/Extensions and remove any of the unsigned kext files.
Reboot and you should be all set.
Starting MacOS in Safe Mode and the starting Xcode should fix the issue. I tried in MacOS High Sierra 10.13.6 and it worked perfectly.
Related
I have downloaded LiClipse 6.1.0 from http://www.liclipse.com/download.html three times (to ensure that I don't have a corrupt/damaged file) and installed it on a MacPro Notebook with MacOS Catalina (10.15.3). I have followed the installation instructions at http://www.liclipse.com/download.html for Native Mac OS Install, but every time I get "“LiClipse.app” is damaged and can’t be opened. You should move it to the Trash."
Since it gets installed without any problem, I think that downloaded file is not corrupted/damaged, but when opening it I always get the warning about its being damaged even when I have run sudo spctl --master-disable to enable apps from "Anywhere" to run.
I would appreciate if anyone who had succeeded in opening it on a MacPro/Catalina would share his/her steps. Thanks.
You can try removing the quarantine flag (when Mac downloads a file it marks it as quarantined and it won't run unless it has an Apple signature -- which LiClipse doesn't have, so, Apple is making it always a bit harder to run files you download).
To remove the quarantine flag, run:
xattr -d com.apple.quarantine <FILE>
(<FILE> being /Applications/LiClipse.app and maybe /Applications/LiClipse.app/MacOS/LiClipse too -- I don't really have Catalina to check).
The Rstudio installation contained in Anaconda 4.3.1 is displayed at low resolution on my macbook with retina screen.
Other anaconda apps, but also the standalone version of Rstudio look fine.
Any ideas on how this can be solved?
This is a legacy from the days of us supporting macOS 10.7.
Open your RStudio.app/Contents/Info.plist file and add:
<key>NSHighResolutionCapable</key><true/>
.. near the end, just before the </dict>
After that you may need to refresh macOS's cached information after editing and before relaunching.
From Terminal:
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -v -f ${CONDA_PREFIX}/Applications/RStudio.app
I have added it to the code so next time I rebuild it this doesn't get missed.
Same issue. My provisional solution is to run RStudio from the command line. First activate the desired workspace, then run RStudio:
source activate workspace-name
RStudio
I get the following message when opening the terminal on mac
Last login: Tue Mar 11 14:33:24 on console
login(291,0x7fff78af9310) malloc: * error for object 0x7f974be006f0: pointer being freed was not allocated
* set a breakpoint in malloc_error_break to debug
[Process completed]
... and I don't seem to be able to escape it. I've been having some weird permissions problems with Adobe CC - could the two be symptoms of a single problem?
It looks like you don't have the right permissions on the /usr/bin directory.
Solution for OS X 10.11 (El Capitan) and later:
Install Onyx 3.1.3 app (Free analog of Disk Utility)
Choose 'Maintenance' -> 'Permissions' -> 'Execute'.
Solution for older versions of OS X:
Open 'Disk Utility' app -> Press 'Repair Disk Permissions'.
It will set default permissions for the /usr/bin directory.
If this step doesn't help try this:
Delete com.apple.terminal.plist from the ~/Library/Preferences folder;
Running on Mac OS X Mavericks just
Open "Disk Utility" app -> Press "Repair Disk Permissions"
Solved the problem
I couldn't find any com.apple.terminal.plist in the ~/Library/Preference folder
I had a similar issue while running OSX 10.11.6. I got a similar error when I ran certain commands, but it did not force bash to exit. It just aborted the command.
I tried running Onyx and repairing disk permissions via command line with no results (along with about another 100 or so desperate "fixes").
Eventually, I tried upgrading to a newer version of bash, which fixed the problem. To do this:
brew install bash
sudo -s
echo /usr/local/bin/bash >> /etc/shells
chsh -s /usr/local/bin/bash
Restart the computer.
I write this in the hopes that if someone else has this error they have one more fix to try!
I tried running the Disk Utility and it kept crashing. I had to run it from OSX Recovery Mode.
You can enter OSX Recovery Mode during system boot by holding down CMD ⌘+R as your mac is booting up. Choose Disk Utility when it reaches the Recovery Options screen.
I had the same problem with my dev machine. After several hours of trying anything other than a reinstall I finally realized that was the only choice. It should have been the FIRST choice. SO EASY!
Back up the critical data (just in case)
Enter the recovery mode by pressing cmd+r at start up
Choose "Reinstall Mac OS X"
That's it. When my computer restarted I was prompted for my Apple ID credentials and then my user loaded like normal, with a working Terminal, even. I didn't need to reinstall / restore anything. The whole process (including the user folder backup) took about 45 min.
Final step, remove all of the sketchy utilities installed trying to fix this without a reinstall.
I just upgraded to Mountain Lion (from Snow Leopard) so as to take advantage of Xcode 4.
Before installing Xcode 4, I would like to remove Xcode 3 (not required, but want to clean up before moving on).
The standard method of removing Xcode 3 is:
$ sudo <Xcode>/Library/uninstall-devtools --mode=all
However, when I issue this command, even from within the /Library folder, the only thing that happens is I get a "command not found" after entering my password.
I can see uninstall-devtools in Finder, so I know it's there. I just can't execute it for some reason. I've tried every possible way of running the uninstall tools.
Assistance is greatly appreciated. Thanks.
If the file really is there, type sudo in the terminal window (with a trailing space), drag and drop the uninstall-devtools file on the window, then append --mode=all. That should clear any chance you have to make a typo or any other mistake.
Similarly to information I found in another SO article, my laptop's old XCode 3.2 didn't even have the uninstall-tools utility.
So it worked fine for me to simply delete the XCode.app folder.
I've got a big problem, I can't launch anything from the terminal, not python, not emacs (or aquamacs), not even 'which'.
I was using homebrew to try to install ffmpeg and was having difficulties so I decided to pay attention to the warning that always come up advising me to uninstall fink. I removed the sw directory from my root directory, which is what the fink website told me to do and was confirmed on many blogs and message boards after a quick google search.
And since then nothing has worked, I'm almost certain that this was the cause of the problem because after removing sw I immediately tried home brew again and it said 'brew: command not found'. I get the same warning with any and every program I try to launch.
I use Mac OS Lion on a 6 year old MacBook.
Any ideas?
You probably busted your PATH. You can use absolute paths to commands until you get it fixed. For example:
/bin/mv ~/.profile ~/.profile.bak
/bin/mv ~/.bash_profile ~/.bash_profile.bak
Then open a new Terminal window, where standard things should now work. and repair your profile script.