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

[Bug]: Logging back in after enabling tiling sets all windows as "always on top". #386

Open
Superfly-Johnson opened this issue Jun 28, 2022 · 2 comments
Open

[Bug]: Logging back in after enabling tiling sets all windows as "always on top". #386

Superfly-Johnson opened this issue Jun 28, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@Superfly-Johnson
Copy link

Summary

Logging onto a KDE workspace where tiling is enabled sets all windows as always on top, while simply enabling Tiling doesn't.

Steps to Reproduce

  1. Disable tiling
  2. Create two workspaces
  3. Disable tiling on one of the two workspaces.
  4. Open a few windows with tiling currently disabled on a blank KDE desktop.
  5. Enable tiling
  6. See windows settings; they should be as normal.
  7. Log out.
  8. Log in.
  9. Open more windows. They will now be set as always on top

Expected behavior

Windows are expected not to be set as always on top with tiling enabled.

Screenshots

No response

Bismuth version

3.1.1

KDE Plasma version

5.24.5

The platform KWin is running on

X11

Additional context

This was tested on Manjaro (Arch Linux) with bismuth built from the community package on the AUR.
@Superfly-Johnson Superfly-Johnson added the bug Something isn't working label Jun 28, 2022
@SonicZentropy
Copy link

Don't have a ton to add, but I'm experiencing this too, and it's "new" in some sense. I don't remember having the problem prior to updating. Several of my windows also end up being permanently-stuck on "always on top" until reboot.

@marccollin
Copy link

marccollin commented Aug 24, 2022 •
edited
Loading

get this issue if i do a suspend to ram
i have a dual display setup and seem to happen only to my secondary screen

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

No branches or pull requests
3 participants
@marccollin @SonicZentropy @Superfly-Johnson