Skip to content
This repository has been archived by the owner on Jun 16, 2024. It is now read-only.

[Bug]: Windows continously stop tiling until toggled in settings #499

Open
ItMeCorban opened this issue Jan 16, 2024 · 8 comments
Open

[Bug]: Windows continously stop tiling until toggled in settings #499

ItMeCorban opened this issue Jan 16, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@ItMeCorban
Copy link

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

@ItMeCorban ItMeCorban added the bug Something isn't working label Jan 16, 2024
@medkira
Copy link

medkira commented Feb 2, 2024

i am facing the same problem

@GrahamJenkins
Copy link

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.
When it worked window borders are/were disabled, but for new windows the title bar is displayed and they refuse to tile.

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.
@medkira @ItMeCorban

@Berny23
Copy link

Berny23 commented Feb 23, 2024

But I don't want to give up tiling, so I wrote a script to automate it.

Thanks, I'm using it with a keyboard shortcut instead of automating it.

@GrahamJenkins
Copy link

@Berny23 Yeah, that's a better option. I realized that restarting it messes with the sizes, and have removed automation.

@medkira
Copy link

medkira commented Mar 21, 2024

@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.
btw: the creator of bismuth stopped working on the package so its officially dead.

@GrahamJenkins
Copy link

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
(TODO)

@Berny23
Copy link

Berny23 commented Apr 30, 2024

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.

@ItMeCorban
Copy link
Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants