DisplayCAL

3 comments on “No such file in /private/var/folders/…/T/AppTranslocation/…”

1. Hi,

   because you’ve run the application once without disabling app translocation, some of the user-configured paths may point to the translocated location (which no longer exists). The solution is simple, go to the “Verification” tab, and select the correct chart (the lowest entry in the list is the last selected one which doesn’t exist). Same for the presets, the correct files are listed at the top.

2. Thanks.  I must apologize.  “It” worked, but I’m not sure what “it” was and  why “it” worked.

   In Verification I clicked the lowest entry in the list, received the error message about the invalid file, clicked “OK”, clicked an item on the top of the list and received no error message.  I could swear I then clicked the last item again, and it was still invalid.

   Then I went to the settings.  No matter which one I clicked, I received a question, whether I wanted to discard the current setting.  Not knowing what that meant, I canceled.  Finally, I decided to select a setting and let DisplayCAL discard the current setting.

   Calibration and profiling proceeded normally.  So, too, did verification.  No error messages.  SO:  What corrected the problem???  I’m almost sure that, before reporting the problem, I had clicked on one of the default presets, received the error message, dismissed it, calibrated and profiled, only to receive the same error message the next time I selected a default preset to calibrate and profile.   What convinced DisplayCAL to forget the invalid translocation location and find the correct one?  Same question, of course, for the settings.

   Thanks.

3. I could swear I then clicked the last item again, and it was still invalid.

   Yes, that is expected. In the list you only see the names, but not the paths behind them (but you can hover the dropdown with the mouse to get a tooltip showing the path).

   Then I went to the settings. No matter which one I clicked, I received a question, whether I wanted to discard the current setting. Not knowing what that meant, I canceled. Finally, I decided to select a setting and let DisplayCAL discard the current setting.

   When you load a preset, then it’ll load settings from that preset. Naturally, you might have changed some of the settings, which will then be overriden by loading the preset, so this is merely alerting you of that.

   SO: What corrected the problem???

   Like I said, just selecting the files(s) with the correct paths.

   I’m almost sure that, before reporting the problem, I had clicked on one of the default presets, received the error message, dismissed it, calibrated and profiled, only to receive the same error message the next time I selected a default preset to calibrate and profile.

   When you selected the old duplicate entry under the same name, this simply was still pointing to the (now non-existent) location. The same would happen if you deleted (in the Finder) your current settings file.

Comments are closed.