With System Settings Version 4.97.0 Using KDE Frameworks 4.100.0, under Event Notifications and Actions, I cannot see the event for logging into the Plasma Next Workspace, which I used to associate with the login chime. Reproducible: Always
Event Source: KDE Workspace should have "Login" event. In the future, please do not report bugs for support questions. We have user forums for help and support.
Probably not yet ported. I am not sure who is the maintainer for this, so I reassign this to "general".
The login sound as a feature has been dropped. We felt it didn't add anything, and was just a remainder of trying to re-create the desktop systems of the 1990s. Do you have a specific use-case which requires the login sound? (I'll close this bugreport as WONTFIX, as it's a design decision, not a bug. Please don't feel discouraged by that to report bugs in the future.)
Note that the design decision is only for the default login sound (while this report is about the missing configuration for it). We will still allow for setting custom sounds, patch already in review at https://git.reviewboard.kde.org/r/118636/
Git commit c2f45884310daba8672233e247fdaf4f9acd5b48 by Martin Klapetek. Committed on 13/06/2014 at 15:39. Pushed by mklapetek into branch 'master'. [ksmserver]Reinstate login & logout sounds This returns the feature of having and configuring login/logout sounds for workspace; default remains off for both. M +1 -0 ksmserver/CMakeLists.txt A +2912 -0 ksmserver/plasma_workspace.notifyrc M +2 -0 ksmserver/server.h M +28 -3 ksmserver/shutdown.cpp M +4 -3 ksmserver/startup.cpp http://commits.kde.org/plasma-workspace/c2f45884310daba8672233e247fdaf4f9acd5b48
Git commit 019f3bf5262bb1a168c2e874b1ca45d1dea9a6f2 by Martin Klapetek. Committed on 19/06/2014 at 12:39. Pushed by mklapetek into branch 'master'. Revert "[ksmserver]Reinstate login & logout sounds" This reverts commit c2f45884310daba8672233e247fdaf4f9acd5b48. Apparently this can cause the login sequence to wait for PulseAudio and can delay the startup quite considerably, so temporarily reverting. REVIEW: 118636 Conflicts: ksmserver/plasma_workspace.notifyrc M +0 -1 ksmserver/CMakeLists.txt M +0 -2 ksmserver/server.h M +3 -28 ksmserver/shutdown.cpp M +3 -4 ksmserver/startup.cpp http://commits.kde.org/plasma-workspace/019f3bf5262bb1a168c2e874b1ca45d1dea9a6f2
*** Bug 342182 has been marked as a duplicate of this bug. ***
Martin, what's the status of this? I've yet to hear a good reason why it's a sensible feature, and given no-one has implemented it properly, I don't see much value in having it in this TODO list.
I'm not sure what's the best way of implementing this. Using KNotification during startup can be qutie heavy now but on the other hand it allows for configuring in the same place as you configure every other sound. Alternatively, KSMServer could play the sound directly by reading the .notifyrc config file, using something like aaplay. As for the feature itself, I have no strong opinions either way. I guess it's nice to have?
I can live with a design decision _not_ to have a log in and out sound anymore, but in that case it should not be present in Notification settings anymore, which is the case now. However I think it is nice to have.
*** Bug 346701 has been marked as a duplicate of this bug. ***
Git commit b0fe26bfb314698693fcf011e59a28769bd9a437 by Martin Klapetek. Committed on 14/05/2015 at 18:03. Pushed by mklapetek into branch 'master'. [ksmserver] Bring back the login sound Now it's played in its own thread, so should not block anything. REVIEW: 123770 M +24 -3 ksmserver/startup.cpp http://commits.kde.org/plasma-workspace/b0fe26bfb314698693fcf011e59a28769bd9a437
Git commit 124ae2712c5869273d95c0460e895ff995195696 by Lukáš Tinkl, on behalf of Martin Klapetek. Committed on 15/05/2015 at 00:54. Pushed by lukas into branch 'ltinkl/solid-power'. [ksmserver] Bring back the login sound Now it's played in its own thread, so should not block anything. REVIEW: 123770 M +24 -3 ksmserver/startup.cpp http://commits.kde.org/plasma-workspace/124ae2712c5869273d95c0460e895ff995195696
*** Bug 352976 has been marked as a duplicate of this bug. ***