Originally created by @maaa3 on GitHub (Apr 2, 2023).
Describe the bug
Komorebi tiles windows almost like there is a invisible window.
To Reproduce
This seems to happen randomly.
Expected behavior
I expect the entire screen to be used.
Operating System
OS Name: Microsoft Windows 10 Enterprise LTSC
OS Version: 10.0.17763 N/A Build 17763
Originally created by @maaa3 on GitHub (Apr 2, 2023).
**Describe the bug**
Komorebi tiles windows almost like there is a invisible window.


**To Reproduce**
This seems to happen randomly.
**Expected behavior**
I expect the entire screen to be used.
**Operating System**
```
OS Name: Microsoft Windows 10 Enterprise LTSC
OS Version: 10.0.17763 N/A Build 17763
```
adam
added the bug label 2026-01-05 14:48:52 +01:00
Komorebi does not know which applications do and do not produce ghost tiles; they must be specified by the user and handled appropriately in the configuration file.
If you can provide your current config file and a copy of the komorebic state output at a time when the ghost tile is visible we should be able to help you identify the application causing the ghost tile and how to handle it.
@LGUG2Z commented on GitHub (Apr 2, 2023):
Komorebi does not know which applications do and do not produce ghost tiles; they must be specified by the user and handled appropriately in the configuration file.
If you can provide your current config file and a copy of the `komorebic state` output at a time when the ghost tile is visible we should be able to help you identify the application causing the ghost tile and how to handle it.
For people searching for a solution: For me, Skype was the application that was producing a ghost tile.
Possibly it has something to do with applications that minimize to tray instead of actually closing? (this is speculation)
@CoenKonings commented on GitHub (Apr 3, 2023):
For people searching for a solution: For me, Skype was the application that was producing a ghost tile.
Possibly it has something to do with applications that minimize to tray instead of actually closing? (this is speculation)
@LGUG2Z commented on GitHub (Apr 3, 2023):
Reminder to everyone that if you find a new case not covered by https://github.com/LGUG2Z/komorebi-application-specific-configuration, please open a PR so that it "just works" for others in the future. :pray:
Closing as there was no further information given by the original user and this should likely be handled using the various configuration options available.
@LGUG2Z commented on GitHub (Apr 26, 2023):
Closing as there was no further information given by the original user and this should likely be handled using the various configuration options available.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @maaa3 on GitHub (Apr 2, 2023).
Describe the bug
Komorebi tiles windows almost like there is a invisible window.
To Reproduce
This seems to happen randomly.
Expected behavior
I expect the entire screen to be used.
Operating System
@LGUG2Z commented on GitHub (Apr 2, 2023):
Komorebi does not know which applications do and do not produce ghost tiles; they must be specified by the user and handled appropriately in the configuration file.
If you can provide your current config file and a copy of the
komorebic stateoutput at a time when the ghost tile is visible we should be able to help you identify the application causing the ghost tile and how to handle it.@CoenKonings commented on GitHub (Apr 3, 2023):
For people searching for a solution: For me, Skype was the application that was producing a ghost tile.
Possibly it has something to do with applications that minimize to tray instead of actually closing? (this is speculation)
@LGUG2Z commented on GitHub (Apr 3, 2023):
Reminder to everyone that if you find a new case not covered by https://github.com/LGUG2Z/komorebi-application-specific-configuration, please open a PR so that it "just works" for others in the future. 🙏
@LGUG2Z commented on GitHub (Apr 26, 2023):
Closing as there was no further information given by the original user and this should likely be handled using the various configuration options available.