Yakuake is set to run at login. The option "Open window after program start" is disabled. However, Yakuake appears at every login and must be closed manually to see the whole desktop. The expected behavior is that Yakuake starts but does not present its window until invoked via the assigned key combo.
You're most likely starting Yakuake twice on logon (e.g. session restore and autostart). It opens when re-run while already running.
cannot confirm such behavior on Arch Linux. Yakuake starts at login but its window remains hidden until I press the shortcut to invoke it. yakuake 3.0.5 plasma 5.12.5
Eike, I think you are right about the cause. I had not put the pieces together until your suggestion, but the conflict of autostart and session resume apparently affects multiple applications. For example, I have a similar issue with wpa_gui, which is in autostart with the parameters to start in tray only and show signal strength there, but on login I get a window labeled wpa_gui<2> and there are two tray icons, one showing signal level and the other not. I will try adding both yakuake and wpa_gui to the "Applications to be excluded from sessions". If this is indeed the solution, then I would suggest to properly fix this by automatically excluding any applications in autostart from sessions (something which I assumed would have been done already).
Yeah, this is a good idea. Unfortunately session management (auto-restart on logon, etc.) has been dreadfully neglected in Plasma for many years, it really needs fresh eyes and some work.
I have the same issue, also note https://forum.manjaro.org/t/yakuake-and-online-accounts/2921 It really seems to be a problem with autostart and session restore. Since this is a bad default behaviour: Should this be treated in Yakuake or in a session management package? I'd be glad to be forwarded to a place where to create a corresponding issue then :)
Interesting. Did not remember I already commented here two years ago :) Now I come to this again since I experience this issue. To me that only happens on X11. Can anybody confirm? I also think that session-restore is somewhat broken on X11. So that might be the reason. Then also bug 423163 makes sense, where the broken session restore from the previous X11 session reaches into the afterwards started Wayland session.
(In reply to Claudius Ellsel from comment #6) > To me that only happens on X11. Can anybody confirm? Happens to me on Wayland as well. Moving to session management as this is clearly not a Yakuake issue (I'm imaging there can be a workaround deployed in Yakuake, but I don't think its the Right Thing).
*** Bug 423163 has been marked as a duplicate of this bug. ***