https://bugs.kde.org/show_bug.cgi?id=497742
--- Comment #10 from Martin Schnitkemper <martin.schnitkem...@nexgo.de> --- Thank you for taking care of the problem. After further testing, I found out that it has something to do with session restoration. When I end a session, the sessions from the last logout are saved in "ksmserverrc" and restored when I log in; and that's when it happens. When I set the option "Start with an empty session", the problem no longer occurred. As a workaround, I added the application "kalarm" to the list of "Ignored applications" and after that the problem also no longer occurred. I looked in older backups and it was always the case that the application "kalarm" was in "ksmserverrc" as a session to be restored, so this is not new. However, I still don't understand why the application is not terminated when the user logs off so that it is not included as an application to be restored, because "kalarm" would be started in a new session via the autostart mechanism anyway. Conversely, it would be wrong to restore and run it if it was previously removed from autostart by the user. During the last system update, "kalarm" was not updated, but "qt6-base" and related components were, among others. The cause of the behavior may be found there. -- You are receiving this mail because: You are watching all bug changes.
