KWrite window opens in background when opening files from Dolphin. STEPS TO REPRODUCE 1. Select some text file(s) in Dolphin and choose Open with KWrite in the context menu OBSERVED RESULT KWrite opens, but the window is behind Dolphin. This is a regression. It didn't happen in 24.08. Note: Sometimes KWrite opens in the foreground. I didn't find a pattern, but the very first KWrite opened from Dolphin after login always opens in the background. Note 2 (just for completeness; I don't see how this could possibly related to the bug): A few KWrite instances are opened/restored via session management. They are restored minimized. EXPECTED RESULT KWrite opens and the new window is shown in front of Dolphin (and other windows). SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1
In case it matters: I'm still using X11.
Pattern: If kwrite was minimized while closing (doesn't matter if reboot or right click on the task bar and close) Then kwrite starts in minimized (don't think its starts in the background, just minimized) If kwrite was **not** minimized while closing (doesn't matter if reboot or right click on the task bar and close) Then kwrite **does not** start minimized (don't think its starts in the background, just minimized) **This is X11 only** tested against Tumblweed and Arch Not sure if this is regression. Can you downgrade kwrite to 24.08 and check if this doesn't happen?
I cannot downgrade to 24.08 without much hassle, but I never saw this with 24.08 (or any other older version) and I'm doing exactly the same as I've always been doing so that I surely would have noticed this problem in 24.08.
Just so I do not misunderstand: Does you kwrite start minimized or just in the background?
It does indeed start minimized. Probably because I have a few minimized KWrite instances that are saved and restored by session management.
This SEEMS like intended behavior. The window state (minimized, maximized, ..) gets saved to ~/.local/share/kwrite/anonymous.katesession Eg.: WindowState=1 when kwrite gets closed. Same for Kate. What I don't know if this SHOULD be the the intended behavior, therefore I let the kwrite/Kate maintainers confirm or close this bug.
Maybe because of https://invent.kde.org/frameworks/kxmlgui/-/merge_requests/239 Windows state restoration was broken for quite sometime
I very much doubt that it is intended behavior that a *new* instance of kwrite started by direct user interaction is started minimized. Only kwrite instances that are restored by session management should be started minimized if they were minimized when the last session was saved.
Yes, that is not the intended behavior.
A possibly relevant merge request was started @ https://invent.kde.org/utilities/kate/-/merge_requests/1697
Could one try https://invent.kde.org/utilities/kate/-/merge_requests/1697