Konsole always saves their own session file into ~/.config/session/konsole_* even when doesn't get saved by ksmserver. Those konsole_* files stays there forever.

Easily reproducible on a clean Fedora 22 install in KVM.

I try to dig deeper but it's not an easy topic for a newbie on KDE like me.

It's not konsole-specific: kwite also affected.

Seems like app window closes before ksmserver could store the session. I hooked a breakpoint on "QGuiApplicationPrivate::saveState()" in Konsole and found that all windows are already gone when it stops on this breakpoint. This is not normal.

Those who rely heavily on Konsole and session management (like me), there is a simple workaround on Fedora 22: use Konsole 4.x - seems like only KF5/Qt5 applications are affected.

# dnf remove konsole5; dnf install konsole

Could it be related to this: Bug 346768 ?

I have the issue too :
 - files accumulate in ~/.config/session (I can see the last ksonsole/kate sessions)
 - ~/.config/ksmserverrc doesn't list all applications (I see kwin_x11, kmix, firewall_applet, sometimes pulseaudio)

Manually saving the session works.

I also show this behavior.  With 3 konsole windows on two desktops, and a konqueror session on the third, only the konqueror session is restored upon login.  Manually saving the session does not work perfectly for me -- the exact opposite occurs: the konsole windows are all restored, but the konqueror session does not appear.

I have following behavior:
-Auto-save session everything except KF5 Konsole is restored
-Tried save manually session and this works as expected

Btw i am using kwin with the fix from this bug report https://bugs.kde.org/show_bug.cgi?id=341930

The only thing not working properly is discarding the last session files for kwin the others are deleted as they should be.
The "discardCommand" entry in ksmserverrc is missing for kwin completely. (also the counting is strange "discardCommand3, discardCommand5,discardCommand6,discardCommand7" where did 1,2 and 4 go?^^)

I confirm this for Debian, both Testing and Unstable, and has been like this for a while. Most or all other programs are restored properly.

Version 15.08.0
Using:
KDE Frameworks 5.15.0
Qt 5.5.1 (built against 5.4.2)
The xcb windowing system

Probably an instance of bug 354724
After I hacked konsole to not quit on session saving, it didn't restore properly on restore... that seems to be a separate bug.
On my computers the bug happens every time, but it is timing dependent so may trigger randomly for others. If konsole dies before kmserver saves the list of applications to restore, konsole will not be restored. If it dies later, it will be restored.

Hmm, I already use Plasma 5.6.1 as date of 29/03/2016. The above BUG is still given for KDE/Plasma specific applicatitions like Konsole, KWrite, Settings and so on.
To relogin to a saved session (last session) was a fine thing in KDE 4.x, because it worked.
Is there any try, any work to solve this bug in close future.
I would be glad about.
Thank you...

(In reply to linuxfluesterer from comment #11)
> Hmm, I already use Plasma 5.6.1 as date of 29/03/2016. The above BUG is
> still given for KDE/Plasma specific applicatitions like Konsole, KWrite,
> Settings and so on.
> To relogin to a saved session (last session) was a fine thing in KDE 4.x,
> because it worked.
> Is there any try, any work to solve this bug in close future.
> I would be glad about.
> Thank you...

Your KDE stack needs to be compiled against Qt 5.6 to fix this. This is hard to change without compiling KDE yourself. Even installing Qt 5.6 won't help.

(In reply to Andreas Hartmetz from comment #12)
> (In reply to linuxfluesterer from comment #11)
> > Hmm, I already use Plasma 5.6.1 as date of 29/03/2016. The above BUG is
> > still given for KDE/Plasma specific applicatitions like Konsole, KWrite,
> > Settings and so on.
> > To relogin to a saved session (last session) was a fine thing in KDE 4.x,
> > because it worked.
> > Is there any try, any work to solve this bug in close future.
> > I would be glad about.
> > Thank you...
> 
> Your KDE stack needs to be compiled against Qt 5.6 to fix this. This is hard
> to change without compiling KDE yourself. Even installing Qt 5.6 won't help.

So then... is there any plan, any schedule to compile KDE by the developers?
If not, could I compile complete KDE packages (Plasma 5.6 Meta packages maybe) by using Gentoo and the 'emerge' command?
I'm a Sabayon user. Sabayon is a rolling release and offers precompiled binaries.
Thank you.

(In reply to linuxfluesterer from comment #13)
> (In reply to Andreas Hartmetz from comment #12)
> > (In reply to linuxfluesterer from comment #11)
> > > Hmm, I already use Plasma 5.6.1 as date of 29/03/2016. The above BUG is
> > > still given for KDE/Plasma specific applicatitions like Konsole, KWrite,
> > > Settings and so on.
> > > To relogin to a saved session (last session) was a fine thing in KDE 4.x,
> > > because it worked.
> > > Is there any try, any work to solve this bug in close future.
> > > I would be glad about.
> > > Thank you...
> > 
> > Your KDE stack needs to be compiled against Qt 5.6 to fix this. This is hard
> > to change without compiling KDE yourself. Even installing Qt 5.6 won't help.
> 
> So then... is there any plan, any schedule to compile KDE by the developers?
> If not, could I compile complete KDE packages (Plasma 5.6 Meta packages
> maybe) by using Gentoo and the 'emerge' command?
> I'm a Sabayon user. Sabayon is a rolling release and offers precompiled
> binaries.
> Thank you.

We don't ship compiled packages, distributions do. They could also backport the necessary changes in Qt and remove the Qt version check in KDE.
If you use Gentoo, sure, you can compile your own and get those changes. But I do not know whether they are already in (your) stable versions of Frameworks 5 and Plasma and applications (where necessary). I haven't done much else for KDE recently, so if you see my name in the commit logs of kdelibs4support, kxmlgui and plasma-workspace in those versions, you have recent enough versions. The commit message should be about "fallback session management".

I'm skeptical of the claim that a full rebuild is required, are you suggesting that qt-5.6.x introduced some abi change wrt session-management?  If so, what evidence do you have for that claim?

(In reply to Rex Dieter from comment #15)
> I'm skeptical of the claim that a full rebuild is required, are you
> suggesting that qt-5.6.x introduced some abi change wrt session-management? 
> If so, what evidence do you have for that claim?

5.6.0 introduced new API that is unfortunately required to fix the bug. That's of course also an ABI change. Evidence: commit e7bf0edfd49de9a4d8285fbe8d878f8fda910e6d in qtbase.

So it's at least an API change, but not necessarily an ABI change

Do you know which kf5/plasma components use this new API?  (only those would need rebuilding, not the entire stack)

Found these so far:

https://quickgit.kde.org/?p=kwrited.git&a=commit&h=e2bb0d7595c0898e8351bbcb721ad7173423f8f5

https://quickgit.kde.org/?p=plasma-workspace.git&a=commitdiff&h=b5e814a7b2867914327c889794b1088027aaafd6

I meant ABI change in the sense that if something is compiled against the new API, it won't run against an older version.
Applications that use KMainWindow (from kxmlgui framework) or KApplication (from kdelibs4support framework) are fixed automatically. Others all need to be fixed separately ("disable fallback session management").

OK, that's not the classic definition (at least what I meant) of ABI change/break.  ABI break, to me, means a new build is no longer backward compatible.

For the record: it is fixed in Fedora 24. Thank you!