[Bug]: Toggling full screen window in master stack layout pushes a window out of master
pjhfggij opened this issue · comments
Before you make the issue, confirm that
- You are running the master build from GitHub actions
- You have read the FAQ and the usage instructions
- You have searched pull requests and issues and have found none similar to your issue
- This problem comes from a failure in the tiling system and not a missing feature
Describe the bug
Fullscreening a window (e.g. a youtube video) and toggling it back pushes it out of master tile.
To reproduce
Put a browser in master window.
Fullscreen a video.
toggle it back.
browser is now in a stack and another window is the master tile. if there is only two windows they get tiled horizontally if they were previously vertical.
Expected behavior
window comes back to it's location (master)
Relevant log output
-Screenshots and videos
No response
Additional context
No response
Try v1.0 and see if the issue persists.
Thanks, that didn't work sadly, also it completely destroyed the system - I've had to revert it back to a previous btrfs snapshot to restore it - even after reinstalling v0.6 and rebooting the system was still in a broken state - windows were flickering, tiling switched from master stack to something else, a lot of "solitaire"/"ghosting" like effect with windows still showing even after they were minimized/moved. Also plasma bar turned into a grey blur - no buttons/widgets were rendered. I took some screenshots before btrfs rollback, but... I've just deleted that snapshot. Sorry, brain in food coma...
I use displaylink, so maybe that's part of the problem.
That's very strange. You might have installed the wrong version of the script, such as installing the Plasma 6 script on Plasma 5. How did you install v1.0?
I've downloaded it from the github pre-release from 2 days ago - pretty sure it was polonium-plasma5.kwinscript for kde5 which im running
Now that KDE6 was pushed into Arch and after a few difficult days when a lot of issues came up at once I can confirm that v1.0 is working - the previous issue still occurs on X11, but Wayland is fine now.
Strange, but good I guess