[Bug] explorer.exe needs to be running for zebar to properly launch

[dillacorn]

Describe the bug

zebar not launching if explorer.exe is not running.

Is this normal expected behavior?

Reproduction

I end task of explorer.exe.

I start GlazeWM that contains launch argument to start zebar.

general:
  # Commands to run when the WM has started. This is useful for running a
  # script or launching another application.
  # Example: The below command launches Zebar.
  startup_commands: ['shell-exec zebar']

zebar doesn't properly start..

I've come up with a workaround in my GlazeWM config

general:
  # Commands to run when the WM has started.
  startup_commands: [
    'shell-exec explorer.exe',  # Ensure explorer.exe is running initially for Zebar
    'shell-exec ping -n 3 127.0.0.1 > nul',  # Wait a few seconds for explorer.exe to stabilize
    'shell-exec zebar'  # Start Zebar with explorer.exe active
  ]

This starts explorer.exe then zebar successfully starts right after it.. I use flow-launcher to run elevated cmd to then kill explorer.exe as a quicker solution than using task manager.

taskkill /IM explorer.exe /F

zebar functions normally when I manually kill explorer.exe.. so why is it reliant on explorer.exe on start?

Stack trace or error logs (if applicable)

No response

Version number

2.4.0

[dillacorn]

I'm suspecting this is expected behavior.. unless the dev wants to re-open the issue if it's due to unexpected behavior.. but more than likely something in zebars code expects explorer.exe to be running.. I have no true issue with that but most programs non-related file programs require explorer.exe to be operational.. closing this issue