mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: Top bar & window frame glitch. #251
Reference in New Issue
Block a user
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?
Originally created by @abidanBrito on GitHub (Oct 8, 2023).
Describe the bug
Some applications get displayed with an extra top bar that exceeds the width of the frame and no rounded corners. It seems to be some sort of glitch; maximizing, minimizing and snapping the window into place seems to solve the issue for a while.
Troublesome applications: Discord, LibreWolf.
To Reproduce
Steps to reproduce the behavior:
Expected behavior

No extra top bar & window frame with rounded corners.
Operating System
komorebic checkOutputAdditional context
No other window managers or hotkey daemons are being used. Default window snapping is also disabled.
@dna113p commented on GitHub (Oct 20, 2023):
I can reliably reproduce this by minimizing and maximizing windows and swapping workspaces. After you maximize a window - if you switch workspaces and then go back to the workspace that monitor is assigned to it will resize into its position and display like this. Minimizing the window restores the normal functionality.
@nullbyto commented on GitHub (Oct 24, 2023):
I have the same problem on some apps, when maximizing and minimizing normally using the window button. But with the command
komorebic toggle-maximize, this issue always happens in every app when executing this command.Example:

When I press the keybinding that executes this command twice: it maximizes the window and then minimizes, but if pressed again, then I cannot maximize again. The window button will look like this after minimizing with this window frame glitch:
Then to fix, I need to press with the mouse on the minimize button and then it actually minimizes.
@abidanBrito commented on GitHub (Oct 24, 2023):
I can reproduce it these ways too @dna113p , @nullbyto . Any clues on how to investigate this further?
@LGUG2Z commented on GitHub (May 13, 2024):
This was fixed a few versions back