Bug 447731 - System settings and infocenter do not properly tile left/right on Wayland
Summary: System settings and infocenter do not properly tile left/right on Wayland
Status: RESOLVED DUPLICATE of bug 434615
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: 5.23.4
Platform: Fedora RPMs Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2021-12-31 10:10 UTC by Stephan Oostveen
Modified: 2022-05-23 18:27 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot displaying the behavior (609.72 KB, image/png)
2021-12-31 10:10 UTC, Stephan Oostveen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Oostveen 2021-12-31 10:10:38 UTC
Created attachment 144986 [details]
Screenshot displaying the behavior

SUMMARY
When tiling the System Settings left the application uses more than 50% of the screen, thus overlapping with a different application tiled to the right side of the screen. When inverted, System Settings being tiled right, it runs of the side of the screen. The same can be observed with the Info Center application

STEPS TO REPRODUCE
1. Open a random application (e.g Firefox) and tile it to the right (using Meta+Right arrow)
2. Open System settings and tile it to the left (using Meta+Left arrow)

OBSERVED RESULT
System Settings overlaps the application tiled on the right side of the screen

EXPECTED RESULT
System Settings resizes to use 50% of the screen instead of overlapping.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 35 KDE Plasma Desktop
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
See the screenshot for a visual hint of what is happening
Comment 1 Nate Graham 2022-01-12 01:26:16 UTC
Can confirm on Wayland; works on X11.
Comment 2 Nate Graham 2022-05-23 17:26:24 UTC
*** Bug 454127 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2022-05-23 17:26:51 UTC
Very likely caused by Bug 395476.
Comment 4 Till Schäfer 2022-05-23 18:27:27 UTC

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