https://bugs.kde.org/show_bug.cgi?id=486919
--- Comment #6 from Friedrich W. H. Kossebau <kosse...@kde.org> --- Not yet got to research the issue (as myself still not on Wayland). From what I have heard elsewhere there might be two different issues when it comes to wayland: * Qt does not properly save & restore the state of QDockWidgets there, even more broken on Qt5 * Wayland window managers might not be too cooperative when a windows tries to restore/set the window size by itself (?) Okteta code itself tries to rely on the abstraction API Qt & KF libraries provide over X11, Wayland (and other windowing systems/platforms). So Okteta should not do anything wrong here, also might only try to work-around things where possible (ideally avoided though and issues fixed with the actual culprits). Someone trying to investigate this bug(s) might try with doing a simple dummy app with some QDockWidgets to reproduce the issues and perhaps find some work-around. Because at least with Qt5 any Qt-side fixes might not be something to expect to arrive soonish now to FLOSS users. Situation is really unfortunate, I am sorry for your experiences. My rough plans hopefully will have me get to complete the current blocker porting-from-QtScript in autumn and then move Okteta finally to Qt6, perhaps even get rid of using QDockWidget (some local sketch exists). For now, until I get to research things, can you help with some information: what happens with the QDockWidgets/tool views on reopening? I.e. * are those you closed shown again? * are they in the same location (left/right/stacked) -- You are receiving this mail because: You are watching all bug changes.
