On Nov 18, 2014, at 10:01 PM, Carl Hoefs <[email protected]> wrote:
>
> Since upgrading my MacBookPro to 10.10, my console log is filled with errors
> like this, repeating every 5 seconds:
>
> com.apple.xpc.launchd[1]: (com.displaylink.usbnivolistener[15580]) Service
> could not initialize: Unable to set current working directory. error=2,
> path=/System/Library/Extensions/DisplayLinkDriver.kext/DisplayLinkAgent:
> 14A389: xpcproxy + 12907 [1227]: 0x2
>
> com.apple.xpc.launchd[1]: (com.displaylink.usbnivolistener) Service only ran
> for 0 seconds. Pushing respawn out by 5 seconds.
>
> This 2-message set occurs for both com.displaylink.usbnivolistener &
> com.displaylink.useragent What are they and what do they want? There are no
> device connections to the MacBook (no external drives, monitors, USB sticks,
> etc). Should I unload these 2 agents? What are the ramifications of doing so?
DisplayLInk is a third-party technology to allow for external monitors
to be connected over USB. At some point you (or someone else) installed their
drivers, and they seem to be going bad. If you are not using it, I would remove
those drivers. Or possibly there are newer drivers that you could install to
just remove the errors without removing the functionality.
—
Karl Kuehn
[email protected]
_______________________________________________
MacOSX-talk mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/macosx-talk
