Created attachment 746127 [details] emerge --info =kde-apps/konsole-21.08.2 I use sddm to log in and out and to reboot. I have three Konsole windows open on one desktop, and it used to be that, when I logged out, they would all close cleanly and then reappear when I next logged in, and in the same directories as before. Now, they don't shut down when sddm (I assume it is) tells them to. Their window contents reappear after a few seconds, for a second or so, before disappearing. The windows themselves don't appear; just their contents. On logging-in again, Konsole is absent from all desktops. My impression, from watching the logout process, is that Konsole is not shutting itself down neatly, or at all, and eventually it just has the ground wrenched out from under it.
I can confirm this. Konsole isn't restoring after re-login. Downgrading konsole doesn't fixed this for me.
The impression I referred to is supported by the fact that the latest bash history is not being appended to ~/.bash_history at Konsole termination.
Did you switch to using Wayland sessions?
(In reply to Andreas Sturmlechner from comment #3) > Did you switch to using Wayland sessions? Nope. Just a straightforward Gentoo ~amd64 system here. Oh, except that I use bootctl from systemd-boot, not Grub. I think that's the only thing you might say is out of the ordinary.
(In reply to Johannes Hirte from comment #1) > Downgrading konsole doesn't fixed this for me. What versions did you test...?
I have so far not been able to reproduce your observations with konsole-21.04.3/KDE Frameworks 5.85 or 21.08.3/Future KDE Frameworks.
I still see this behavior with konsole-21.08.3/KDE Frameworks 5.87.0 All applications/windows but konsole are restored at login. I'll try with a new created user, in case some user specific config is causing this.
Could the problem be in sddm not issuing the shutdown signal properly? I'm on sddm-0.18.1-r5. I use it to log in and out.
Must be somehting user-specific. I wasn't able to reproduce this with a new user.
(In reply to Johannes Hirte from comment #9) > Must be somehting user-specific. I wasn't able to reproduce this with a new > user. Seeing that, I created a new user, and the effect did not appear. Then I ran System Settings to set preferences to suit me and the effect reappeared. That's all I did. So the problem does evidently lie in an internal Plasma conflict of some sort. Is there a file I can send to show what user settings I set, or do I have to list them myself?
You probably could but that is out of scope for a downstream bug. Please narrow down the settings you change as much as possible, then file a report at bugs.kde.org.
Roger. Wilco.
I'm also seeing this, but even more weirdly, some konsoles (the ones I've had open for months and prior to this weird behaviour showing up) seem to restore just fine. However, the windows that I've opened recently seem to "get stuck while logging out" and those same konsoles are MIA when I log back in. Any chance you narrowed down a specific setting to twiddle?
(In reply to David Flogeras from comment #13) > Any chance you narrowed down a specific setting to twiddle? Not quite, yet. I've been running detailed tests by creating new users and tweaking one thing at a time, logging out and in at each step. Strangely enough, Firefox now seems to be involved, because I finished setting up a new user yesterday, with no problems showing, and then I went to Firefox to set that up too and the fault appeared again. Maybe one of my three Firefox add-ons is writing where it shouldn't: Bit Warden, Ublock Origin and Startpage. Still more testing to do...
(In reply to peter@prh.myzen.co.uk from comment #14) > set that up too and the fault appeared again. Maybe one of my three Firefox > add-ons is writing where it shouldn't: Bit Warden, Ublock Origin and > Startpage. Well that's really bizarre, but I too use Ublock origin, so maybe shine the light on that one? I don't know how many times in my life I've said "well that can't possibly be the problem" then been proven wrong :)
It isn't Firefox after all. I really don't know what's going on; I've run many tests and they come back with contradictory results. Sometimes the same test run twice gives different results. I can't go any further with this. The problem is still present after a bare-metal recompilation and installation of everything on the system. Looks like I'll just have to wait until some other development exposes the real cause.
I filed https://bugs.kde.org/show_bug.cgi?id=445862, but cannot seem to add it to this bug properly.
Curiouser and curiouser. I've just finished setting up a new user for myself, for the umpteenth time, and towards the end of the process I started getting "There have been repeated failed attempts to access KWallet. An application may be misbehaving" whenever I log out of the desktop. (I may have misspelt KWallet.) This began while I was setting up the System Settings to suit me, and now it happens every time I log out. I'm getting a bit thin on top, what with all the head-scratching.
After switching to the live-ebuilds for frameworks and plasma, the problem seems to be gone. Konsole(s) are saved and restored correctly again.
(In reply to Johannes Hirte from comment #19) > After switching to the live-ebuilds for frameworks and plasma, the problem > seems to be gone. Konsole(s) are saved and restored correctly again. I don't know what you mean by live ebuilds, but I'm on kde-frameworks/plasma-5.88.0-r1 and kde-plasma/plasma-meta-5.23.4, and the fault is still present. (The rest of kde-frameworks is at 5.88.0.)
(In reply to peter@prh.myzen.co.uk from comment #20) > (In reply to Johannes Hirte from comment #19) > > After switching to the live-ebuilds for frameworks and plasma, the problem > > seems to be gone. Konsole(s) are saved and restored correctly again. > > I don't know what you mean by live ebuilds, but I'm on > kde-frameworks/plasma-5.88.0-r1 and kde-plasma/plasma-meta-5.23.4, and the > fault is still present. (The rest of kde-frameworks is at 5.88.0.) Live ebuilds are 9999 (from git). And I was wrong. I have one konsole that is restored correctly. Everything else is still missing after logout/login. This is really strange.
Anyone have any revelations on this? Still affecting this one machine. I did notice that if I manually kill kwalletmanager5 prior to logging out, the desktop doesn't seem to pause on logout (which is what I thought was causing it to not save konsole sessions). However, it doesn't fix the issue for me.
I still see it here on two machines. One is an Intel i7-5820K and the other is a Ryzen M9 5900X. Both are running Gentoo ~amd64, and the Ryzen box also suffered the fault while running Gentoo amd64. Neither of them is over-clocked. The fault is repeatable, and the only way to avoid it is to log in to a new user account, set up three (in my case) Konsole windows, then run the system settings app, changing only one thing at a time and logging out and in again before making another change. If the fault appears, start all over again.
Do you happen to use the "New Session" feature of plasma? The one where you can log into a different account, but leave the current one running in the background? I'm just trying to think of things that I do differently on this particular machine compared to the others that are not affected.
(In reply to David Flogeras from comment #24) > Do you happen to use the "New Session" feature of plasma? The one where you > can log into a different account, but leave the current one running in the > background? I don't, no. I don't know how I might do it, as I haven't heard of it.
I don't think we can do anything here. Please follow-up with upstream on this matter.
