Bug 454827 - Minimum window size rule is ignored for applications with a programmed minimum size on wayland
Summary: Minimum window size rule is ignored for applications with a programmed minimu...
Status: CONFIRMED
Alias: None
Product: kwin
Classification: Plasma
Component: rules (show other bugs)
Version: 5.24.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2022-06-04 11:04 UTC by Fabio Lenherr
Modified: 2022-06-06 19:21 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Bug displayed with systemsettings (227.79 KB, image/png)
2022-06-04 11:04 UTC, Fabio Lenherr
Details
example how it should work (267.19 KB, image/png)
2022-06-04 11:05 UTC, Fabio Lenherr
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Fabio Lenherr 2022-06-04 11:04:40 UTC
Created attachment 149446 [details]
Bug displayed with systemsettings

SUMMARY
***
On Wayland, plasma ignores the minimum window size rule. 
In other words, manually redefining the minimum size is not possible, or rather it doesn't work.
On X11 it works as intended.

example attached.

***


STEPS TO REPRODUCE
1. Start plasma with wayland
2. set a minimum window size rule for systemsettings -> example 0 width 0 height
(systemsettings used as example, works for every application with a fixed minimum size.)
3. try to resize smaller to than the default minimum size

OBSERVED RESULT

Window doesn't resize smaller than the default minimum size

EXPECTED RESULT

Window resizes to set minimum size via rule.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch / KDE
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Comment 1 Fabio Lenherr 2022-06-04 11:05:31 UTC
Created attachment 149447 [details]
example how it should work
Comment 2 Paul Worrall 2022-06-05 08:58:03 UTC
Confirming.  Note that minimum window size works OK on Wayland for applications with no pre-programmed minimum size.
Comment 3 Nate Graham 2022-06-06 19:21:59 UTC
Probably Bug 434615 has the same root cause.