I have two monitors with different resolution (1680x1050 and 1280x1024). I usually use Dolphin on maximized on my secondary monitor. When I close Dolphin and open it again, it opens on the secondary monitor, not maximized but with the size of the primary one. Reproducible with Dolphin and Konsole. Kate opens maximized properly. Systemsettings never opens maximized but with the last size it had before maximizing. (So, is this application specific?) Reproducible: Always Steps to Reproduce: 1. Have the above screen configuration :) 2. Open Dolphin 3. Move Dolphin to the secondary monitor and maximize it 4. Close Dolphin 5. Open Dolphin again Actual Results: Dolphin opens on the secondary monitor, not maximized, with the size of the primary monitor Expected Results: Dolphin opens on the secondary monitor, (maximized), with the size of the secondary monitor.
The application reads the last size from its rc, according to the screensize of the screen where it assumes to show up (being the first since this hapens before its mapped/placed... i think the entire KMainWindow thing can only deal with changing screen sizes) and kwin places it on the active screen (screen with active window or where the mouse is - configurable) Overmore KMainWindow does not store the window state (maximized or not) but simply "screensize + 1,1 - the WM will hopefully be so kind to turn this into maximization" See bug #51571, bug #191072 and bug #150772 Things that need to happen for KF/5 a) KMainWindow needs to properly re/store former states - not abuse the size. That worked on static single screen setups 10 years ago. b) KMainWindow has to restore the former size _after_ being mapped by a maprequest (risking onscreen flicker) c) alternatively KMainWindow *might* re/store the previous screen (causing a bypass of the "active screen" selection) --------------- To workaround the issue, use a kwin rule. Make dolphin initially appear on screen 2 and have it maximized.
*** Bug 346396 has been marked as a duplicate of this bug. ***
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!