System.InvalidOperationException: Sequence contains no matching element #453

Activity

1. github-actions commented on Jun 13, 2026

   

   github-actionsBot

   on Jun 13, 2026 – with GitHub Actions

   More actions

   This issue is stale because it has been open for 90 days with no activity.
2. github-actions

   added

   staleIssue has not been updated recently and will be closedIssue has not been updated recently and will be closed

   on Jun 13, 2026
3. github-actions commented on Jun 28, 2026

   

   github-actionsBot

   on Jun 28, 2026 – with GitHub Actions

   More actions

   This issue was closed because it has been inactive for 14 days since being marked as stale.
4. github-actions

   closed this as completedon Jun 28, 2026
5. yatahaze commented on Sep 27, 2026

   

   yatahaze

   on Sep 27, 2026

   Last edited by yatahaze

   More actions

   I'm also experiencing this...

   Describe the bug
   Observing the following error:

   System.InvalidOperationException: Sequence contains no matching element
      at System.Linq.ThrowHelper.ThrowNoMatchException()
      at System.Linq.Enumerable.First[TSource](IEnumerable`1 source, Func`2 predicate)
      at WinMan.Windows.Win32DisplayManager..ctor(Win32Workspace workspace)
      at WinMan.Windows.Win32Workspace.Open()
      at FancyWM.MainWindow..ctor()
      at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean wrapExceptions)
   

   To Reproduce
   Steps to reproduce the behavior:

   1. Restart computer if you want, just to keep it fresh
   2. Open the app

   Expected behavior
   The app to load.

   Desktop (please complete the following information):

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

   Additional context
   Used to work fine, not sure what happened.
6. yatahaze commented on Sep 27, 2026

   

   yatahaze

   on Sep 27, 2026

   More actions

   I found the cause for me. I had a 3rd monitor set up that I had disabled. When it's disabled, this app won't load and crashes like that. But if I re-enable that monitor the app works again.