CLion Linux errors in terminal on start

Getting back to C++ and wanted to try CLion for use on Linux (actually Windows Subsytem for Linux (WSL ) in this case, Unbuntu 22.04).

Installed the trial yesterday and I'm sure it worked just fine, but today the startup dumps a load of text errors in the terminal it was started from.  A small sample below:

Debug | ByteBufferAsyncProcessor  | 22:DefaultDispatcher-worker-5 | PAUSE ('Socket not connected') :: {id = FrontendToBackend/Sender, state = 'Initialized'}
Debug | Server                    | 58:FrontendToBackend | FrontendToBackend: listening /127.0.0.1:36149
2024-12-20 10:27:40,309 [    854]   WARN - #c.i.s.ComponentManagerImpl - `preload=TRUE` must be used only for core services (service=com.jetbrains.rdclient.util.tests.RdClientDistributedTestHost, plugin=org.jetbrains.plugins.clion.radler)
2
etc. etc.

--- EXCEPTION #1/2 [AsyncAccessOnlySyncGetValueException]
Message = “Sync GetValue for IEnumerable<JetBrains.TextControl.ITextControlCreatorWarmUpListener> is prohibited (Instantiation contains AsyncAccessOnly flag)”
ExceptionPath = Root.InnerException
ClassName = JetBrains.Application.Components.AsyncAccessOnlySyncGetValueException
HResult = COR_E_INVALIDOPERATION=80131509

--- EXCEPTION #2/2 [LoggerException]
Message = “Sync GetValue for IEnumerable<JetBrains.TextControl.ITextControlCreatorWarmUpListener> is prohibited (Instantiation contains AsyncAccessOnly flag)”
InnerException = “Exception #1 at Root.InnerException”
StackTraceString = “
  at JetBrains.Util.LoggerBase.Log(LoggingLevel level, String message, Exception ex) in Log.il:line IL_0024 mvid 03FF
     at JetBrains.Diagnostics.LogEx.Error(ILog this, Exception ex, String message) in Error.il:line IL_0000 mvid 2A6A
     at JetBrains.Application.Components.AsyncDescriptorBase.AssertAsyncOnlyAccess() in AssertAsyncOnlyAccess.il:line IL_003E mvid 887E
     at JetBrains.Application.Components.AsyncDescriptorBase.GetValue() in GetValue.il:line IL_000E mvid 887E or GetValue.il:line IL_001A mvid 887E
     at JetBrains.Application.Components.AsyncLazyValueResolver.AsyncLazyDescriptor`1.get_Value()
... etc.

I should point out it does start and is usable - but a bit ugly to get those each time