https://bugs.kde.org/show_bug.cgi?id=15329
--- Comment #216 from Bob English <[email protected]> --- (In reply to rlk from comment #213) > Firefox works just fine; Chromium does not; only one of the windows I have > open at shutdown actually reopens (unclear whether there's a pattern to > which one opens). A *possible* workaround is a shutdown script in > $HOME/.config/plasma-workspace/shutdown/chrome-shutdown.sh (note that kill > -HUP does not, but this may work, possibly because the first window to come > up prompts for restoring previous windows). Note that the key is to kill > chromium without any saving throw; kill -HUP results in chromium shutting > down cleanly, causing the problem. > > #!/bin/bash > > # Deliberately kill all chromium processes hard which paradoxically > # allows for a clean recovery on startup. > /usr/bin/killall -9 chrome chromium > > # Synchronously loop for up to 4 seconds while Wayland is 100% active > start=$(date +%s) > while pgrep -x chrome >/dev/null && (( $(date +%s) - start < 4 )) ; do > usleep 100000 > done This in contect to above quoted but to all for clarity If I can add some: I don't use chromium, and this thread isn't about any of that! Windows I leave open, mostly reopen on reboot, but this is about closing windows. and then when opening them again at any time many like myself want them to open in the very same place on the screen they were when we closed them: The title of this report gives it away. This is an old thread, it was fixed, and it worked great in Plasma 5, but no longer in 6, and so the thread was picked up again, so now it's about KDE 6 with Wayland. Individual programs outside of KDE Plasma with Wayland should be just as effected as all programs because they don't control this! This is related to making the newer Plasma infrastructure to do it, which has been said more than enough is rather difficult and sort of unknown or something the developers are already aware of and figuring out: It will need time to find the reason or a way to make it work, implementing it will most likely go quick. If those familiar with and looking into the code are having a hard time, then no amount of comparing it to other things elsewhere in Linux, X11 and what not, will not and cannot help, but if you think you can do better, then maybe look at the code yourself! BTW the ones who maintain X11 make Wayland too! So maybe for those dissing KDE and Wayland because X11 is superb... go there and lay it on them, and let the developers here fix stuff, instead of having to keep this report in line, and it will happen faster and come to fruition. Sorry if off topic, but to me discipline here is a big part of the fix! -- You are receiving this mail because: You are watching all bug changes.
