#5110 (Bug) upgrade 3.1.7.2 -> 3.2.2 on Windows 10 x64 did not upgrade profile loader

+1 0

Closed as Fixed
Component: DisplayCAL 0install Setup (Windows)
Created by

Last modified


Setup:
Windows 10 x64
Clevo based laptop with Intel HD4000 + NVidia 680m

Steps

  1. I launched dispcal today (was 3.1.7.2).
  2. Zero install said it had an update for itself.
  3. I accepted to update zero install.
  4. In parallel, dispcal ran and I got the dispcal update modal dialog box.
  5. I clicked cancel on the dispcal update model dialog box. My intention was to let zero install do the update rather than the dispCAL built-in.
  6. Someone (unclear if it was zero install or dispCAL) then showed a window of an update occurring. I think it was zero install because it had text similar to "waiting for all zero install instances"
  7. All the windows and dialogs doing installs/upgrades closed.
  8. I rebooted because the things that happened seemed suspicious

Result

DisplayCAL 3.2.2 app is installed. When I run this full app, it is 3.2.2
Profile Loader 3.1.7.2 is installed. When I click on the icon in the tray, it has version 3.1.7.2 in it and the old menu entry "Open Windows Color Management Settings..."

I can probably fix the mismatched versions by forced update or un/install. However, do you want any info from me before I do that?


DisplayCAL-logs (application/x-gzip | 2016-12-14 15:13:18)
error1 (image/png | 2016-12-15 01:37:01)
DisplayCAL-logs2 (application/x-gzip | 2016-12-15 01:37:35)


6 thoughts on “upgrade 3.1.7.2 -> 3.2.2 on Windows 10 x64 did not upgrade profile loader”

  1. Zero install said it had an update for itself.

    I clicked cancel on the dispcal update model dialog box. My intention was to let zero install do the update rather than the dispCAL built-in.

    Note that this really only updates Zero install itself, not DisplayCAL.

    Someone (unclear if it was zero install or dispCAL) then showed a window of an update occurring. I think it was zero install because it had text similar to “waiting for all zero install instances”

    Yes, this is the normal sequence of events when Zero Install updates itself.

    All the windows and dialogs doing installs/upgrades closed.

    I rebooted because the things that happened seemed suspicious

    Nothing to worry about. Here’s what happened:

    As mentioned. the Zero Install update was a self-update of only Zero Install itself. So, naturally, after the reboot, DisplayCAL was still at 3.1.7.2, so this is the version of the profile loader that launched. But, by the mere act of launching, the update to DisplayCAL 3.2.2 was completed by Zero Install in the background (due to the periodic checks it does), and that was why when you launched DisplayCAL, it launched the freshly downloaded 3.2.2. But note that this auto-update will not (and cannot) restart the profile loader automatically.  After manually closing and re-launching it (or logging out and back in), it should show 3.2.2.

    *Edit* I should have looked at the logs. You have the standalone version of DisplayCAL installed as well, and that is still 3.1.7.2. Re-download the DisplayCAL 0install setup and run it, it should remove the standalone version during installation.

  2. I encountered an error. Steps…

    downloaded DisplayCAL 0install setup
    Ran it
    Started through typical Wizard Setup UI

    Result
    A setup error model dialog appears. In the background, the Wizard progress bar is red. (Screenshot attached)
    It seems to be in the creating shortcuts phase.
    IPersistFile::Save failed; code 0x80070003. The system cannot find the path specified.

    4. I clicked OK on the error dialog. It is the only possible thing to do.
    5. Then Wizard progress bar turned green.
    6. Another dialog box appeared “Integrate DisplayCAL”.  Start Menu is selected. Desktop is not selected.
    7. clicked OK
    8. Setup Wizard dialog says Setup has finished installing.
    9. I left both readme and launch displayCAL selected.
    10. Clicked Finish

    Result

    DisplayCAL 3.2.2 launched. No immediately seen issues.
    Profile Loader 3.2.2 launched. No immediately seen issues.
    (I attached log files again)

    Attachment:
  3. The error message seems to be related to creating start menu entries, namely the main application entry. Can you confirm if the start menu entry exists?

  4. In Win10, I do visually see a DisplayCAL shortcut group and inside it there are 14 entries. One of those 14 is the DisplayCAL shortcut to the app.

    When I look at the hard drive, I found…

    C:\Users\Dale\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\DisplayCAL
    has 10 shortcuts (one of those 10 is the DisplayCAL shortcut to the app)
    all 10 shortcuts have a modified date of 16 Feb 2016   (10 months ago)

    C:\ProgramData\Microsoft\Windows\Start Menu\Programs\DisplayCAL
    has 3 shortcuts + 2 internet shortcuts
    The one shortcut in this folder that does not appear in the Windows menu group is “Uninstall DisplayCAL”
    all 5 shortcuts have a modified date of 15 Dec 2016   (these match my recent install datetime)

  5. Alright. I think everything’s fine, but the installation error is probably caused by a (harmless) race condition when creating the first shortcut (which is the DisplayCAL shortcut in C:\ProgramData\Microsoft\Windows\Start Menu\Programs\DisplayCAL, which seems to be missing in your case, which makes sense given the error. Note that this is not related to the DisplayCAL shortcut in C:\Users\Dale\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\DisplayCAL, although both will launch DisplayCAL). I’ve updated the DisplayCAL 0install setup to wait two seconds after uninstalling the previous version during installation, which should prevent the race condition.

Comments are closed.