[argyllcms] Re: problem with dispcal : Error - Configuring USB port (OS X)

  • From: Graeme Gill <graeme@xxxxxxxxxxxxx>
  • To: argyllcms@xxxxxxxxxxxxx
  • Date: Wed, 02 Feb 2011 15:51:05 +1100

Grzegorz Wróbel [felix] wrote:
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".

Hi, that helps a little. It would be good to know for certain what's being 
started by
launchd though, ie:

        ls -l /Library/LaunchDaemons /Library/LaunchAgents

---------------------------------------------------------------------------

Here is another version of the programs that (hopefully) addresses
the problem more conveniently: <http://www.argyllcms.com/osxtools.tgz>

To see if they work, you'll need to initially run them as root, ie.:

   sudo spotread

since the newer X-Rite driver daemons are running as root, and a normal
user process can't stop them.

If that works, the need to use sudo can be removed by modifying
the X-Rite daemons to run as your user account, by adding the appropriate
tag to the .plist file.

For the ColorMunki for instance, you would need to:

To do this you need to edit the script that controls the X-Rite Daemon.

    cp /Library/LaunchDaemons/com.xrite.device.colormunki.plist temp.plist
    open temp.plist

and add one child below the root:

    _Item_                      _Type_                   _Value_
    UserName                     string                   myusername

where "myusername" is your username, and save the file. You then need to copy 
the modified file back:

    sudo cp temp.plist /Library/LaunchDaemons/com.xrite.device.colormunki.plist 
temp.plist

You will then need to restart the machine for this change to take effect, or 
invoke the following commands:

   sudo launchctl unload 
/Library/LaunchDaemons/com.xrite.device.colormunki.plist
   sudo launchctl load /Library/LaunchDaemons/com.xrite.device.colormunki.plist

I don't currently know what the .plist file associated with the EyeOne driver
is, but the "ls -l /Library/LaunchDaemons" may provide the answer.

Graeme Gill.

Other related posts: