starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[BUG]: When starting Komorebi with minimized windows they are not managed #268

New Issue
Closed
opened 2026-01-05 14:49:23 +01:00 by adam · 7 comments
adam commented 2026-01-05 14:49:23 +01:00
Owner
Copy Link

Originally created by @allora on GitHub (Dec 11, 2023).

Describe the bug
When i start komorebi and have some windows minimized, komorebi will not manage the minimized window and i have no idea how to make it do so without first stopping komorebi and unminimizing everything and starting it again.

To Reproduce
Steps to reproduce the behavior:

  1. Stop komorebi
  2. Minimize a window
  3. Start Komorebi
  4. See bug

Expected behavior
I expected all windows to be included in the tile management

Screenshots and Videos
I can add these if needed

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

OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.19045 N/A Build 19045

komorebic check Output
Provide the output of komorebic check

No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\Allie

Looking for configuration files in C:\Users\Allie

No komorebi configuration found in C:\Users\Allie

If running 'komorebic start --await-configuration', you will manually have to call the following command to begin tiling: komorebic complete-configuration

Additional context
Pretty much a default basic setup as described in the readme. No additional window placement tools or hotkey daemons

This is a multi monitor setup

Originally created by @allora on GitHub (Dec 11, 2023). **Describe the bug** When i start komorebi and have some windows minimized, komorebi will not manage the minimized window and i have no idea how to make it do so without first stopping komorebi and unminimizing everything and starting it again. **To Reproduce** Steps to reproduce the behavior: 1. Stop komorebi 2. Minimize a window 3. Start Komorebi 4. See bug **Expected behavior** I expected all windows to be included in the tile management **Screenshots and Videos** I can add these if needed **Operating System** Provide the output of `systeminfo | grep "^OS Name\|^OS Version"` ``` OS Name: Microsoft Windows 10 Pro OS Version: 10.0.19045 N/A Build 19045 ``` **`komorebic check` Output** Provide the output of `komorebic check` ``` No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\Allie Looking for configuration files in C:\Users\Allie No komorebi configuration found in C:\Users\Allie If running 'komorebic start --await-configuration', you will manually have to call the following command to begin tiling: komorebic complete-configuration ``` **Additional context** Pretty much a default basic setup as described in the readme. No additional window placement tools or hotkey daemons This is a multi monitor setup
adam added the bug label 2026-01-05 14:49:23 +01:00
adam closed this issue 2026-01-05 14:49:23 +01:00
adam commented 2026-01-05 14:49:23 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Dec 12, 2023):

This is definitely strange behaviour - could you attach a video of this? I've tried to trigger this with various windows but have not been successful. Is this behaviour specific to a group of windows/applications for you, or does it happen with all windows/apps?

It would also be helpful if you can get komorebic log running on a terminal while you reproduce it for the video and share those logs.

@LGUG2Z commented on GitHub (Dec 12, 2023): This is definitely strange behaviour - could you attach a video of this? I've tried to trigger this with various windows but have not been successful. Is this behaviour specific to a group of windows/applications for you, or does it happen with all windows/apps? It would also be helpful if you can get `komorebic log` running on a terminal while you reproduce it for the video and share those logs.
adam commented 2026-01-05 14:49:23 +01:00
Author
Owner
Copy Link

@allora commented on GitHub (Dec 12, 2023):

Here is the video and the log it created

https://github.com/LGUG2Z/komorebi/assets/12771565/bc4831a7-73de-49e1-9d15-8d72ba7df350

komorebic.log

@allora commented on GitHub (Dec 12, 2023): Here is the video and the log it created https://github.com/LGUG2Z/komorebi/assets/12771565/bc4831a7-73de-49e1-9d15-8d72ba7df350 [komorebic.log](https://github.com/LGUG2Z/komorebi/files/13652252/komorebic.log)
adam commented 2026-01-05 14:49:23 +01:00
Author
Owner
Copy Link

@allora commented on GitHub (Dec 12, 2023):

OH sorry forgot to mention:
This happens when i change desktops on any of my monitors, it doesnt really matter what application is there, as you can see in the video its notepad in this case. But when i switch desktops alt acts like its held, so modifies what keypresses mean for that app.

@allora commented on GitHub (Dec 12, 2023): OH sorry forgot to mention: This happens when i change desktops on any of my monitors, it doesnt really matter what application is there, as you can see in the video its notepad in this case. But when i switch desktops alt acts like its held, so modifies what keypresses mean for that app.
adam commented 2026-01-05 14:49:23 +01:00
Author
Owner
Copy Link

@Insprill commented on GitHub (Apr 23, 2024):

I can reliably reproduce this for most applications that Komorebi previously had cloaked. Reproducing is as easy as:

  1. Move an application to workspace 2.
  2. Go to workspace 1 and kill Komorebi.
  3. Start Komorebi.
  4. Refocus the application from the taskbar.

I've recorded a video showcasing this happening with bs-manager, an Electron application. I've been able to successfully reproduce it with several other applications made with Electron and Unity. However, as seen in the video, I've not been able to reproduce it with Firefox. You can also see that Komorebi isn't sure what to do with the window border when interacting with one of these bugged windows.

https://github.com/LGUG2Z/komorebi/assets/52843537/c46a78b5-b232-44b9-b952-a3fa0aa6efec

@Insprill commented on GitHub (Apr 23, 2024): I can reliably reproduce this for most applications that Komorebi previously had cloaked. Reproducing is as easy as: 1. Move an application to workspace 2. 2. Go to workspace 1 and kill Komorebi. 3. Start Komorebi. 4. Refocus the application from the taskbar. I've recorded a video showcasing this happening with bs-manager, an Electron application. I've been able to successfully reproduce it with several other applications made with Electron and Unity. However, as seen in the video, I've not been able to reproduce it with Firefox. You can also see that Komorebi isn't sure what to do with the window border when interacting with one of these bugged windows. https://github.com/LGUG2Z/komorebi/assets/52843537/c46a78b5-b232-44b9-b952-a3fa0aa6efec
adam commented 2026-01-05 14:49:23 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Apr 23, 2024):

@Insprill thanks for sharing this video which clearly shows what's happening with the logs in the background!

3370e6acc5/komorebi/src/process_event.rs (L587)

Uncloak is currently deliberately unmanaged which is why you're seeing this behaviour; I too come up against this sporadically with Electron apps, and the workaround I am using for now is to minimize and restore to force the system to send the restore event instead of the uncloak event.

I'll brainstorm if there are any heuristics we might be able to use to allow us to handle this specific subset of uncloak events.

@LGUG2Z commented on GitHub (Apr 23, 2024): @Insprill thanks for sharing this video which clearly shows what's happening with the logs in the background! https://github.com/LGUG2Z/komorebi/blob/3370e6acc55dc57a541819adb282de5134dd9d0c/komorebi/src/process_event.rs#L587 Uncloak is currently [deliberately unmanaged](https://github.com/LGUG2Z/komorebi/pull/768#issuecomment-2060331047) which is why you're seeing this behaviour; I too come up against this sporadically with Electron apps, and the workaround I am using for now is to minimize and restore to force the system to send the restore event instead of the uncloak event. I'll brainstorm if there are any heuristics we might be able to use to allow us to handle this specific subset of uncloak events.
adam commented 2026-01-05 14:49:23 +01:00
Author
Owner
Copy Link

@allora commented on GitHub (Apr 24, 2024):

Huh, sorry i didnt even realize that for whatever reason my uploaded video wasnt playable x_x Glad you got one (right clicking and saving as does seem to work tho)

@allora commented on GitHub (Apr 24, 2024): Huh, sorry i didnt even realize that for whatever reason my uploaded video wasnt playable x_x Glad you got one (right clicking and saving as does seem to work tho)
adam commented 2026-01-05 14:49:24 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (May 12, 2024):

I believe this was fixed here: 07b2da69a1

@LGUG2Z commented on GitHub (May 12, 2024): I believe this was fixed here: https://github.com/LGUG2Z/komorebi/commit/07b2da69a1d132caaee1975752ef695a8ea15ce3
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#268
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?