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]: Komorebi compatiblity with MS Teams #291

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

Originally created by @tardyp on GitHub (Jan 31, 2024).

Describe the bug

I see various issues when using teams with a komorebi setup.
When I open a call with teams, the application opens another window, which appears to be be not detected by komorebi.
It stays floating when open

Usually I push the team call window in my secondary screen, and if I do so, the main team window is actually put in my secondary screen, while the call window stay floating in the secondary screen.

To Reproduce
Steps to reproduce the behavior:

install teams here: https://www.microsoft.com/fr-fr/microsoft-teams/download-app
2. call somebody
3. switch the call window to the seconday screen
4. the main window will be put to secondary screen by komorebi

Expected behavior
Team call window is recognised separately from Team main window

Screenshots and Videos
Difficult to make a video of this without publishing private info.

Operating System

OS Name:                   Microsoft Windows 11 Entreprise
OS Version:                10.0.22621 N/A Build 22621

komorebic check Output

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

Looking for configuration files in C:\Users\xxx

No komorebi configuration found in C:\Users\xxx

If running 'komorebic start --await-configuration', you will manually have to call the following command to begin tiling: komorebic complete-configuration
Originally created by @tardyp on GitHub (Jan 31, 2024). **Describe the bug** I see various issues when using teams with a komorebi setup. When I open a call with teams, the application opens another window, which appears to be be not detected by komorebi. It stays floating when open Usually I push the team call window in my secondary screen, and if I do so, the *main* team window is actually put in my secondary screen, while the call window stay floating in the secondary screen. **To Reproduce** Steps to reproduce the behavior: install teams here: https://www.microsoft.com/fr-fr/microsoft-teams/download-app 2. call somebody 3. switch the call window to the seconday screen 4. the main window will be put to secondary screen by komorebi **Expected behavior** Team call window is recognised separately from Team main window **Screenshots and Videos** Difficult to make a video of this without publishing private info. **Operating System** ``` OS Name: Microsoft Windows 11 Entreprise OS Version: 10.0.22621 N/A Build 22621 ``` **`komorebic check` Output** ``` No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\xxx Looking for configuration files in C:\Users\xxx No komorebi configuration found in C:\Users\xxx If running 'komorebic start --await-configuration', you will manually have to call the following command to begin tiling: komorebic complete-configuration ```
adam added the bug label 2026-01-05 14:49:31 +01:00
adam closed this issue 2026-01-05 14:49:31 +01:00
adam commented 2026-01-05 14:49:31 +01:00
Author
Owner
Copy Link

@tardyp commented on GitHub (Jan 31, 2024):

Here is the AHKSpy info for this kind of window
image

When doing koremic state, I can't find this window in the state.

Also, I realized that the bug is not only the other team window which is moved to the other monitor, but whatever window container that is behind the floating/unmanaged window.

If I do a minimize + restore cycle, then the teams window is managed correctly, and I don't have the issue anymore.

@tardyp commented on GitHub (Jan 31, 2024): Here is the AHKSpy info for this kind of window ![image](https://github.com/LGUG2Z/komorebi/assets/109859/b15b9259-80ec-4757-ab70-f83df95c8004) When doing koremic state, I can't find this window in the state. Also, I realized that the bug is not only the other team window which is moved to the other monitor, but whatever window container that is behind the floating/unmanaged window. If I do a minimize + restore cycle, then the teams window is managed correctly, and I don't have the issue anymore.
adam commented 2026-01-05 14:49:31 +01:00
Author
Owner
Copy Link

@kajedot commented on GitHub (Jun 5, 2024):

Hi,
for now I can share workaround with you. It scans for teams and outlook apps for new windows. Then minimizes and maximizes them so they are registered by komorebi.
https://github.com/kajedot/deal-with-windows/blob/main/komorebi_workaround.ahk

@kajedot commented on GitHub (Jun 5, 2024): Hi, for now I can share workaround with you. It scans for teams and outlook apps for new windows. Then minimizes and maximizes them so they are registered by komorebi. https://github.com/kajedot/deal-with-windows/blob/main/komorebi_workaround.ahk
adam commented 2026-01-05 14:49:32 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Jan 23, 2025):

We have not had any complaints about Teams in almost a year now. If any issues persist please re-open this thread.

@LGUG2Z commented on GitHub (Jan 23, 2025): We have not had any complaints about Teams in almost a year now. If any issues persist please re-open this thread.
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#291
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?