System.ArgumentException: An item with the same key has already been added. Key: Win32Display { \\?\DISPLAY#GSM81CD#5&1f5d279b&0&UID4352#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} }

[XipiGamer]

Describe the bug
Observing the following error:

System.ArgumentException: An item with the same key has already been added. Key: Win32Display { \\?\DISPLAY#GSM81CD#5&1f5d279b&0&UID4352#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} }
   at System.Collections.Generic.Dictionary`2.TryInsert(TKey key, TValue value, InsertionBehavior behavior)
   at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
   at FancyWM.MultiDisplayTilingService..ctor(IWorkspace workspace, IAnimationThread animationThread, IObservable`1 settings)
   at FancyWM.MainWindow.<>c__DisplayClass37_5.<.ctor>b__27()
   at System.Windows.Threading.DispatcherOperation.InvokeDelegateCore()
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
--- End of stack trace from previous location ---
   at FancyWM.MainWindow.<>c__DisplayClass37_0.<<-ctor>b__17>d.MoveNext()
--- End of stack trace from previous location ---
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__124_0(Object state)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at FancyWM.Startup.AppMain(String[] args)
   at FancyWM.Startup.Main(String[] args)

To Reproduce
Steps to reproduce the behavior:

1. Open '...'
2. Resize '....'
3. Enable '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Desktop (please complete the following information):

• OS: Microsoft Windows NT 10.0.26200.0
• FancyWM Version: 2.18.4.0

Additional context
Add any other context about the problem here.

[rubyrubyp]

I also get this when launching FancyWM on startup.

I can only successfully launch it after changing my display configuration (disable/enable a display), after which FancyWM launches no problem.

It seems to only be on startup. After that first initial change I can close/reopen FancyWM with any display configuration and there's no problem.