Graybooked
commented
2 months ago Culprit found, bug is NOT FIXED and will likely appear on first launch for any user who did not choose to optionally install zebar, but bug is REASONABLY USER-CIRCUMNAVIGABLE by simply going into the settings file config.yaml and commenting out the first argument after general by adding a # before startup_commands like so:
# startup_commands: ['shell-exec %userprofile%/.glzr/zebar/start.bat']
Describe the bug
Non-fatal error window appears containing following:
Failed to execute '%userprofile%/.glzr/zebar/start.bat'. Error: Program path is not valid for command '%userprofile%/.glzr/zebar/start.bat'.
Occurs on fresh install of current latest version of GlazeVM, after having unchecked the allegedly optional zebar installation option.
I am on the latest version of Windows 11 as of writing and a first time user of this program. I predict replicability if you don't check that option on a fresh install on latest W11.
Reproduction
Occurs on fresh install of current latest version of GlazeVM, after having unchecked the allegedly optional zebar installation option.
I am on the latest version of Windows 11 as of writing and a first time user of this program. I predict replicability if you don't check that option on a fresh install on latest W11.
Stack trace or error logs (if applicable)
''' [2m2024-09-01T03:51:40.741710Z[0m [31mERROR[0m [2mglazewm::common::commands::shell_exec[0m[2m:[0m [3merr_message[0m[2m=[0m"Failed to execute '%userprofile%/.glzr/zebar/start.bat'.\n\nError: Program path is not valid for command '%userprofile%/.glzr/zebar/start.bat'." [2m2024-09-01T03:52:09.161135Z[0m [31mERROR[0m [2mglazewm::common::commands::shell_exec[0m[2m:[0m [3merr_message[0m[2m=[0m"Failed to execute '%userprofile%/.glzr/zebar/start.bat'.\n\nError: Program path is not valid for command '%userprofile%/.glzr/zebar/start.bat'." '''
Version number
Latest