SUMMARY -> See title STEPS TO REPRODUCE 1. Use Wayland (not sure whether this is a requirement) 2. Open Dolphin (for example) 3. Maximize Dolphin 4. Close Dolphin 5. Open Dolphin again OBSERVED RESULT Dolphin opens up as a small window. EXPECTED RESULT Dolphin opens up maximized. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.8.14-1-MANJARO OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 ADDITIONAL INFORMATION Apps I have seen with this problem: - Dolphin - Gwenview (opened from dolphin) Apps that don't seem to have this problem: - Systemsettings - Firefox - GIMP I have a multi-monitor setup, that might possibly be related. The product I filed this for might also be wrong.
I already saw ths bug on neon unstsble when I used a third party window decoration.
Should be fixed in 5.20.1
Nice, thanks!
*** This bug has been marked as a duplicate of bug 409919 ***
(In reply to Nate Graham from comment #4) > > *** This bug has been marked as a duplicate of bug 409919 *** This is most likely not a duplicate of that bug. This is about an application that was closed not open maximized again. The other one is about a maximized application still opening maximized again after closing, but when then restoring the original size the size is not the previous non-maximized size, but similarly to the maximized size. That is at least what the description from bug 409919 says. Please review!
Reading that bug again you were probably right with the duplicate. The original description just sounds different, but after having a closer look that behavior was probably what he meant, so everything fine.
(In reply to Claudius Ellsel from comment #5) > a maximized application still opening maximized again > after closing, but when then restoring the original size the size is not the > previous non-maximized size, but similarly to the maximized size. I have reported this issue as bug 427124
Interesting and thanks for the link. So there is actually such an issue as described in that bug's description. Maybe it just got "hijacked" and repurposed, then (we will probably never know :)).
Reopening to further track the remaining problems discovered in the discussions started in https://bugs.kde.org/show_bug.cgi?id=409919. Might then be a duplicate of https://bugs.kde.org/show_bug.cgi?id=427875, though.
Marking as duplicate, as I am rather confident they are the same. The symptoms are the same at least. *** This bug has been marked as a duplicate of bug 427875 ***
Removing the referenced commit and version fixed in, as that commit seems to fix a different problem, if I understand it correctly.