I'd like to gather as much information about this failure as possible, in order to try and spot a pattern. I'm working on a new iMac with a clean install of leopard I received it with tiger and a leopard upgrade disc. All prerequisites are installed X11, Xcode 3. I use bash. At the time of installation, I didn't have a. The hidden files in my home dir are the following:. Have I missed something I need for successfully working with MacPorts for now I have not included anything that is used for X11?
If this is enough, my direct problem is solved. However I will try to help solving this, so don't hesitate to ask more questions. I just reported this with I didn't see this report first. I swear I searched before and didn't see this reported.
You can close , but please add me to the CC of this. I have had this happen on two machines with clean Leopard installs upgraded to I had the same problem when I tried to install MacPorts 1.
It seems to be caused at least in my case by the fact that the installer tries to make an rsync-connection. This might fail when you are using an HTTP-proxy. Therefore I think the postflight script should be modified to take this into account. I am not behind an HTTP-proxy, so that is not the problem in my case.
A "sudo port selfupdate" works without problems. Any more info anyone in this ticket can provide me with? If you can, please create a virgin account if on Leopard, the Guest account might suffice and confirm that it doesn't have any MacPorts Terminal settings through the following:. Setting set -x debugging mode for bash might help. No MacPorts paths where present. After running the postflight script ran withoud sudo , a.
Really hope there's a fix for this soon - not a good look. I resolve this problem, by loading in OSX safe mode hold down the shift key during startup , ran the uninstaller of the previously install virtualbox to remove any other files that the current version of uninstaller missed and then installed the current 3. That's a useful workaround, let's hope there is a proper resolution to this year old issue, before another 12 months rolls around.
Search for all stuff which include VBox. This shows that the old kernel extension could not be unloaded. That is the reason why the installer fails. Now we need to find out why it couldn't be unloaded. When installing a new version, you have to make absolutely sure that there is no part of VirtualBox running. Please check with "ps -A grep -i box" in a Terminal window if there are some processes of VBox left before trying to install it.
Can you please attach the VBox. Does the uninstall also fail if you try it directly after a reboot of your Mac? The problem doesn't happen if I haven't started VirtualBox after a reboot.
Please attach the xml config and a vbox log file. Also please attach the output of kextstat after using the VM. Sorry for asking so much questions, but I can't reproduce that behavior. Built-In iSight [] " is checked. I just bought a brand new MacPro5,1 with SnowLeopard Virtualbox was installed successfully, but the installer claimed that the install failed!
Do you think it might be time to fix this once and for all? It makes users wonder about the kwality of the programming in the product. I see the problem: logging in as root causes the postflight script to not identify the current user, and so when it runs 'sudo' to register file extensions, it dies with 'unknown user'. What is the reason to install VirtualBox as root? This is not necessary. We install all software as root, and then prevent users from changing it.
This may be considered a corner case. I fixed the root install problem, although the rest of the ticked is about different installation problems unloading the driver , which I still can't reproduce. I still have this problem and the work around of rebooting is a nuisance. This is the log of exectuing the uninstall tool:. I checked with ps and the Activity monitor for VBox related tasks, but there are none.
Since there is no process running, maybe the extension is retained, whatever that means. MiSchi, which did you really check that no VBox processes are running?
Contact — Privacy policy — Terms of Use. Login Preferences. Browse Source. The following install step failed: Run postflight script Kontakt 5 Content. More Less. Communities Get Support. Sign in Sign in Sign in corporate. Browse Search. Ask a question. User profile for user: johnfromwarwick johnfromwarwick. I have a Macbook. Ned, I really appreciate the help! I think we are getting closer.
I put the info from the installer log into my question. Add a comment. Active Oldest Votes. Improve this answer. Ned Deily Ned Deily 80k 16 16 gold badges silver badges bronze badges. I did indeed delete the Python. I saw on a separate post that I shouldn't mess with it after I had done the damage I tried to copy over the files, and it didn't work.
So I had to do a full system restore to a previous backup. Thank goodness for time machine : I can't tell you how much I appreciate your help. Dave W. Smith Dave W. Smith Thanks Dave for the info! I tried installing 2.
0コメント