Flow Launcher does not work after Windows has been suspended (Parallels on Mac)

[Greven-of-Norway]

I am not sure if this is an issue only when running Flow under Parallels on a Mac or not, but in Parallels you can Suspend the Windows VM and when Windows is resumed, Flow no longer workd. After resuming: prior to version 1.9 at least right clicking on the icon in the task bar showed me the menu (though the menu did not work) and launhcing Flow with the keyboard shortcut would pop up, but it would not accept any input. After version 1.9 the icon does not respond and the keyboard shortcut does nothing. I have to force quit Flow from Task manager and start it again to make it work.

I first encountered this problem on the version I had before I upgraded to 1.9, but unfortunately I don't know which version that was. When looking at the logs in %AppData%\FlowLauncher\Logs I see I have logs for versions 1.9.1, 1.8.3 and 1.8.0, so most likely 1.8.0 was the last one that did not have this problem.

When I use the Window Spy tool (from Autohotkey) I see that when I press the keyboard shortcut after resuming a VM, the Flow Launcher process is actually activated and receives focus (i.e. the application I was in loses focus), but it does not show up visually and it does not accept any input either.

Your System

Windows build number: Microsoft Windows [Version 10.0.19042.1415]
Flow Launcher version: 1.9.1

Flow Launcher Error Log

2022-01-07.txt

[taooceros]

Are you in m1 Mac?

[Greven-of-Norway]

No, it's Intel (2009 Mac Pro)

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[taooceros]

Sorry for the very delayed reply. I currently have no idea about this. The reason of the different behavior of 1.9+ should because we use wpf flyout instead of winform flyout for the icon after 1.9. Therefore, i guess the reason may be responsible to wpf.

[jjw24]

Hey I was able to reproduce this actually using recent Parallels but haven't had the time to look into it.

I use to have a shortcut on my taskbar that terminates and relaunches flow if this helps for the time being.

[github-actions]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[onesounds]

memo : We are currently using a software render, so this issue should have been resolved.

references

• WPF Rendering issue on any machine dotnet/wpf#4276
• BUG: Flyouts not showing after WIN+L Kinnara/ModernWpf#364

[github-actions]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[jjw24]

Still getting this error on Parallels.

[github-actions]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.