For some time now, when I start a plasma session (x11, AMD graphics Ryzen 7 5700G, Gentoo Linux) I get two copies each of xosview and conky, but not gkrellm or any other applications, all of which start correctly with one copy (based on what was running when I logged out.) On one occasion, I neglected to close the extras (they are started on top of each other, so it’s not obvious except by looking at the task bar) and when I restarted, I then had four of each of them.
I’m aware of session-restore not working properly on Wayland, but this is x11, and is not a failure to restart anything, it’s that those two applications get started twice.
Qt: 6.8.1, KDE Frameworks: 6.10.0, KDE Plasma: 6.2.5, KDE Apps: 24.08.3
Where is the list of apps to restart saved? I assume it would help to know if the apps are being stored twice, or perhaps being restarted by two different mechanisms.
Hi - and for what it’s worth, I believe the state file for session restore (if you want to check the contents of that) is located here: ~/.local/state/plasmasessionrestorestaterc
The only think in Autostart is dolog, and I have no idea what that is. Removing it made no difference. If I close those apps before logging out, they do not appear when I log in again.
Note that I do not use a display manager, and log in by running startx, in case it matters.
Setting to restore with clean session, logging out, emptying ~/.cache, and logging in gave me a clean session. I started all the usual programs. Reset to restore session at logout, logout, login gave me one copy of each program. However, another logout/login was back to two copies. Maybe there is something wrong/extra saved in .cache, but it clearly comes back, so unless I can determine which it is, knowing doesn’t seem to help.
I have no delay set, and am not using autostart, but I’m curious how you think adding a delay could help. Also, if I do use autostart, then won’t they get started both by the autostart and because they were in the session when I logged out?
[Sorry for the multiple replies - they do indicate who I was replying to, but I had thought they might be indented.]
I notice that ~/.local/state/plasmasessionrestorestaterc does not include entries for konsole or firefox, for example, but they get restored properly. I wonder if apps that plasma knows can properly restore themselves (is that a thing?) do not need to be included in that file? If that is so, then perhaps xosview and conky need to be added to the list of apps that do not need to be added to that file. Either that, or might there be another file also used to track what needs to be restarted?
AHA! I logged out, and deleted that file. On logging in again, everything was started just onde. Oddly, balsa (email client) was also restarted, even though it had been listed in that file, but was never started twice. I think there is more to restarting a session than meets the eye.
This is the script I use and which is pointed to in my autostart. And no, it acts as it should ( a sleep 20 delay and remembering the last used conky), regardless a session restore or not.
No script for me. I just type “conky” either in bash in konsole, or to the prompt I get with Alt-Space or Alt-F2. Yes, it has to be being started SOMEWHERE, but so is XOsview. I suppose I’ll keep hunting through .local for references.
The priority for solving this has now decreased for me, since I’ve finished a period of instability with my PC. Since I no longer NEED to reboot or re-login so often, it’s less annoying. However, I do plan on still paying attention and trying to figure out what’s going on. I might even add some debug output to either conky or xosview, perhaps by moving the binary and introducing a script.