[BUG]: komorebi doesn't seem to start after being killed

[symplrdudley]

Describe the bug

After performing Get-Process -Name:whkd | Stop-Process, I am unable to start komorebi and have whkd stay running. I have to then restart.

To Reproduce
Steps to reproduce the behavior:

1. Start komorebi: komorebic.exe start --await-configuration
2. Nothing happens and get impatient after 5min
3. Attempt to stop komorebi: komorebic stop
4. Nothing happens as whkd is still running.
5. Kill process: Get-Process -Name:whkd | Stop-Process
6. Attempt to start komorebi again: komorebic.exe start --await-configuration
7. Check if process is running: Get-Process -Name:whkd, yet nothing is running
8. Reboot and try again.

Expected behavior

I expect Komorebi to start and capture all my windows when first started after a reboot.

Screenshots and Videos
Add screenshots and videos to help explain your problem.

Operating System
Provide the output of systeminfo | grep "^OS Name\|^OS Version"

PS C:\Users\pdudley\AppData\Local\komorebi> systeminfo | grep "^OS Name\|^OS Version"
grep: The term 'grep' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Here's from just running systeminfo and selecting the fields needed

OS Name:                   Microsoft Windows 10 Enterprise
OS Version:                10.0.19045 N/A Build 19045
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation

komorebic check Output
Provide the output of komorebic check

For example:

PS C:\Users\pdudley\AppData\Local\komorebi> komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\pdudley

Looking for configuration files in C:\Users\pdudley

Found komorebi.ps1; this file will be autoloaded by komorebi

Found ~/.config/whkdrc; key bindings will be loaded from here when whkd is started

Additional context

No Auto Hot Keys or anything. We do have Sophos DLP (Digital Loss Protection) suite, which could potentially be blocking somethings, but I don't have access to any of those logs.

When I looked for the logs of $env:LOCALAPPDATA\komorebi\komorebi.log I didn't see any mentions of errors when started up even though none of the windows were seemingly being captured. My laptop did ramp up in CPU fan so something was attempting at happening.

[symplrdudley]

After I rebooted, and attempted to show the start up issues, Komorebi worked. I'm wondering if it was because I issued the date command afterwards, or it just happened to work this time. Third restart is the charm.

[eddyu0]

I was able to reproduce the bug occasionally just by smashing the focus windows shortcut quickly and whkd would start acting unstable or outright stop responding. See #448.

Killing both whkd and komorebi, and then restart komorebic seems to work for me.

get-process -name:whkd | stop-process
get-process -name:komorebi | stop-process

komorebic.exe start -a

[symplrdudley]

I'm leaving Komorebi running this week again to see if I encounter the same issues I did last week. I have intermittent start up times that either work quickly or it takes 5min or I need to kill and restart Komorebi to get it to work, even after a restart.

[symplrdudley]

Today is when Komorebi seems to have crashed. I restarted Komorebi using the two stop-process commands as described above.

I had to restart Outlook PWA (from Edge) as well for it to be captured by Komorebi.

[symplrdudley]

I don't see any errors in the $env:LOCALDATA\komorebi\komorebi.log but I did see where I restarted the application.

At this point, I'm not sure if it's Sophos DLP making it slow to run and I just pressed ALT+1/2/3 too fast.

[symplrdudley]

I have seen a the pattern of if I leave komorebi running for 4 days straight on my laptop, I have to stop komorebi and restart it.

Sometimes I have to Stop and Start komorebi to get certain configuration changes to work, and when doing that repeatedly, it doesn't seem to load every time. That's when I have to kill the windows that were open from the previous times and restart them for komorebi to capture them.

I am okay with this for now so I will close this issue.

Using the recommendation from @eddieyutc I made two scripts to help make the typing reduced.

<#
.SYNPSIS
  Stop-Komorebi.ps1
#>        

Write-Host "Stopping whkd"
Get-Process -Name:whkd | Stop-Process

Write-Host "Stopping komorebi"
Get-Process -Name:komorebi | Stop-Process

and

<#
.SYNOPSIS
  Start-Komorebi.ps1
#>       

Write-Host "Starting Komorebi"
& komorebic.exe start --await-configuration

[LGUG2Z]

Please also keep an eye on this issue (and test if you'd like!) #427

[mistertuna93]

Hey there, I figured its worth adding that I am experiencing a similar bug. I am currently doing my initial config, so I am far from an expert, but upon using Komorebic stop I am having issues getting it started again. It shows the normal reply in the PS window "Start-Process komorebi.exe -ArgumentList '--await-configuration' -WindowStyle hidden
Waiting for komorebi.exe to start...Started!" but seems the process never starts. I just discovered this so I can update when things progress.

BTW:
Windows 11 Pro N 22H2 22621.1848
Newest Release Komorebi
I am also using YASB