#10068 (Bug) DisplayCAL-apply-profiles.exe: unrecognized option `–skip’

+1 0

Closed as Fixed
Component: DisplayCAL 3.4.0.0 | Milestone: 3.5
Created by rafik

Last modified


DisplayCAL-3.4.0.0 + Argyll_V2.0.0 x64:

2018-01-16 11:43:11,757 DisplayCAL-apply-profiles.exe 3.4.0.0 2017-12-30T16:01:57.145Z
2018-01-16 11:43:11,767 Windows 10 Enterprise x86_64
2018-01-16 11:43:11,767 Python 2.7.14 (v2.7.14:84471935ed, Sep 16 2017, 20:19:30) [MSC v.1500 32 bit (Intel)]
2018-01-16 11:43:11,769 Faulthandler 3.0
2018-01-16 11:43:12,213 Imported existing <module 'comtypes.gen' from 'C:\Program Files\DisplayCAL-3.4.0.0\lib\library.zip\comtypes\gen\__init__.pyc'>
2018-01-16 11:43:12,217 Creating writeable comtypes cache directory: 'c:\users\admin\appdata\local\temp\comtypes_cache\DisplayCAL-apply-profiles-27'
2018-01-16 11:43:12,220 Using writeable comtypes cache directory: 'c:\users\admin\appdata\local\temp\comtypes_cache\DisplayCAL-apply-profiles-27'
2018-01-16 11:43:12,226 wxPython 3.0.2.0 msw (classic)
2018-01-16 11:43:12,226 Encoding: cp852
2018-01-16 11:43:12,226 File system encoding: mbcs
2018-01-16 11:43:12,246 DisplayCAL-apply-profiles.exe: unrecognized option `--skip'
2018-01-16 11:43:12,247 Exiting DisplayCAL-apply-profiles
2018-01-16 11:43:12,247 Usage: DisplayCAL-apply-profiles.exe [OPTION]...
2018-01-16 11:43:12,247 Apply profiles to configured display devices and load calibration
2018-01-16 11:43:12,247 Version 3.4.0.0
2018-01-16 11:43:12,247
2018-01-16 11:43:12,249 --help Output this help text and exit
2018-01-16 11:43:12,249 --force Force loading of calibration/profile (if it has been
2018-01-16 11:43:12,249 disabled in DisplayCAL.ini)
2018-01-16 11:43:12,249 --oneshot Exit after loading calibration
2018-01-16 11:43:12,249 -V, --version Output version information and exit
2018-01-16 11:43:12,249 Ran application exit handlers


17 thoughts on “DisplayCAL-apply-profiles.exe: unrecognized option `–skip’”

    1. The option isn’t normally set for the profile loader task scheduler or autostart entry though, so you must have added it at some point.

  1. the relevant part from DisplayCAL.log:

    2018-01-16 11:43:08,469 Session log: PL2480H #3 2018-01-16 11-10 2.2 F-S XYZLUT+MTX
    2018-01-16 11:43:08,469
    2018-01-16 11:43:08,470 Working directory:
    2018-01-16 11:43:08,470 c:\
    2018-01-16 11:43:08,470 users\
    2018-01-16 11:43:08,470 admin\
    2018-01-16 11:43:08,471 appdata\
    2018-01-16 11:43:08,471 local\
    2018-01-16 11:43:08,473 temp\
    2018-01-16 11:43:08,474 DisplayCAL-mhahn_\
    2018-01-16 11:43:08,474
    2018-01-16 11:43:08,476 Command line:
    2018-01-16 11:43:08,476 C:\Users\admin\Downloads\Argyll_V2.0.0\bin\dispwin.exe
    2018-01-16 11:43:08,476 -Sl
    2018-01-16 11:43:08,476 -v
    2018-01-16 11:43:08,477 -d3
    2018-01-16 11:43:08,477 -c
    2018-01-16 11:43:08,479 -I
    2018-01-16 11:43:08,479 “PL2480H #3 2018-01-16 11-10 2.2 F-S XYZLUT+MTX.icm”
    2018-01-16 11:43:08,480
    2018-01-16 11:43:11,588 The profile has been installed and activated.
    2018-01-16 11:44:03,661 ——————————————————————————–
    2018-01-16 11:44:03,661 Measure ambient
    2018-01-16 11:44:03,813 ——————————————————————————–

  2. perhaps the source of the problems lies in https://sourceforge.net/p/dispcalgui/code/HEAD/tree/trunk/DisplayCAL/worker.py#l7701 ?

    1. That’s fallback code that shouldn’t really be running unless there’s something wrong with Windows task scheduler. If you open up task scheduler, do you see a “DisplayCAL profile loader launcher” entry?

  3. No, after “The profile has been installed and activated.” I don’t see the profile loader icon – I have to run DisplayCAL-apply-profiles-launcher.exe manually.

    Probably the “–skip” option causes the profile loader to fail and exit 🙁

  4. No, I cannot see such task.

    If it helps: I am running Windows 10  Enterprise with the highest UAC setting.

    1. Did you opt to let DisplayCAL profile loader handle calibration loading when installing the software, or did you initially opt to let Windows handle calibration loading on its own?

      1. Alright. So in your case, the task scheduler entry wasn’t created by the installer, and thus the fallback code should have created an old-fashioned autostart entry for the profile loader (please check if such entry exists) and also tried to launch the loader as it wasn’t yet running (as expected). I think the original meaning of the --skip option was to prevent the loader from loading calibration when launched right after profile installation, as this action is unnecessary right after installation of the profile (which already loads the calibration). The meaning must have been lost along the evolution of the profile loader, and I probably need to restore it so that the fallback code can do its job in case it is still needed.

  5. I am 90% sure (I was really excited to perform my first ever calibration&profiling!) I let DisplayCAL profile loader handle calibration loading, as I read that Windows profile loading is low quality(?). I must admit that until today the old profiles were loaded without DisplayCAL (only by Windows), as I have downloaded DisplayCAL today 10:50.

  6. Additional info, perhaps it helps somehow: I let DisplayCAL install new profile as system-wide. But loader was not loaded.

  7. Yes, I can see the shortcut in “C:\Users\admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup”

    1. Ok, that’s good. So the only thing that didn’t work as intended was that the profile loader couldn’t be auto-launched right after profile installation. Will be fixed with the next release. It should still be interesting to see why creating the task scheduler entry failed initially. If you want, re-run the setup.exe, and check if the problem is reproducible.

    1. Ah, so that’s why 🙂 The task scheduler entry is actually created by the profile loader itself when it is run with admin rights (which the setup does).

Comments are closed.