system settings -> notification there's no way to disable all sounds at once anymore. it is extremely user unfriendly to have to go through all event sources and then each possible state which does require several steps for each single entry: #1 select event source from dropdown #2 select state #3 uncheck "play a sound" # repeat which cannot not be don without jumping around excessively with either mouse or keyboard. give the nasty #352457 it's even more urgent to allow people to get rid of those annoying sounds in one fell swoop. this can in fact be extended to provide "disable all" facilities for all notification types (sound, popup, log, mark taskbar entry, run command), because the UI does not allow for easy and fluent configuration of either. i am not sure, if the version matches -- for reasons i fail to understand, there's neither an indication of the module's name used for bug reports nor a version number anywhere in these kcm UIs, so i took the version from the containing package of the closest looking file. Reproducible: Always
Thanks for the report We use the "Event sounds" channel of PulseAudio for notification sounds, you should be able to just mute that channel in either kmix or install pavucontrol package and disable there. This however works only with phonon-gstreamer backend as there is a bug in the vlc backend that the vlc devs don't want to fix.
please, do not close a report before i had a chance to answer! in this case you are missing my point -- while it may be a _work-around_ to disable the channel, this is not what i am refering to! when the notifications channels to be configured in the notifications module, then the missing feature hast to be that very module. sound is completely different module and at least from a usability POV has nothing to do with it -- after all, one doesn't configure/enable the sound notifications there, why should one disable them there instead of the appropriate module -- which obviously is the notifications module.
Sound volume belongs to the mixer. If the sound is bothering you, it's not a _workaround_ to mute them in the mixer, it's intended. The notifications configuration allows you to select _which_ sound will be played. We are not going to add any other sound controls at this point, sorry.
why then, pray tell, is the sound notification part of the notifications module? if you are right, it has to be moved to the sound module. i am not (at least not only) talking about _volume_ but summarily disabling sound notifications, which is a genuine feature of notifications configuration (just instead of walking over all possible events and unchecking the box each time, having one place for all). this feature has been there in plasma 4 and i fail to understand why usability has to suffer for obscure reasons with plasma 5.
> why then, pray tell, is the sound notification part of the notifications module? > if you are right, it has to be moved to the sound module. Because one event can do several actions. You are configuring "what happens when this event happens". I'm sure you don't want to open a different module just to configure which sound gets played at any given event. Muting an audio channel equals "summarily disabling sound notifications". > this feature has been there in plasma 4 and i fail to understand why usability has to suffer for obscure reasons with plasma 5. This plasma4 feature you are referring to did exactly that. It muted the event sounds channel.
Duplicate of bug 157272?
yes, marking so, thanks for pointing that out. *** This bug has been marked as a duplicate of bug 157272 ***