Discussion:
ColorMunki on OS X
Graeme Gill
2014-02-10 07:30:23 UTC
Permalink
Today I tried using ColorMunki with dispcalGUI (argyllcms 1.6.3) after
using the software from X-Rite =93ColorMunki Design=94 on Mac OS X 10.9
Mavericks'.
dispcal: Error - new_disprd() failed with 'Instrument Access Failed
in the GUI I briefly saw (=93kill nprocess..=94) in the log (several
kill_nprocess: killing process 'ColorMunkiDeviceService' pid 108
kill_nprocess: kill process 'ColorMunkiDeviceService' failed with 1
As it didn't work I tried unloading the daemon/service from launchd (as
written on the page
http://argyllcms.com/doc/Installing_OSX.html#ColorMunki) afterwards it
worked flawlessly.
So I am wondering if it would be possible to use the command (as
launchctl unload =
/Library/LaunchDaemons/com.xrite.device.colormunki.plist
instead of trying to kill processes ?
Hi,
I'd imagine that will work, but then I also imagine that running
ArgyllCMS or dispcalGUI as root would also work.

If you follow the advice here <http://www.argyllcms.com/doc/Installing_OSX.html>
and modify com.xrite.device.colormunki.plist to run as you rather than root,
then you should also not have any problems.

The advantage of the Argyll tools killing the ColorMunkiDeviceService
process is that you can simply run either tool, without any further consideration.

Graeme Gill.
Jonathan Buschmann
2014-02-10 18:29:11 UTC
Permalink
Post by Graeme Gill
Today I tried using ColorMunki with dispcalGUI (argyllcms 1.6.3) after
using the software from X-Rite =93ColorMunki Design=94 on Mac OS X 10.9
Mavericks'.
dispcal: Error - new_disprd() failed with 'Instrument Access Failed
in the GUI I briefly saw (=93kill nprocess..=94) in the log (several
kill_nprocess: killing process 'ColorMunkiDeviceService' pid 108
kill_nprocess: kill process 'ColorMunkiDeviceService' failed with 1
As it didn't work I tried unloading the daemon/service from launchd (as
written on the page
http://argyllcms.com/doc/Installing_OSX.html#ColorMunki) afterwards it
worked flawlessly.
So I am wondering if it would be possible to use the command (as
launchctl unload =
/Library/LaunchDaemons/com.xrite.device.colormunki.plist
instead of trying to kill processes ?
Hi,
I'd imagine that will work, but then I also imagine that running
ArgyllCMS or dispcalGUI as root would also work.
If you follow the advice here <http://www.argyllcms.com/doc/Installing_OSX.html>
and modify com.xrite.device.colormunki.plist to run as you rather than root,
then you should also not have any problems.
The advantage of the Argyll tools killing the ColorMunkiDeviceService
process is that you can simply run either tool, without any further consideration.
In that case would it be possible to print the url in argyll commands output (log window in dispcalGUI) when the ColorMunkiDeviceService is running as root and cannot be killed ?
Post by Graeme Gill
Graeme Gill.
Graeme Gill
2014-02-11 02:25:10 UTC
Permalink
Post by Jonathan Buschmann
In that case would it be possible to print the url in argyll commands output (log
window in dispcalGUI) when the ColorMunkiDeviceService is running as root and cannot be
killed ?
Hi,
that's a little difficult - it's normal for some of the attempts at killing
the other process to fail, since it's a race/competition for Argyll to grab
the device before the X-Rite daemon restarts. The only way you really know that
this has failed is that Argyll fails to connect, and the failure is reported.

Graeme Gill.

Continue reading on narkive:
Loading...