Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System.Runtime.InteropServices.COMException: Element not found. (0x8002802B (TYPE_E_ELEMENTNOTFOUND)) #270

Open
ZahiriNatZuke opened this issue Jul 4, 2024 · 1 comment
Labels
stale Issue has not been updated recently and will be closed

Comments

@ZahiriNatZuke
Copy link

Describe the bug
Observing the following error:

System.Runtime.InteropServices.COMException (0x8002802B): Element not found. (0x8002802B (TYPE_E_ELEMENTNOTFOUND))
   at WinMan.Windows.Com.IComApplicationViewCollection.GetViewForHwnd(IntPtr hwnd, IComApplicationView& view)
   at WinMan.Windows.Windows.Win32VirtualDesktopService22631R3085.MoveToDesktop(IntPtr hWnd, Desktop desktop)
   at WinMan.Windows.FaultTolerantWin32VirtualDesktopService.<>c__DisplayClass16_0.<MoveToDesktop>b__0()
   at WinMan.Windows.FaultTolerantWin32VirtualDesktopService.ExecuteWithRetry(Action action)
   at WinMan.Windows.FaultTolerantWin32VirtualDesktopService.MoveToDesktop(IntPtr hWnd, Desktop desktop)
   at WinMan.Windows.Win32VirtualDesktop.MoveWindow(IWindow window)
   at FancyWM.MainWindow.OnMoveToDesktopHotkeyPressed(Int32 desktopIndex)
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_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.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 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.22631.0
  • FancyWM Version: 2.14.0.0

Additional context
Add any other context about the problem here.

Copy link

github-actions bot commented Oct 3, 2024

This issue is stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the stale Issue has not been updated recently and will be closed label Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issue has not been updated recently and will be closed
Projects
None yet
Development

No branches or pull requests

1 participant