I looked at the engine log out of curiosity and I’m worried by what I see there.
This part for instance:
2017-12-20 07:43:21 Engine Starting 8.0.4
2017-12-20 07:43:21 Old engine details remains a running process Running Engine Details/370
2017-12-20 07:43:22 Running application query took a while (3788 us)
2017-12-20 07:43:22 Invalid Plug In Action with Name Wrap Text
and the fact that there are hundreds of lines with Invalid Plug In Action with Name Wrap Text populating that log.
Does anyone know if/what I should do about that?
Tom answered:
Why haven’t you opened a new topic?
I have now
That means that at least one of your macros has an action that is based on a custom plugin “Wrap Text”, and that plugin is either missing or it is not compatible with KM8.
The plugins are located here:
~/Library/Application Support/Keyboard Maestro/Keyboard Maestro Actions
If the plugin is there, then update it or remove it. If you remove it then you should also remove the corresponding action(s) from your macros.
If it is not there, then install it or remove the orphaned action(s) from your macros.
Re:
07:43:21 Old engine details remains a running process Running Engine Details
I don’t know if this related to the plugin issue. There is a very similar thread here1, also about missing plugins, and this message is also mentioned. So, quite possible that it is related. Fix the plugin issue and then see if the “old engine” message still appears.
I’ve searched for Wrap Text and it found markdown macros. While I could not find any reference to a ‘Wrap Text’ action in any of them, I deleted the whole macro group and the invalid plugin message stopped in the engine log.
This part still persist after a reboot though:
2017-12-20 09:21:48 Engine Starting 8.0.4
2017-12-20 09:21:48 Old engine details remains a running process Running Engine Details/370
2017-12-20 09:21:49 Daemon launched by login window. Initiating login actions.
2017-12-20 09:21:49 Running application query took a while (3058 us)
) and I also have the “old engine” message. It appears exclusively after the “Engine Starting 8.0.4” message, that is, it appears only after engine (re)start.