Well, it's a much better workaround than uninstalling all the ColorMunki software. It works, thank you! Graeme-- here's the output of ls -l /Library/LaunchAgents: total 64 -r--r--r-- 1 root wheel 460 Dec 29 16:30 at.obdev.LittleSnitchNetworkMonitor.plist -r--r--r-- 1 root wheel 437 Dec 29 16:30 at.obdev.LittleSnitchUIAgent.plist -rw-r--r-- 1 root wheel 698 May 31 2010 com.Logitech.Control Center.Daemon.plist -rw-r--r-- 1 root wheel 612 Jan 1 00:44 com.adobe.AAM.Updater-1.0.plist -r-xr-xr-x 1 root wheel 582 Jan 1 00:44 com.adobe.CS5ServiceManager.plist -rw-r--r-- 1 root wheel 476 Jan 4 20:12 com.micromat.TechToolProAgent.plist -rw-r--r-- 1 root wheel 464 Oct 9 2009 com.xrite.colormunkid.plist -rw-r--r-- 1 root wheel 426 Jun 2 2009 com.xrite.device.message.plist Cheers, Rishi On Tue, Feb 1, 2011 at 2:10 PM, Graeme Gill <graeme@xxxxxxxxxxxxx> wrote: > Grzegorz Wróbel [felix] wrote: >> >> Problem solved. Turning off (not removing preference pane) fixed problem. >> I tried to > > Sorry, I'd call that a "workaround", not a solution. > >> identify process by "lsof \ grep -i usb", but it shows false trail to >> Quicktime, so I >> type "top" command and find numbers of suspicious processes. Reports from >> findings >> right process was concluded in "trying.txt" file. I hope that my findings >> help. Report >> after command "ps -A -c" are saved in "log.txt" File "trying.txt" was made >> few days >> before, so PID are different than in "log.txt". > > On looking into this further, it might be easier to get a listing of what's > in > /Library/LaunchAgents, rather than for me to try and guess. ie: > > ls -l /Library/LaunchAgents > > Graeme Gill. > >