hugodejong
Results
2
comments of
hugodejong
Same issue for me, similar messages in the log and reported events. Strange enough, reverting back to the previous version 1.36.0 does not seem to resolve the issue.
@krhermans Force-removing and repairing has not resolved this issue for me. I guess we'll have to wait until the next release?