https://bugs.kde.org/show_bug.cgi?id=514571
--- Comment #2 from Jason <[email protected]> --- Thank you Tracey While ultimately this would be best, there are really two issues here. ======== ISSUE 1 The first one is why does the stop script that works 100% under KDE-X11 have three different outcomes occurring randomly under KDE_wayland? This part of the issue must surely be a KDE problem. How the shutdown script behave differently under wayland only. To repeat myself 1a) killall -9 chrome (at the Konsole terminal) 1b) logout/shutdown Results in Chrome complaining on startup, but at least allowing a restore of previously open tabs 2a) logout/shutdown 2b) auto-execution of logout script which executes (1a) above followed by a sleep Results in 33% chance Chrome complaining on startup but allowing a restore, 33% chance Chrome complaining on startup but allowing a partial restore, 33% Chrome NOT complaining on startup but not allowing any restore Like I mentioned previously, bug 436318 would be the ideal fix, but in the meantime there is something "strange" happening with the auto-execution of logout scripts, but only under wayland ======== ISSUE 2 Resolvable by bug 436318 I am not saying this just a KDE issue, there is obviously something with Chrome misbehaving as well. But surely one of the main software packages not closing down properly is a serious enough issue that it is worth looking at? -- You are receiving this mail because: You are watching all bug changes.
