On 10/16/2015 05:01 PM, Wolfgang Bauer wrote:
No, I´m running 13.2 as well (Plasma 5.4.2, Frameworks 5.15, Qt 5.5.0), sorry for forgetting to mention that.
As the behavior is quite random, it may be a timing issue. So, any difference in the system timing (e.g. slower/faster hardware) can also change the behavior I suppose, that could range from totally breaking it or even make it more reliable, possibly.
What I can say so far (after some testing) is, that the problem is not in *restoring* the session. This seems to work reliably. But applications that are not restored, are not even written to ksmserverrc. Creating an entry manually there, makes that application start on login (reliably, AFAICT so far) Thanks for pointing me in the right direction. I just did some more testing, and found some encouraging results.
You're absolutely correct about the problem occurring at save-time rather than restore-time. The problem is not even with the session-saving code per se. It seems to be working fine in isolation. The problem only occurs when the session-saving code is called automatically at logout. It's either some kind of timing issue, as you suggested, or the session-saving code is conflicting with other processes running at logout-time. I've noticed frequent kdeinit5 seg faults at logout when sessions are set to autosave and one or more kf5 apps are open, but only when both these conditions are true. If I go to systemsettings5-->startup_and_shutdown-->desktop_settings and change the setting from "Restore Previous Session" to "Restore Manual Session.", and then remember to choose "Leave-->save_session" from the app launcher widget each time before I log out, all KF5 apps are restored perfectly, exactly where I left them, every time. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org