Profile does not load after restart

2010-09-21
2013-03-15
  • Hallo

    calibration and profiling work well, but after a restart of my PC the profile
    isn´t loaded into the LUT. An error is displayed. Here the log:

    2010-09-21 23:52:04,698 Befehlszeile:
    2010-09-21 23:52:04,698   dispwin
    2010-09-21 23:52:04,699     -v
    2010-09-21 23:52:04,699     -d1
    2010-09-21 23:52:04,699     -c
    2010-09-21 23:52:04,700     -I
    2010-09-21 23:52:04,700     FP937s.icc
    2010-09-21 23:52:04,700 
    2010-09-21 23:52:04,719 About to open dispwin object on the display
    2010-09-21 23:52:04,719 About to clear the calibration
    2010-09-21 23:52:04,719 About to install 'FP937s.icc' as display's default profile
    2010-09-21 23:52:04,719 Installed 'FP937s.icc' and made it the default
    2010-09-21 23:52:04,720 About to destroy dispwin object
    2010-09-21 23:52:04,720 ...ok.
    2010-09-21 23:54:05,560 Anzeigegeräteprofil konnte nicht geladen werden.
    

    Typing "dispwin -L" by hand and the profile get loaded into LUT.

    My system is Linux OpenSuse 11.3.

    Edgar

     
  • Florian Hoech
    Florian Hoech
    2010-09-23

    Hi,

    do you have maybe several displays? The 'error' could be about a 2nd
    unprofiled display (then it would not be an error per se, and I should
    probably make sure it is suppressed in the future). The messages from my
    profile loader are very generic atm unfortunately (and also the logging is not
    verbose), I need to work on those. You could try installing an updated version
    of the profile loader. You can get it here:

    http://dispcalgui.hoech.net/tmp/dispcalGUI-apply-
    profiles

    Make it executable (chmod +x dispcalGUI-apply-profiles) and copy to /usr/bin/,
    overwriting the existing one. No need to reboot,

    you can just type dispcalGUI-apply-profiles in a terminal. Now the logging
    should be more detailed and also the display number displayed in error
    messages.

     
  • Hallo

    I changed the file in /usr/bin and started it in a terminal to see what
    happens:

    edgar@linux-jgpt:~> dispcalGUI-apply-profiles
    
    Befehlszeile:
      oyranos-monitor
    
    WARNUNG 0,000000: oyOptions_s[47] oyranos_cmm_oyX1.c:773 oyX1Configs_Modify() 
      Could not obtain _ICC_PROFILE(_xxx) information for :0.0
    found 1 EDIDs
    EDID version: 1.3 in .0[16] "DFP-0"  "BenQ FP937s"
    sh: xcalib: Kommando nicht gefunden.
    WARNUNG 0,050000: [-1] oyranos_monitor.c:864 oyX1MonitorProfileSetup() Keine Grafikkartengammakurven im Profil: FP937s.icc
    
    Befehlszeile:
      dispwin
        -v
        -d1
        -L
        -V
    
    About to open dispwin object on the display
    Verify: '/home/edgar/.local/share/color/icc/devices/display/FP937s.icc' is NOT loaded (discrepancy 4.7%)
    About to destroy dispwin object
    

    I see that xcalib is missing but xcalib shoudn´t be ne necessary for dispwin.
    Or am I wrong?

    I only have one screen installed using the proprietary nvidia-driver.

    Btw: dispcalGui is a great tool!

    Edgar

     
  • Florian Hoech
    Florian Hoech
    2010-09-23

    xcalib shoudn´t be ne necessary for dispwin

    That's right. I think the problem in your case though is indeed that xcalib is
    missing (if oyranos is installed, it will be used to set the monitor profile
    by the dispcalGUI profile loader, and dispwin will only be used to verify that
    the calibration has been loaded). I wonder if oyranos-monitor does return a
    non-zero exit code if it fails, because if it does, actually the dispcalGUI
    profile loader should fall back to dispwin for the profile loading also. This
    seems not to be the case.

     
  • I played a little with oyranos-monitor. I cannot force another returncode than
    0. So the fallback cannot run. I don´t know, wether this is a common behavior
    of oyranos or only located on my system . I think I will play a little more
    with oyranos next days.

    Edgar

     
  • Florian Hoech
    Florian Hoech
    2010-09-25

    You are right. oyranos-monitor does emit a returncode of 0 on my system too,
    even in case of an error. I think I have been mistaken in my error handling.

     
  • julian
    julian
    2011-01-22

    I got a similar problem: Some days ago, automatic calibration loading on
    startup stopped working. I am not sure what happened (perhaps some package
    that was upgraded?), but now I get the message:

    Dispwin: Error - Failed to get the displays current ICC profile
    

    My color.jcnf file is:

    {
      "devices": {
        "display": {
          "1": {
            "NAME": ":0.0",
            "ICC_PROFILE": "/home/julian/.local/share/color/icc/devices/display/Screen 1 2010-12-22 120cdm² D6500 min nativ 2.2 HQ XYZLUT.icc"
          },
          "2": {
            "NAME": ":1.0",
            "ICC_PROFILE": "/home/julian/.local/share/color/icc/devices/display/Screen 1 2010-12-22 120cdm² D6500 min nativ 2.2 HQ XYZLUT.icc"
          }
        }
      }
    }
    

    My .local/share/color/icc/devices/display:

    ~/.local/share/color/icc/devices/display$ ls
    Screen 1 2010-12-21 120cdm² D6500 min nativ 2.2 LQ-HQ 3xGamma+MTX.icc
    Screen 1 2010-12-21 max nativ min nativ 2.2 MQ-HQ 1xCurve+MTX.icc
    Screen 1 2010-12-22 120cdm² D6500 min nativ 2.2 HQ XYZLUT.icc
    Screen 1 2010-12-22 120cdm² D6500 min nativ 2.2 LQ-HQ 3xCurve+MTX.icc
    Screen 1 2010-12-22 120cdm² D6500 min nativ 2.2 LQ-HQ 3xGamma+MTX.icc
    
     
  • julian
    julian
    2011-01-22

    Ah and I should add that the profile is loaded immediately when I start
    dispcalgui.. so what might be the problem?

     
  • Florian Hoech
    Florian Hoech
    2011-01-23

    Some graphics drivers install an utility which is loaded on startup and
    tinkers with the video carg gamma table (e.g. the proprietary nVidia driver's
    nvidia-settings is notorious for this). If that's the case, it is usually
    enough to disable that utility from autostart.

     
  • julian
    julian
    2011-01-23

    I have indeed a nvidia card, but removing nvidia-settings from startup did not
    change anything. Calling "dispcalGUI-apply-profiles" still gives the same
    error, and it makes no difference if nvidia-settings was started or not. What
    baffles me is that running dispcalGUI obviously applies the profile, it's just
    the command-line version "dispcalGUI-apply-profiles" that does not work
    anymore.

     
  • julian
    julian
    2011-01-23

    Ah, and if I run

     dispwin -v -d1 -c -I "Screen 1 2010-12-22 120cdm² D6500 min nativ 2.2 HQ XYZLUT.icc"
    

    in the correct directory on the command line, it also works.

    The same is running "bash .local/share/dispcalGUI/storage/Screen\ 1\ 2010-12-22\ 120cdm²\ D6500\ min\ nativ\ 2.2\ HQ\ XYZLUT/Screen\ 1\ 2010-12-22\ 120cdm²\ D6500\ min\ nativ\ 2.2\ HQ\ XYZLUT.dispwin.sh", which also works.

    I looked into the "dispcalGUI-apply-profiles" and it also calls dispwin but
    only with "-v -d1 -c -L", so how does it know which profile to load? Obviously
    that seems to be the problem. Because after running the scripts as above,
    "dispcalGUI-apply-profiles" works, until next reboot that is.

     
  • Florian Hoech
    Florian Hoech
    2011-01-24

    Calling "dispcalGUI-apply-profiles" still gives the same error

    Does it show an error dialog? If so, what is the message? (you may also look
    at the logfile under ~/.local/share/dispcalGUI/logs/dispcalGUI.log, it should
    also contain messages from the profile loader if any).

    dispwin's -L parameter (in conjunction with -d) tells it to use
    the configured profile from color.jcnf

    I don't know why this isn't working (anymore) in your case.

    The reason it works when opening dispcalGUI is because it will always load the
    calibration from the profile selected under "settings" (the dispwin
    commandline is something like dispwin -v -d1 <profile.icc>), which is not
    necessarily the same as the configured display profile.

    Are you maybe using other software thart tries to apply calibration curves on
    login? I recall some version of Gnome Color Manager under Ubuntu in
    conjunction with the proprietary nVidia driver causing the calibration loaded
    by dispwin to get un-loaded. I think this was fixed in recent versions of GCM,
    but I don't know if it has found its way into all distributions yet. If that
    is indeed the problem, disabling "gcm-apply-profiles" from autostart or
    switching from the proprietary NVidia driver to Noveau could help.

     
  • i too have the exact same problem as jhoch's. nvidia startup is disabled, and
    no gnome color manager installed.

     
  • I'm sorry I have not forgotten, the problem still is interesting and I will
    follow up on this.

    It's just that at the moment I am not at home for some time and don't have my
    desktop with me. As soon as I find the time, I will send logfiles.

    Sincerly, Julian Hoch

     
  • steve
    steve
    2011-06-04

    I also have this same problem. Ubuntu 10.10

    I have two monitors and the profile fails to load for d1 but loads correctly
    for d2, see extract from log file:

    ]2011-06-03 23:37:03,311 Loading calibration curves of current display device
    profile...

    2011-06-03 23:37:03,314 /usr/bin

    2011-06-03 23:37:04,000 Argyll CMS 1.1.1

    2011-06-03 23:37:04,243

    2011-06-03 23:37:04,243 Command line:

    2011-06-03 23:37:04,243 dispwin

    2011-06-03 23:37:04,244 -v

    2011-06-03 23:37:04,244 -d1

    2011-06-03 23:37:04,245 -c

    2011-06-03 23:37:04,245 -L

    2011-06-03 23:37:04,245

    2011-06-03 23:37:04,366 Dispwin: Error - Failed to get the displays current
    ICC profile

    2011-06-03 23:37:04,366 About to open dispwin object on the display

    2011-06-03 23:37:04,366 About to clear the calibration

    2011-06-03 23:37:04,366

    2011-06-03 23:37:04,367 Command line:

    2011-06-03 23:37:04,367 dispwin

    2011-06-03 23:37:04,367 -v

    2011-06-03 23:37:04,367 -d2

    2011-06-03 23:37:04,367 -c

    2011-06-03 23:37:04,367 -L

    2011-06-03 23:37:04,367

    2011-06-03 23:37:04,524 About to open dispwin object on the display

    2011-06-03 23:37:04,524 About to clear the calibration

    2011-06-03 23:37:04,524 About to set display to given calibration

    2011-06-03 23:37:04,524 Calibration set

    2011-06-03 23:37:04,525 About to destroy dispwin object

    2011-06-03 23:37:04,525

    2011-06-03 23:37:04,525 Command line:

    2011-06-03 23:37:04,525 dispwin

    2011-06-03 23:37:04,525 -v

    2011-06-03 23:37:04,525 -d2

    2011-06-03 23:37:04,526 -L

    2011-06-03 23:37:04,526 -V

    2011-06-03 23:37:04,526

    2011-06-03 23:37:04,649 About to open dispwin object on the display

    2011-06-03 23:37:04,649 Verify:
    '/home/drgrumpy/.local/share/color/icc/devices/display/SyncMaster-2 2011-06-01
    100cdm² native min native 2.2 MQ 3xCurve+MTX.icc' IS loaded (discrepancy 0.0%)

    2011-06-03 23:37:04,649 About to destroy dispwin object

    I checked color.jcnf and it looks correct.

    It seems that the profille can be installed:

    ~$ dispwin -v -d1 -I
    "/home/drgrumpy/.local/share/color/icc/devices/display/SyncMaster-1 2011-06-01
    100cdm² native min native 2.2 MQ 3xCurve+MTX.icc"

    About to open dispwin object on the display

    About to install
    '/home/drgrumpy/.local/share/color/icc/devices/display/SyncMaster-1 2011-06-01
    100cdm² native min native 2.2 MQ 3xCurve+MTX.icc' as display's default profile

    Installed '/home/drgrumpy/.local/share/color/icc/devices/display/SyncMaster-1
    2011-06-01 100cdm² native min native 2.2 MQ 3xCurve+MTX.icc' and made it the
    default

    About to destroy dispwin object

    But when verifying, note that the output doesn't display the file name as
    above:

    ~$ dispwin -v -d1 -L -V

    About to open dispwin object on the display

    Verify: '_ICC_PROFILE' IS loaded (discrepancy 0.0%)

    About to destroy dispwin object

     
  • steve
    steve
    2011-06-04

    I should also add ATI FireMV card using ubuntu standard driver, gnome-color-
    management not installed.

    Thanks,

    Steve

     
  • steve
    steve
    2013-03-14

    This problem still persists - after upgrading to Mint 13, and installing the latest version of dispcalGUI, I still have exactly the same error messages in the log as above The profile gets loaded for monitor 2, but not for monitor 1, my workround for the last year has been to manually force dispwin to load the profile.

    dispcal is still a great tool.

    Thanks, Steve

     


Anonymous


Cancel   Add attachments