I'm not sure when exactly this started, but all packages (.pkg) that I try to install, including Microsoft Teams, fail just at the end of installer, with a message to contact the software manufacturer. I'm currently on 10.15.4, but I know these problems started when I was still on a 10.15 beta.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Package installation fails
- Thread starter DingeZ
- Start date
- Sort by reaction score
Hmm. For some reason I can't the log file is not selectable for uploading, but here is an excerpt from my last try:
Code:
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: @(#)PROGRAM:Install PROJECT:Install-1000
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: @(#)PROGRAM:Installer PROJECT:Installer-965.1
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Hardware: MacBook8,1 @ 1.20 GHz (x 4), 8192 MB RAM
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Running OS Build: Mac OS X 10.15.4 (19E287)
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Env: USER=Bernd
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Env: COMMAND_MODE=unix2003
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Env: LOGNAME=Bernd
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Env: HOME=/Users/Bernd 1
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Env: SHELL=/bin/zsh
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Env: TMPDIR=/var/folders/3p/7h92hx654_j298wcskf_ysr00000gn/T/
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Env: __CF_USER_TEXT_ENCODING=0x1F5:0x0:0x5
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Env: XPC_SERVICE_NAME=com.apple.xpc.launchd.oneshot.0x10000003.Installer
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Env: XPC_FLAGS=0x0
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Microsoft Teams 1.00.308663 Installation Log
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Opened from: /Users/Bernd 1/Downloads/Teams_osx.pkg
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Package Authoring Error: <background_scaling> has an unsupported MIME type: X-NSObject/NSNumber
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Package Authoring Error: <background_alignment> has an unsupported MIME type: X-NSObject/NSNumber
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Package Authoring Error: <layout-direction> has an unsupported MIME type: X-NSObject/NSNumber
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Failed to load specified background image
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Product archive /Users/Bernd 1/Downloads/Teams_osx.pkg trustLevel=350
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: External component packages (1) trustLevel=350
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Could not load resource readme: (null)
2020-05-05 09:12:46+02 MacBook-van-Bernd-Keuning Installer[733]: Could not load resource license: (null)
2020-05-05 09:12:48+02 MacBook-van-Bernd-Keuning Installer[733]: PUKApplicationCloser: Done updateOpenAppsAndPlugIns!
2020-05-05 09:12:48+02 MacBook-van-Bernd-Keuning Installer[733]: PUKApplicationCloser: Alert did end with code: -1
2020-05-05 09:12:48+02 MacBook-van-Bernd-Keuning Installer[733]: ================================================================================
2020-05-05 09:12:48+02 MacBook-van-Bernd-Keuning Installer[733]: User picked Standard Install
2020-05-05 09:12:48+02 MacBook-van-Bernd-Keuning Installer[733]: Choices selected for installation:
2020-05-05 09:12:48+02 MacBook-van-Bernd-Keuning Installer[733]: Installeer: "Microsoft Teams"
2020-05-05 09:12:48+02 MacBook-van-Bernd-Keuning Installer[733]: Installeer: "Microsoft Teams"
2020-05-05 09:12:48+02 MacBook-van-Bernd-Keuning Installer[733]: Teams_osx.pkg#Teams_osx_app.pkg : com.microsoft.teams : 1.00.308663
2020-05-05 09:12:48+02 MacBook-van-Bernd-Keuning Installer[733]: ================================================================================
2020-05-05 09:12:48+02 MacBook-van-Bernd-Keuning Installer[733]: It took 0.00 seconds to summarize the package selections.
2020-05-05 09:12:49+02 MacBook-van-Bernd-Keuning Installer[733]: -[IFDInstallController(Private) _buildInstallPlanReturningError:]: location = file://localhost
2020-05-05 09:12:49+02 MacBook-van-Bernd-Keuning Installer[733]: -[IFDInstallController(Private) _buildInstallPlanReturningError:]: file://localhost/Users/Bernd%201/Downloads/Teams_osx.pkg#Teams_osx_app.pkg
2020-05-05 09:12:49+02 MacBook-van-Bernd-Keuning Installer[733]: Set authorization level to root for session
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning Installer[733]: Administrator authorization granted.
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning Installer[733]: Will use PK session
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning Installer[733]: Using authorization level of root for IFPKInstallElement
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning Installer[733]: Starting installation:
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning Installer[733]: Configuring volume "Macintosh HD"
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning Installer[733]: Preparing disk for local booted install.
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning Installer[733]: Free space on "Macintosh HD": 17,3 GB (17298444288 bytes).
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning Installer[733]: Create temporary directory "/var/folders/3p/7h92hx654_j298wcskf_ysr00000gn/T//Install.7335u8Ikw"
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning Installer[733]: IFPKInstallElement (1 packages)
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: Adding client PKInstallDaemonClient pid=733, uid=501 (/System/Library/CoreServices/Installer.app/Contents/MacOS/Installer)
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning Installer[733]: PackageKit: Enqueuing install with framework-specified quality of service (utility)
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: ----- Begin install -----
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: request=PKInstallRequest <1 packages, destination=/>
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: packages=(
"PKLeopardPackage <id=com.microsoft.teams, version=1.00.308663, url=file:///Users/Bernd%201/Downloads/Teams_osx.pkg#Teams_osx_app.pkg>"
)
2020-05-05 09:12:52+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: Set reponsibility for install to 733
2020-05-05 09:12:53+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: Extracting file:///Users/Bernd%201/Downloads/Teams_osx.pkg#Teams_osx_app.pkg (destination=/Library/InstallerSandboxes/.PKInstallSandboxManager/75D00B25-48AA-4E30-AAC3-7E961EB25FCD.activeSandbox/Root/Applications, uid=0)
2020-05-05 09:12:54+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: prevent user idle system sleep
2020-05-05 09:12:54+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: suspending backupd
2020-05-05 09:12:54+02 MacBook-van-Bernd-Keuning install_monitor[746]: Temporarily excluding: /Applications, /Library, /System, /bin, /private, /sbin, /usr
2020-05-05 09:12:54+02 MacBook-van-Bernd-Keuning install_monitor[746]: Re-included: /Applications, /Library, /System, /bin, /private, /sbin, /usr
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: releasing backupd
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: allow user idle system sleep
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: Cleared responsibility for install from 733.
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: Cleared permissions on Installer.app
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: Install Failed: Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory" UserInfo={NSFilePath=/private/tmp/PKInstallSandbox.XXXXXX} {
NSFilePath = "/private/tmp/PKInstallSandbox.XXXXXX";
}
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: Running idle tasks
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning Installer[733]: install:didFailWithError:Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory" UserInfo={NSFilePath=/private/tmp/PKInstallSandbox.XXXXXX}
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: Removing client PKInstallDaemonClient pid=733, uid=501 (/System/Library/CoreServices/Installer.app/Contents/MacOS/Installer)
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning installd[494]: PackageKit: Done with sandbox removals
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning Installer[733]: Install failed: Er heeft zich in het installatieprogramma een fout voorgedaan waardoor de installatie is mislukt. Neem contact op met de fabrikant van de software.
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning Installer[733]: IFDInstallController 11D3320 state = 8
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning Installer[733]: Displaying 'Install Failed' UI.
2020-05-05 09:12:55+02 MacBook-van-Bernd-Keuning Installer[733]: 'Install Failed' UI displayed message:'Er heeft zich in het installatieprogramma een fout voorgedaan waardoor de installatie is mislukt. Neem contact op met de fabrikant van de software.'.That fails too. 'File or directory does not exist'
It gives me this:
Code:
ls -l@ /tmp
/private/tmp: broken symbolic link to private/tmp
/tmp: broken symbolic link to private/tmp
lrwxr-xr-x@ 1 root admin 11 10 apr 15:20 /tmp -> private/tmp
com.apple.rootless 0It seems that the link from
I am not sure if this is trivial to fix, as the
/tmp or /private/tmp to <Data volume>/private/tmp is broken. It maybe a remnant of the Catalina beta; the result of a botched installation. Have you used the Mac App Store installer for Catalina after the betas or did you update to another beta version instead? Running the installer (again) might fix this.I am not sure if this is trivial to fix, as the
private directory is located on the data volume and “firmlinked” to the root directory that is not writeable anymore. You should check if the directory exists on your data volume (replace the name of the Macintosh HD as needed):
Code:
file "/Volumes/Macintosh HD/private/tmp" "/Volumes/Macintosh HD/tmp"Dingez, here's what you need to do.
First off, the people in this thread are absolutely correct; your system is screwed up from the Catalina betas. You need to do a full installation; rather than a software update to fix your system up.
Open the App Store and search for Catalina.
Click "Get", it will open Software Update and say that it's looking for the update. You will see a drop down banner asking you to download/install Catalina. Go ahead and click Download and once that is done open the "Install macOS Catalina" application in your /Applications folder. Do an upgrade over your current system.
Don't worry, this is non-destructive and your data will be safe.
First off, the people in this thread are absolutely correct; your system is screwed up from the Catalina betas. You need to do a full installation; rather than a software update to fix your system up.
Open the App Store and search for Catalina.
Click "Get", it will open Software Update and say that it's looking for the update. You will see a drop down banner asking you to download/install Catalina. Go ahead and click Download and once that is done open the "Install macOS Catalina" application in your /Applications folder. Do an upgrade over your current system.
Don't worry, this is non-destructive and your data will be safe.
Yes, I’ve had problems with the Catalina beta. I was actually stuck on a beta version long after the final version was released. Trying updates or redownloading via the App Store didn’t work until I found the ‘reinstall on boot’ shortcut that did work. I’m now trying the redownload through the App Store again.
And no luck either. I tried the download through the App Store and got a failure once the download was complete. Then I tried a reinstall through the recovery manager (boot up on cmd+R), it worked but didn't solve the issue. Then I tried the download through the App Store again, but it failed similarly.
Try to download Catalina 10.15.4 with
or
create a bootable installer https://support.apple.com/en-us/HT201372, back up your data and make a clean install.
Code:
open "x-apple.systempreferences:com.apple.preferences.softwareupdate?installMajorOSVersion=10.15.4"
Code:
softwareupdate --fetch-full-installer --full-installer-version 10.15.4create a bootable installer https://support.apple.com/en-us/HT201372, back up your data and make a clean install.
Was there an error message? At which stage did the installation fail (e.g. during the initial setup, after the reboot, etc).
The installation failed right after the download was complete. There was no specific error message other than 'Installation failed', but looking through /var/log/install.log I found the error to be 'No such file or directory exists', referring tot /var/tmp. So the main issue here seems to also affect the ability to update MacOS.
As a further attempt I tried installing the 10.15.5 beta, which prompted an issue I had before. After the download is completed, MacOS shuts down to update. The Apple logo with loading bar comes on, but after around 10% completion it suddenly disappears and boots as if nothing happened.
Whats also wierd is that system.log logs the following error every second (!):
I think I'm going to try a clean install, but that would have to wait until the weekend, as restoring files takes around 24 to 36 hours.
As a further attempt I tried installing the 10.15.5 beta, which prompted an issue I had before. After the download is completed, MacOS shuts down to update. The Apple logo with loading bar comes on, but after around 10% completion it suddenly disappears and boots as if nothing happened.
Both methodes failed with the same errors as before.
Whats also wierd is that system.log logs the following error every second (!):
Code:
May 6 13:30:45 MacBook-van-Bernd-Keuning com.apple.xpc.launchd[1] (com.apple.quicklook.ui.helper[1185]): Service could not initialize: Unable to set current working directory. error = 2: No such file or directory, path = /tmp: 19E287: xpcproxy + 14521 [673][8D92CEED-157E-321E-A121-16695DE8DBC5]: 0x2
May 6 13:30:45 MacBook-van-Bernd-Keuning com.apple.xpc.launchd[1] (com.apple.quicklook.ui.helper[1185]): Service exited with abnormal code: 78
May 6 13:30:45 MacBook-van-Bernd-Keuning com.apple.xpc.launchd[1] (com.apple.quicklook.ui.helper): Service only ran for 0 seconds. Pushing respawn out by 1 seconds.I think I'm going to try a clean install, but that would have to wait until the weekend, as restoring files takes around 24 to 36 hours.
At this point, you may do better to try reinstalling the operating system through Internet Recovery. This should avoid the missing /tmp situation and won't delete your data if you do not manually erase the disk. Start up the computer holding command-option-R to get into internet recovery. This will install 10.15.4 on the computer.
You should also try creating a Catalina thumb drive, boot onto it and install Catalina from there. It seems that any installation procedure started from within the running system will not work.
I also still suggest using the commands at #9, maybe the issue can at least be somewhat fixed with further analysis.
I also still suggest using the commands at #9, maybe the issue can at least be somewhat fixed with further analysis.
Okay, so let's just do what we can to get the installer to succeed.
Open Terminal and Run:
sudo mkdir -p /private/tmp
sudo mkdir -p /private/var
sudo mkdir -p /private/etc
Then try launching the installer again.
Packages may start working against simply by doing this; but you do not want to live with this hack. Just do this so that you can use the installer again.
I did it. The re-installation worked, worked, but it didn't solve the problem.
The result is:
Code:
mkdir: /private/tmp: Input/output errorYou cannot write to the root path like that anymore, because it is on a read-only filesystem.
It is difficult to assess this problem without exactly knowing where the cause lies; either it is just a missing directory (hence the broken link), or a permissions problem on that directory or it is a problem in the filesystem itself (maybe the firmlinks have to be recreated).
Can you post the result of these commands?
/private/tmp is an APFS firmlink that links to another location on another APFS volume (the Data volume).It is difficult to assess this problem without exactly knowing where the cause lies; either it is just a missing directory (hence the broken link), or a permissions problem on that directory or it is a problem in the filesystem itself (maybe the firmlinks have to be recreated).
Can you post the result of these commands?
Code:
ls -l /System/Volumes/Data
Code:
ls -l /System/Volumes/Data/privateHere you go:
Code:
total 2
drwxrwxr-x+ 20 root admin 640 6 mei 23:12 Applications
drwxr-xr-x 62 root wheel 1984 6 mei 23:12 Library
drwxr-xr-x@ 3 root wheel 96 29 feb 10:23 System
drwxr-xr-x 6 root admin 192 6 apr 21:45 Users
drwxr-xr-x 4 root wheel 128 8 mei 00:19 Volumes
drwxr-xr-x 2 root wheel 64 25 aug 2019 cores
dr-xr-xr-x 2 root wheel 1 7 mei 08:19 home
drwxr-xr-x 2 root wheel 64 25 aug 2019 mnt
drwxr-xr-x 3 root wheel 96 24 sep 2019 opt
drwxr-xr-x 6 root wheel 192 6 mei 23:12 private
drwxr-xr-x 2 root wheel 64 25 aug 2019 sw
drwxr-xr-x 5 root wheel 160 6 apr 21:38 usr
Code:
total 0
drwxr-xr-x 131 root wheel 4192 7 mei 22:44 etc
drwxr-xr-x 2 root wheel 64 29 feb 07:55 tftpboot
lrwxr-xr-x@ 1 root wheel 11 6 jul 2018 tmp -> private/tmp
drwxr-xr-x 27 root wheel 864 6 mei 23:13 varHmm that looks weird.
It seems that your /System/Volumes/Data/private/tmp (which is supposed to be the temporary directory, is itself a symbolic link).
Try this:
Then reboot. Then try
ls -l /System/Volumes/Data/private looks like this for me:
Code:
drwxr-xr-x 116 root wheel 3712 May 1 00:58 etc
drwxr-xr-x 2 root wheel 64 Nov 9 11:38 tftpboot
drwxrwxrwt 5 root wheel 160 May 7 18:21 tmp
drwxr-xr-x 28 root wheel 896 Apr 5 22:55 varIt seems that your /System/Volumes/Data/private/tmp (which is supposed to be the temporary directory, is itself a symbolic link).
Try this:
Code:
sudo rm /System/Volumes/Data/private/tmp
sudo mkdir /System/Volumes/Data/private/tmp
sudo chmod 1777 /System/Volumes/Data/private/tmpThen reboot. Then try
ls -l /System/Volumes/Data/private and file /private/tmp /tmp again.
Last edited:
You're getting EIO when making a directory.
This is really bad and means you have filesystem corruption.
You need to backup your data, go to Recovery, open Disk Utility, erase the entire APFS Container, and reinstall macOS from Recovery with a clean install.