Dear developers, there is s a little issue with KDE I want to tell you. It is not easy to describe, but please let me try:: When you have some application running, that got in its settings an option like "start with windowmanager" and this is activated, then this will be started as usual. As you know, KDE (plasma) also has the option, to save the actual state of running, and restore it at restart. BUT: When, you do this with such running applications, then at next start of KDE, those aplications are started twice, one because its own settings, the other because of KDE`s setting. This should not happen. A workaround is, stopping these applications and save state again, but that is of course not the comfortable way. Applications with this behaviour for this are for example keepassxc, kmail, barrier, telegram or signal. There are probably more. Although some applications got the option in theire setting "start only a single instance", there are two of them running (check with keepassxc). I can not say, which part is responsible for this, but it would be nice, if you could take an eye on it. Thank you very much! (And also for such great windowmanager!) Best regards Hans
I'm not able to replicate this with Plasma 6.3.2 or git-master using keepassxc or input-leap (which is the successor to barrier) Desktop Session restore set to "On last logout" With KeePassXC, I have the option "Start only a single instance of KeePassXC" enabled I only have one process for keepassxc For input-leap, it runs the same processes if I quit and restart as it does at system startup (there is more than one normally) Can you provide this information we ask for in the template? SOFTWARE/OS VERSIONS (available in About System) Linux/KDE Plasma: Also, can you attach a screenshot of System Settings -> Desktop Session? Thanks!
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.