Bug 476474 - New "tiling" functionality breaks 50/50 window division on desktop, nor can it be turned off.
Summary: New "tiling" functionality breaks 50/50 window division on desktop, nor can i...
Status: RESOLVED DUPLICATE of bug 465937
Alias: None
Product: kwin
Classification: Plasma
Component: Quick Tiling (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-02 15:48 UTC by Kryštof Jelínek
Modified: 2023-11-03 21:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kryštof Jelínek 2023-11-02 15:48:23 UTC
SUMMARY
***
New "tiling" functionality breaks 50/50 window division, nor can it be turned off.
***

Before a system update, I used to be able to fit windows 50/50 on desktop just by dragging them to the left and right or top and bottom edges of the screen, now, the windows strangely do not fit half of the screen, but variable amounts which are determined by some setting which I do not know.


Somehow, I have gotten to determining that this awkward filling is caused by the "tiling" functionality and it can't be turned off, supposedly because of these lines of code: https://invent.kde.org/plasma/kwin/-/blob/b7a94a536e59a21fedecb2c6ca7cc99e3fec4e68/src/window.cpp#L1896-1899

It is really uncomfortable for me to work like this, for me, windows can't be organized anyhow as of right now, which is why I am filing this report.


SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.5.6-1-default (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 7773
Comment 1 Nate Graham 2023-11-03 21:21:41 UTC

*** This bug has been marked as a duplicate of bug 465937 ***