https://bugs.kde.org/show_bug.cgi?id=409919

--- Comment #5 from Yogesh Marwaha <yogeshm....@gmail.com> ---
I'll try to rephrase (or may be explain better) the problem being faced by OP
and me.

Prerequisite info:
-----------------
Operating System: Arch Linux 
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.59.0
Qt Version: 5.13.0
Kernel Version: 4.19.57-1-lts
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz
Memory: 14.6 GiB

Disclaimer:
----------
1. Assuming that the OP wants to restore the application window (from maximized
state) not minimize it; for me minimizing works fine.
2. This only seems to happen on KDE applications under wayland. Other non-KDE
applications I use seem to work fine (e.g. Firefox, Gnu Cash, FileZilla,
Chromium, Android Studio)

Steps to reproduce:
------------------
1. Maximize a KDE application (Ref. screenshot 1)
2. Close it
3. Reopen the application (Note: Now the application seems to be opened with a
size which would be if it was started maximized, but it does not actually start
maximized, as is evident from titlebar buttons' state) (Ref. screenshot 2)
4. Try to maximize window by clicking on relevant button in titlebar. Window is
resize in a weird way. (Ref. screenshot 3) If the window is resized (dragging
from edges) before maximizing, it is maximized properly.


Effects of behavior mentioned above:
-----------------------------------
1. Since the application window is started with a size of a maximized
application (while not actually maximized as per KWin), it cannot be restored
to a smaller size.
2. Since KWin thinks the window is not maximized, shown windows (i) have
borders around them and (ii) are shown with a titlebar even if showing
titlebars for maximized applications is disabled.

Possible cause of problem:
-------------------------
Application indeed opens its window in maximized position but either KWin does
not get the message or it forgets later that the window is maximized.


I hope I'm clear enough. 

Regards.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to