As the title says I'm trying to install anaconda onto my MacBook running macOS Monterey. I feel like I have tried everything. Have booted in safe mode, have downloaded older versions, have even set my profile picture to default (it was somehow a fix for another piece of software with the same install error). It simply won't get past the last little bit of 'running package scripts'. Any help is appreciated.
In the first link below, csoja gave a clue to solve this issue following the instructions in the second link.
https://github.com/ContinuumIO/anaconda-issues/issues/12940
https://docs.anaconda.com/anaconda/user-guide/troubleshooting/#the-installation-failed-message-when-running-a-pkg-installer-on-osx
In my case, I successfully installed the Anaconda distribution for M1 Anaconda3-2022.05-MacOSX-arm64.pkg after changing the owner of my shell config files from root to my current user name cgironda.
I hope this would be helpful!.
I also ran into this issue and the way I fixed it was by going into Finder and searching for a folder named 'Anaconda3'. Not entirely sure why but I when I completely deleted this folder from my machine and tried to install again everything seemed to work just fine. Hope this works for you!
PS: On the successful install it did still get stuck on again for like 10 mins
Related
Sorry because i know that this topic has already been explored many times, but i couldn't find any solution to my problem.
I'm on windows 10 (if my company was working with linux i wouldn't have this type of problem --')
To sum up i tried to unsinstall Anaconda (the usual windows way by unstalling the application), to reinstall and make a fresh new installation (i'm naïve i was hopping this would be simple)...
Then when i launched spyder and the anaconda navigator, it told me that the shortcuts was invalid and that i needed to delete it.
Why not after all i just uninstall reinstall, i just needed to create new shortcuts using directly the application of spyder or anaconda that i would find in my computer...
But nothing worked. When i found the application (spyder or anaconda navigator) it didn't work, i wasn't able to launch anything. My anaconda prompt just seems to be a classic windows terminal (commands as conda, pip or jupyter just doesn't exist anymore).
This is the beginning....
Currently i have tried many thing (uninstall reinstall 4 times, delete folders myself etc..) but nothing worked and i'm affraid i totaly broke Anaconda..
Do you have any ideas on how i can get out of this mess ?
PS: of course to make the problem harder, i used a proxy to install package so i used pip for all my libraries and i'm not sure i can install with conda (whatever the conda commands doesn't work now :'( )
Seems that i finally achieve to delete all the concerning file and redo the installation ^^
I've been using gitbash these past few days and it's working just fine. But a while ago, after install a pdf reader with patch file, when I opened my gitbash it gave me the error which says "Failed to run '/usr/bin/bash': No such file or directory". I don't know what happened and why, but I think the patch file of the application that I installed has something to do with it. My pc antivirus prompted a warning, and I took actions. Then the trouble in the gitbash happened. Please help me, I don't want to reinstall gitbash again coz I also have to install some things.
Had the same issue, searched for it, this is one of the first few results. So if you are looking why you got this message recently: check your antivirus and that the folder and the file actually exist. As previous answers mentioned, reinstall helps bring it back, but antivirus might break it again. So I would check your antivirus GUI and see if you can restore it and add an exception.
Mine was that Avast antivirus classified it as 'IDP.Generic' threat (weirdly only when I would close the shell with ctrl+c or ctrl+d on Windows 10).
to resolve this issue simply reinstall git.
I disabled Avast antivirus software
Then uninstalled and reinstalled git
It worked for me:)
Like jack this was caused by my virus scanner(avast). To resolve I opened the quarantine page restored and added exemption.
Try 'echo $PATH' in CygWin Terminal to get the PATH it must written something like
/usr/local/bin:/usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Program
Files/TortoiseHg:/home
Depending on the Chroot in you sshd_config it looks for the /bin/bash file
you will have three options
you might have to copy the files into the Chroot mentioned folder and give the permission.
You can update with you Chroot
Or bind mounting would also help
ref
To resolve this issue simply deactivate your antivirus while reinstalling git.
I'm frustrated. I'm a total beginner in this (TYPO3), know well about HTML/CSS though but all the info I found on the web reads like Chinese for me. Like that one: http://mac-dev-env.patrickbougie.com/graphicsmagick/
I have no clue what that means!
I've downloaded GM, extracted the zip and double-clicked the configure file. The installation finished without any problems (as far as I can tell).
So here's the ting: can anybody please tell me, how this sort of installation is suppossed to be completed? I need it from the very beginning, actually from unpacking the zip.
Do I have to have another program, like this terminal program on the Mac, where you have to type in command lines? Do I have to write or edit code somewhere? Do I need to create folders? Where, in the TYPO3-Backend, can I check if it even works?
TYPO3 is installed and it works perfectly so far. THANKS A LOT! :)
PS: I really like to learn this (!), but my head is bumping right now :(
Easy way:
If you want to "just install" GM I suggest you to use one of OS X package managers like homebrew or macports. They can simplify configuration, building and installation process for you. So you'll only need to open Terminal and type (depending on chosen package manager):
brew install graphicsmagick or port install graphicsmagick
To verify that your installation is successful open Terminal and type gm version, as result you should see version and other details of your installation.
Fundamental way:
If you want learn how to build and install GM from sources, I recommend you to start reading official documentation. And then, by the way, read about "Make" and other tools used in build process.
As #Oles Savluk pointed easiest way to install such stuff is using homebrew. When you'll install it already, open new terminal window and use command which gm to find the path it will be i.e.: /usr/local/bin/gm - copy/write it and use in the TYPO3's Install Tool in proper place.
Installed MacVim on my Yosemite 10.10.2 Macbook Pro today from http://www.macupdate.com/app/mac/25988/macvim
The problem is that no editor window(s) are visible. If I open a file using the menu, there's simply no effect: no editor window appears. It's not hidden behind other windows, it's not listed in the Windows menu, it's just entirely undisplayed.
Strangely, the file will appear in the MRU list, though. So this renders the entire editor completely useless. Should I just build gvim myself? Is this app actually being maintained by anyone?
I'd read some answers which suggest running:
brew install macvim
... does the trick.
You might want to try that first.
What worked for me...
However, this didn't work for me because although it updated my macvim, the one being linked to in the /Applications folder was not the version being updated by brew.
So, here are the steps I had to take.
Quit MacVim if open.
Delete the MacVim file in /Applications.
In the terminal, run:
brew install macvim --override-system-vim
Run (this will add the link to your Applications file):
brew linkapps macvim
I can't be sure every step above is required, or that the --override-system-vim flag is required, but I can tell you that doing the above steps worked for me.
Hope this helps.
It looks like MacVim development has been moved to a new repository (and maybe a different group of developers?):
https://github.com/macvim-dev/macvim
This repo has had changes applied to fix MacVim's graphical problems under Yosemite. (This is the same location that brew's macvim formula currently pulls its source from, which is why MacVim works on Yosemite when installed via brew.)
They also have a set of precompiled binary releases:
https://github.com/macvim-dev/macvim/releases
The latest ("snapshot 76") has worked fine for me in Yosemite so far. You just need to download the .tbz archive, double-click it to unpack to a folder, then drag the MacVim.app icon to Applications -- much easier and less invasive than installing a whole package management system and build environment! :)
Note: I had to execute a command given in another StackOverflow answer to correct a rendering glitch seen in full screen mode for snapshot 76:
$ defaults write org.vim.MacVim MMNativeFullScreen 0
I got the same problem today.
The solution:
mv ~/.vimrc ~/.vimrc_bak
It looks like there is something wrong with my .vimrc file.
I was having the same issue, and one of the answers in here helped me, but not for the reason explained so I thought this might be useful for others.
Some plugins might depend on the version of vim, and may work in version 7 but not in version 8, when you install MacVim this could be version 8, and the terminal vim version might be 7, both will use the same .vim folder and .vimrc to load the plugins and configuration, when you open the vim from terminal it might still work because the plugins were depending on vim version 7, but when you try to execute MacVim it will try to load the plugins using version 8 and then it will crash, the reason some of the answers worked it's because they are replacing the system vim, therefore MacVim and vim will be in the same major version, if you have upgraded from the previous version the best you can do it's to clear up the plugins folder and then load MacVim or vim and check that everything is working, then start applying the plugins one by one checking that they are not breaking vim. At least with this method I found that one of the plugins was not working as expected and removing it solved the "MacVim" issue.
In summary:
- move your .vim as .vim_bak
- move your .vimrc as .vimrc_bak (suggested by #hai feng kao)
And test if this solves the issue, if that's the case then a plugin is breaking your installation and you will need to activate some and figure out which is the one that causes the issue.
Hope this helps to others, I've followed a lot of these recommendations without success until I decided to upgrade vim (terminal) and this started to break as well, that pointed me in the right direction.
Again hope this saves some hours for some.
I had the same symptom with MacVim launching with no window and command-N doesn't start any a new one. brew re-install didn't help.
It turned out there was another instance of macvim installed on my system somehow, in the Downloads folder. I found out by clicking "MacVim" --> "About MacVim" and it was a version from 2014. I found the instance and deleted it.
I created an alias for the newly installed version and copied that into Applications folder so spotlight search can find the new one. That solved my problem.
I had this problem upon updating from MacOS 10.12.5 to 10.12.6.
I uninstalled MacVim by moving it to the trashcan and downloading it again.
I would guess that the new version fixed whatever issue it had with the new operating system.
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.