Dext not initializing with a log "Failed to write extension load report plist"

Question

Created Mar ’25

Replies 1

Boosts 0

Participants 2

When plugging in my matched USB device I see the logs below. It seems the kernelmanagerd process is sandboxed and can't write out the reason my Dext failed to load. Is there somewhere else I can look for this info?

	default	11:03:22.175152-0700	kernelmanagerd	Received kext load notification: me.keithg.MyUserUSBInterfaceDriver
	default	11:03:22.177637-0700	kernel	1 duplicate report for Sandbox: icdd(2124) allow file-read-data /Library/Image Capture/Devices
	error	11:03:22.177681-0700	kernel	Sandbox: kernelmanagerd(545) deny(1) file-write-create /private/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/com.apple.kernelmanagerd/TemporaryItems
com.apple.libcoreservices	error	11:03:22.177711-0700	kernelmanagerd	mkdir: path=/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/com.apple.kernelmanagerd/TemporaryItems/ mode= -rwx------: [1: Operation not permitted]
	error	11:03:22.179361-0700	kernel	Sandbox: kernelmanagerd(545) deny(1) file-write-create /private/var/db/loadedkextmt.plist.sb-5a00fc77-LNttZF
com.apple.libcoreservices	error	11:03:22.177755-0700	kernelmanagerd	_dirhelper_relative_internal: error for path <private>: [1: Operation not permitted]
com.apple.accessories	default	11:03:22.177674-0700	WindowServer	Sending analytics event... (eventName: com.apple.ioport.transport.USB.published)
	error	11:03:22.179913-0700	kernelmanagerd	Failed to write extension load report plist.

Boost

Answer 1

DTS Engineer OP

Apple

Mar ’25

When plugging in my matched USB device I see the logs below. It seems the kernelmanagerd process is sandboxed and can't write out the reason my Dext failed to load. Is there somewhere else I can look for this info?

I think there's something else going on with your machine, as the sandbox shouldn't be preventing a process from writing to it's own temporary items directory. Do you have any endpoint security product installed? Having said that, the system log should also explain why the load failed.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

0