SUMMARY KDE application like dolphin, discover and konsole have a really strange behavior in plasma-wayland. But, it doesn't happen with other app like firefox and chromium. STEPS TO REPRODUCE 1. Maximize a KDE application 2. Close the application 3. Reopen the application 4. Minimize the application OBSERVED RESULT The minimized application have the size of the maximized application. EXPECTED RESULT The minimized application have the size of the initial minimized application. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60 Qt Version: 5.12.3 ADDITIONAL INFORMATION
Restoring the size is the task of the applications.
Created attachment 121636 [details] Screenshot 1
Created attachment 121637 [details] Screenshot 2
Created attachment 121638 [details] Screenshot 3
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.
Well, as I said: restoring size (including maximized state) is task of the applications.
All right then. Since this bug affects multiple KDE applications (tested on dolphin, konsole, ksysguard, system settings, many KDE games) and needs to be worked on each one of them separately, does this bug needs to be reported separately for all those applications? If the answer is no, can you guide how can this be done.
Thanks Yogesh Marwaha, that what I wanted to say. It's not minimizing, it's restoring to the non-fullscreen size.
I assume the problem lies in a library. Either Qt or a KDE Framework. Unfortunately I do not know which part is responsible here. So I would suggest to report against an application so that they can investigate.
I have filed a report against dolphin (https://bugs.kde.org/show_bug.cgi?id=410061). Can you have a look at screenshot 3 and confirm whether incorrect drawing along the right edge and bottom edge of the window is a fault of KWin or not? Judging from the mouse actions on that area, it is still part of the application window.
> Well, as I said: restoring size (including maximized state) is task of the > applications. On X11, KWin currently takes care of maximizing windows that were maximized when they were closed (IIRC it compares the window size to the screen size and maximizes the window if they're equal). It should have the same behavior on Wayland.
Actually no. KWin only performs a sanity check for windows requesting a size larger than the screen. This isn't meant for restore of windows, but for screen layout changes. Such a sanity check is useful, but shouldn't replace a correct implementation in the applications.
*** Bug 410061 has been marked as a duplicate of this bug. ***
Yeah, if non-KDE apps remember their maximization state correctly, I guess you're right. Moving to frameworks-kxmlgui for initial triage.
I tried to look for the problem and it looks like kxmlgui (or any part of KDE) is not to be blamed here. Following are the few observations (while on plasma-wayland session): - #1: Applications correctly save window size/maximized state on close, but they somehow cannot restore maximized window state #2: Vanilla Qt5 applications also fail to set maximized window state on open #3: For example, with 'qdbusviewer --platform xcb', window is maximized on open with 'qdbusviewer --platform wayland', window is not maximized on open (but still has proportions of maximized window) So, either Qt(wayland) is not setting the window state properly or there is a communication gap between KWin and Qt5 (wayland) clients. I've tried to look into the qtwayland source, but that's probably too much for me. Thanks for your time.
This also happens on WayFire. KDE apps don't remember remember size but other apps like qBitorrent and thunar do. Also konsole don't follow initial terminal size on WayFire. it always opens with 138x18 regardless of initial terminal size setting.
Just updated my (Arch Linux) installation and the bug has disappeared (at least for all the KDE/non-KDE apps I use). A big thumbs-up for everyone involved! Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.4.45-1-lts OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530
Yep, this was fixed in 5.19!
Scratch that. It's only working for XWayland apps. Full Wayland apps are still broken in the way described here.
It seems to work for KDE apps(In reply to Nate Graham from comment #19) > Scratch that. It's only working for XWayland apps. Full Wayland apps are > still broken in the way described here. Is xeyes method valid to check whether an app is wayland native? If not, how can one verify that? PS: xeyes doesn't move on KDE apps and firefox (under wayland)
Fixed by Vlad Zahorodnii with https://invent.kde.org/plasma/kwin/-/commit/a195223a8d581e0d6d36374771c939414c7c036d in Plasma 5.20.1!
possibly dupes: bug 427808 and bug 409516
*** Bug 427808 has been marked as a duplicate of this bug. ***
*** Bug 409516 has been marked as a duplicate of this bug. ***
*** Bug 419471 has been marked as a duplicate of this bug. ***
I tested yesterday on Manjaro unstable with 5.20.1 and it didn't seem to work for me (tested with Dolphin). Maybe not all required packages were available then, though, so leaving this bug at the current state for now.
It didn't work with Dolphin (Konsole too) for me also. Since other applications (which I use) seem to work fine, I tried some tricks. I manually resized application window and then closed it. Again started, maximised and closed. Afterwards it functioned as intended. PS: A bit unrelated, Firefox with custom title bar cannot determine that it's maximised.
(In reply to Yogesh Marwaha from comment #27) > It didn't work with Dolphin (Konsole too) for me also. Since other > applications (which I use) seem to work fine, I tried some tricks. I > manually resized application window and then closed it. Again started, > maximised and closed. Afterwards it functioned as intended. Ah, thanks for the hint. Sounds like old configs have to be overwritten to get it working properly. I assume deleting the dolphinrc file from the .config folder has a similar effect.
Neither resizing dolphin nor deleting dolphinrc helped. Maybe that has something to do with me running a multi-screen setup and is not really related to this?
(In reply to Claudius Ellsel from comment #29) > Neither resizing dolphin nor deleting dolphinrc helped. Maybe that has > something to do with me running a multi-screen setup and is not really > related to this? On my dual-monitor setup, dolphin preserves the maximized state across application launches.
Created attachment 132637 [details] Screenshot of the problem This is how my setup looks like (with dolphin opened after being closed maximized). [clel@claudius-pc ~]$ kwin_wayland -v kwin 5.20.1
Created attachment 132639 [details] wayland debug output of dolphin with Claudius Ellsel's screen layout If I arrange my screens similar to Claudius' setup, this issue surfaces. The most interesting thing is that dolphin doesn't issue any set_maximized() request.
Created attachment 132640 [details] with my screen layout, dolphin sends set_maximized() requests
So yeah, dolphin restores its maximized state based on the screen layout. Weird.
Shell we track this in a different bug report? In the meantime while testing other stuff, now Dolphin seems to remember the maximized state, but opens always on the left screen, similar to https://bugs.kde.org/show_bug.cgi?id=427875. The testing had me build and run Dolphin from master, so that might have changed stuff in the config files, maybe?
(In reply to Vlad Zahorodnii from comment #34) > So yeah, dolphin restores its maximized state based on the screen layout. > Weird. Yes, that was a recent intentional change. See https://invent.kde.org/frameworks/kconfig/-/merge_requests/17
(In reply to Nate Graham from comment #36) > Yes, that was a recent intentional change. See > https://invent.kde.org/frameworks/kconfig/-/merge_requests/17 Not sure whether that introduced it, but the current behavior seems to be buggy for me.
I suggest to report any issues that you are still noticing as a separate ticket.
(In reply to Christoph Feck from comment #38) > I suggest to report any issues that you are still noticing as a separate > ticket. Sure. We can use https://bugs.kde.org/show_bug.cgi?id=427808 for that (I will undupe it) and also there is https://bugs.kde.org/show_bug.cgi?id=427875.