Apple Installer failing in Catalina with ON1 Raw

Question

Level 1

8 points

Apple Installer failing in Catalina with ON1 Raw

I'm experiencing issues with Catalina in a new iMac.

For some reason, finding the Apple Installer seems to start ok; but then abruptly fails.

In this case with ON1 software; but I've had the same with some drivers for HP printer.

Had been having trouble trying to update from 10.15.3 the computer arrived with, along with some software not installing; after a few attempts, managed a restore that installed 10.15.5.

I hoped issues would be resolved now; yet here's the Installer stopping.

And while error message says I should contact the software manufacturer, I suspect there is an issue with Apple's Installer; there are other messages online about problems with this, but I haven't seen a solution that works for me.

In case useful, lines from the log here, from the point error noted:

PackageKit: ----- Begin install -----

PackageKit: Install

Failed: Error Domain=NSPOSIXErrorDomain Code=2 "No such file or

directory"

UserInfo={NSFilePath=/private/tmp/PKInstallSandbox.XXXXXX} {

Install failed: The

Installer encountered an error that caused the installation to fail.

Contact the software manufacturer for assistance.

IFDInstallController

F01220 state = 8

iMac 27″, macOS 10.15

Posted on Jun 23, 2020 2:21 AM

Reply

Answer 1

Best reply

Old Toad

Level 10

207,697 points

Jun 23, 2020 4:12 PM in response to docmartinhk

xBoot into Safe Mode (How to use safe mode on your Mac - Apple Support) by booting with the Shift key held down and try installing from there. Reboot normally afterward.

NOTE: Safe Mode boot can take up to 10 minutes as it's doing some system cache cleaning, volume verifying and directory repairing.

Reply

Answer 2

docmartinhk Author

Level 1

8 points

Jul 8, 2020 7:44 PM in response to docmartinhk

Turned out there was a solution in this; ON1 suggested I check the /private/tmp link in Terminal; got a symbolic link broken message

I found some code for deleting and then recreating this link; had to turn off SIP to do so, then re enable.

I'm no coder, not sure this is perfect solution, but hope that this could lead someone to solution.

Reply

Answer 3

docmartinhk Author

Level 1

8 points

Jun 23, 2020 4:00 PM in response to docmartinhk

I now believe this is to do with private/tmp

Perhaps permission of the tmp folder; also maybe owner [now "admin" on Catalina, not "root" as before, I've found via googling]

Maybe can use a terminal command, to set permission as 1777 ??? [again, info found online; posts from people way beyond my level in using Terminal etc]

Reply

Answer 4

docmartinhk Author

Level 1

8 points

Jun 24, 2020 9:22 PM in response to docmartinhk

Online, I've found Installer issues can be fixed by changing permission of tmp

chmod 01777 /private/tmp

Ran this; no error message, but Installer not working still.

then, I found that can find info on permissions with a command, which I used:

ls -l@ed /tmp ; ls -l@ed /private/tmp

Result:

lrwxr-xr-x@ 1 root admin 11 Jun 23 01:53 /tmp -> private/tmp

com.apple.rootless 0

lrwxr-xr-x@ 1 root wheel 11 Mar 8 2019 /private/tmp -> private/tmp

com.apple.rootless 0

The "@" character is unusual here? Something re non Unix properties?

Reply

Answer 5

docmartinhk Author

Level 1

8 points

Jun 25, 2020 4:10 PM in response to docmartinhk

Another installer failing: online installer for Topaz gigapixel.

Log says:

Service could not initialize: Unable to set current working directory. error = 2: No such file or directory, path = /tmp: 19F101: xpcproxy + 14521 [673][79E208B1-0CBD-3EDD-B9EB-CA98C7224A2F]: 0x2

26 Jun 2020 at 6:39:17 AM com.apple.xpc.launchd[1]: Service exited with abnormal code: 78

so there's tmp folder, again... ...

Again looked for info, and there's some about trying to fix issue with installer not working; a bug found on systems inc with OS reinstalled from system restore [as I've done]

"While investigating, both I and a Malwarebytes support engineer both

independently found the same thing on these two systems: the /private/tmp folder had been replaced with a recursive symlink, pointing back to itself. And, worse, that symlink was marked with a restricted flag, meaning that it was protected against being modified by System Integrity Protection. "

gives a couple of possible solutions; not sure if I should attempt tho!

https://whitehatmac.com/odd-recursive-symlink-bug-in-catalina/

Reply