[BUG]: komorebi crashes when switching desktop
Summary
komorebi simply shuts down when i send commands to switch desktop either via bar or whkd
Version Information
komorebic 0.1.34 tag:v0.1.34 commit_hash:80edcadb build_time:2025-02-21 02:21:41 +00:00 build_env:rustc 1.85.0 (4d91de4e4 2025-02-17),stable-x86_64-pc-windows-msvc
Komorebi Configuration
{
"$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.34/schema.json",
"app_specific_configuration_path": "$Env:USERPROFILE/applications.json",
"window_hiding_behaviour": "Cloak",
"cross_monitor_move_behaviour": "Insert",
"default_workspace_padding": 5,
"default_container_padding": 5,
"border": true,
"border_width": 4,
"border_offset": -1,
"theme": {
"palette": "Base16",
"name": "Ashes",
"unfocused_border": "Base03",
"bar_accent": "Base0D"
},
"stackbar": {
"height": 40,
"mode": "OnStack",
"tabs": {
"width": 300
}
},
"monitors": [
{
"workspaces": [
{
"name": "I",
"layout": "BSP"
},
{
"name": "II",
"layout": "VerticalStack"
},
{
"name": "III",
"layout": "HorizontalStack"
},
{
"name": "IV",
"layout": "UltrawideVerticalStack"
},
{
"name": "V",
"layout": "Rows"
},
{
"name": "VI",
"layout": "Grid"
},
{
"name": "VII",
"layout": "RightMainVerticalStack"
}
]
}
]
}
Hotkey Configuration
.shell powershell
# Reload whkd configuration
# win + o : taskkill /f /im whkd.exe && start /b whkd # if shell is cmd
win + o : taskkill /f /im whkd.exe; Start-Process whkd -WindowStyle hidden # if shell is pwsh / powershell
win + shift + o : komorebic reload-configuration
# App shortcuts - these require shell to be pwsh / powershell
# The apps will be focused if open, or launched if not open
win + f : firefox
win + RETURN : wt
win + q : komorebic close
win + m : komorebic minimize
# Focus windows
win + h : komorebic focus left
win + j : komorebic focus edown
win + k : komorebic focus up
win + l : komorebic focus right
win + shift + oem_4 : komorebic cycle-focus previous # oem_4 is [
win + shift + oem_6 : komorebic cycle-focus next # oem_6 is ]
# Move windows
win + shift + h : komorebic move left
win + shift + j : komorebic move down
win + shift + k : komorebic move up
win + shift + l : komorebic move right
win + shift + return : komorebic promote
# Stack windows
win + left : komorebic stack left
win + down : komorebic stack down
win + up : komorebic stack up
win + right : komorebic stack right
win + oem_1 : komorebic unstack # oem_1 is ;
win + oem_4 : komorebic cycle-stack previous # oem_4 is [
win + oem_6 : komorebic cycle-stack next # oem_6 is ]
# Resize
win + oem_plus : komorebic resize-axis horizontal increase
win + oem_minus : komorebic resize-axis horizontal decrease
win + shift + oem_plus : komorebic resize-axis vertical increase
win + shift + oem_minus : komorebic resize-axis vertical decrease
# Manipulate windows
win + t : komorebic toggle-float
win + shift + f : komorebic toggle-monocl
# Window manager options
win + shift + r : komorebic retile
win + p : komorebic toggle-pause
# Layouts
win + x : komorebic flip-layout horizontal
win + y : komorebic flip-layout vertical
# Workspaces
win + 1 : komorebic focus-workspace 0
win + 2 : komorebic focus-workspace 1
win + 3 : komorebic focus-workspace 2
win + 4 : komorebic focus-workspace 3
win + 5 : komorebic focus-workspace 4
win + 6 : komorebic focus-workspace 5
win + 7 : komorebic focus-workspace 6
win + 8 : komorebic focus-workspace 7
# Move windows across workspaces
win + shift + 1 : komorebic move-to-workspace 0
win + shift + 2 : komorebic move-to-workspace 1
win + shift + 3 : komorebic move-to-workspace 2
win + shift + 4 : komorebic move-to-workspace 3
win + shift + 5 : komorebic move-to-workspace 4
win + shift + 6 : komorebic move-to-workspace 5
win + shift + 7 : komorebic move-to-workspace 6
win + shift + 8 : komorebic move-to-workspace 7
Output of komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\Nicol
Looking for configuration files in C:\Users\Nicol
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\Nicol.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
It would help if you look for some logs in your temp folder (see $Env:Temp folder). Files such as komorebi.log.2025-03-17 could contain important clues