Describe the bug
I added gnomeExtensions.tiling-shell to my nixconfig yesterday to my great enjoyment, but I'm repeatedly bumping into a bug that breaks rendering for certain windows. I have auto-tiling turned off, but I have suggestions turned on.
The broken windows fail to render, but if I mouse over where they 'should' be, I can see the focus outline appear. If I tap the super key, they still appear (live and running) in that selection view. If I double click the header bar area of the space a window should be, it 'maximizes', but is still not rendered - I can see from the super key view that it is maximized, though.
The issue seems to only occur with certain applications like Text Editor and Console, and whether it triggers seems to depend on what order I start tiling my windows in. I have a consistent repro recipe:
To Reproduce
Steps to reproduce the behavior:
- Launch a chromium window, a Text Editor window, and a Console window or two all in the same workspace (untiled, autotiling off).
- Super-click and drag the Chromium window into a tile
- Console Windows and Text Editor disappear
- Missing windows still appear if you tap the super key
- If focus outlines and sloppy focus are enabled, mousing over the areas the windows previously were will show the outline. The windows are active but not rendered.
- Issue persists through extension disable / re-enable, but everything resets after a logout or if I do the below:
If I mouse over my console windows and close them via keyboard, I can open new instances, tile them, and I'm good to go from there. The issue only occurs if I tile my browser first (and presumably other applications I haven't bumped into it with yet).
Screenshots
If a screen recording would be helpful, just let me know.
Information (please complete the following):
- Tiling Shell version:
17.3 (pulled by default via nixpkgs)
- GNOME version:
50
Additional context
This seems like maybe a GNOME 50 issue - claude's guess was it's a problem related to tile suggestions with v50, so I'm going to try turning those off and rebooting to see if it resolves the problem. But I like them so I'd like to keep them if I can :)
I saw the closed issue about 50 support being live, but I observed that the 17.3 branch does not include v50 in the manifest in resources/. Maybe there's an issue with what particular version is getting pulled in by nixpkgs?
Describe the bug
I added gnomeExtensions.tiling-shell to my nixconfig yesterday to my great enjoyment, but I'm repeatedly bumping into a bug that breaks rendering for certain windows. I have auto-tiling turned off, but I have suggestions turned on.
The broken windows fail to render, but if I mouse over where they 'should' be, I can see the focus outline appear. If I tap the super key, they still appear (live and running) in that selection view. If I double click the header bar area of the space a window should be, it 'maximizes', but is still not rendered - I can see from the super key view that it is maximized, though.
The issue seems to only occur with certain applications like Text Editor and Console, and whether it triggers seems to depend on what order I start tiling my windows in. I have a consistent repro recipe:
To Reproduce
Steps to reproduce the behavior:
If I mouse over my console windows and close them via keyboard, I can open new instances, tile them, and I'm good to go from there. The issue only occurs if I tile my browser first (and presumably other applications I haven't bumped into it with yet).
Screenshots
If a screen recording would be helpful, just let me know.
Information (please complete the following):
17.3(pulled by default via nixpkgs)50Additional context
This seems like maybe a GNOME 50 issue - claude's guess was it's a problem related to tile suggestions with v50, so I'm going to try turning those off and rebooting to see if it resolves the problem. But I like them so I'd like to keep them if I can :)
I saw the closed issue about 50 support being live, but I observed that the 17.3 branch does not include v50 in the manifest in resources/. Maybe there's an issue with what particular version is getting pulled in by nixpkgs?