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

Fancy zones not working! #19310

Closed
1 task done
cert-mkubica opened this issue Jul 11, 2022 · 11 comments
Closed
1 task done

Fancy zones not working! #19310

cert-mkubica opened this issue Jul 11, 2022 · 11 comments
Labels
Issue-Bug Something isn't working Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@cert-mkubica
Copy link

Microsoft PowerToys version

0.60.0

Running as admin

  • Yes

Area(s) with issue?

FancyZones

Steps to reproduce

After update fancy zones to v0.60.0 fancy zones not work at all

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Other Software

No response

@cert-mkubica cert-mkubica added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Jul 11, 2022
@MiLeX84
Copy link

MiLeX84 commented Jul 11, 2022

#19298

@SeraphimaZykova
Copy link
Collaborator

/bugreport

@ghost ghost added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Jul 11, 2022
@ghost
Copy link

ghost commented Jul 11, 2022

Hi there!

We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here? You right click on our system tray icon and just go to report bug. Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks!
Report Bug

@zach-hunt
Copy link

PowerToysReport_2022-07-11-13-23-42.zip
I have the exact same issue, except on three monitors. Monitor 3 changes to a default when PowerToys is opened, and monitor 2 changes to whatever 3 was supposed to be.

@jaimecbernardo
Copy link
Collaborator

What does not work at all mean for you? Do you get zones shown when shift dragging a Windows? Can you set layouts in FancyZones Editor?

@jaimecbernardo
Copy link
Collaborator

@ZacharyPH , you issue might be this: #19203 (comment)

@cert-mkubica
Copy link
Author

cert-mkubica commented Jul 12, 2022

I cannot open fancyzones and configure them. I added a report bug

PowerToysReport_2022-07-12-11-41-22.zip

PowerToysReport_2022-07-12-11-50-10.zip

And I tested debug version, still not work at all

@ghost ghost added Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Needs-Team-Response An issue author responded so the team needs to follow up and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jul 12, 2022
@jaimecbernardo
Copy link
Collaborator

[11:42:00.2637407] [Error] App::OnUnhandledException
    Unhandled exception
Object reference not set to an instance of an object.
Inner exception: 

Stack trace: 
   at FancyZonesEditor.Overlay.ShowLayout()
   at FancyZonesEditor.Overlay.Show()
   at FancyZonesEditor.App.OnStartup(Object sender, StartupEventArgs e)
   at System.Windows.Application.OnStartup(StartupEventArgs e)
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   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 System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   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 System.Threading.ExecutionContext.Run(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 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.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.Run()
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at System.Windows.Application.Run()
   at FancyZonesEditor.App.Main()

@jaimecbernardo
Copy link
Collaborator

/dup #19223 instead.

Can you please give this other build a try instead and continue discussion in that issue? Thank you!
#19223 (comment)

@ghost
Copy link

ghost commented Jul 12, 2022

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jul 12, 2022
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Needs-Team-Response An issue author responded so the team needs to follow up labels Jul 12, 2022
@cert-mkubica
Copy link
Author

the #19223 still not solve the issue.
Bug is still there

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug Something isn't working Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

5 participants