-
-
Notifications
You must be signed in to change notification settings - Fork 93
[Bug]: Windows continously stop tiling until toggled in settings #499
Comments
i am facing the same problem |
I'm encountering the same issue with Konsole, I saw another comment that suggested it may be related to QT applications or something like that. The strange thing is that it was working previously, now something changed and it isn't. Edit: I got tired of opening settings to disable, apply, re-enable, apply. But I don't want to give up tiling, so I wrote a script to automate it. I use crontab to spam it every minute. I'll update if it seems to cause any adverse behavior. |
Thanks, I'm using it with a keyboard shortcut instead of automating it. |
@Berny23 Yeah, that's a better option. I realized that restarting it messes with the sizes, and have removed automation. |
@GrahamJenkins bismuth is dead In my machine don't know why it just stopped working after upgrade my debian, anyway I didn't have time to mess with the package 🙃 so I swapped to polonium. |
Hmm, I haven't heard of Polonium yet, I'll have to take a look. A quick search provides: https://zeroxoneafour.github.io/polonium/usage.html |
Polonium is now ready for everyday use. With the latest KDE Plasma 6 version on Arch and the current v1 script release, no crashes have happened anymore. |
This has been my experience recently too |
Summary
Windows will randomly decide not to tile anymore until bismuth is toggled off and on again. Like they've been set to floating, but toggling them to float doesn't change anything.
Steps to Reproduce
Happens most often with dolphin/kate but frequently happens with firefox as well. I'm using the mouse to move windows, untile by dragging is turned off.
Expected behavior
Windows should always tile unless set to floating. Windows that aren't tiled should return to being tiled when floating is toggled
Screenshots
No response
Bismuth version
3.1.4-1
KDE Plasma version
5.27.10
The platform KWin is running on
Wayland
Additional context
No response
The text was updated successfully, but these errors were encountered: