Bug 361400

Summary: Option to disable knotify sounds when full KDE is not installed
Product: [Frameworks and Libraries] frameworks-knotifications Reporter: Lucio Crusca <lucio>
Component: generalAssignee: Lucio Crusca <lucio>
Status: RESOLVED FIXED    
Severity: wishlist CC: kdelibs-bugs, nicolas.fella
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian unstable   
OS: Linux   
URL: https://lists.debian.org/debian-user/2016/04/msg00050.html
Latest Commit: Version Fixed In:

Description Lucio Crusca 2016-04-05 07:16:21 UTC
I run Xfce and a few KDE apps, but I haven't the full KDE desktop installed. When the KDE apps show notifications, some KDE subsystem library plays a sound (I assume it's knotify but I'm not sure) and it raises the sound volume.
There used to be a systemsettings command that let users access sound settings also when not running KDE, but that's not the case anymore, since the new systemsettings5 does not offer audio configuration.
A workaround is removing read permissions to the sound files with
    # chmod o-r /usr/share/sounds/KDE*
but that obviously falls short of a real solution.

Reproducible: Always

Steps to Reproduce:
1. Install Xfce and Konquest, but not the full KDE environment
2. Turn sound volume off in Xfce
3. Play konquest and look for a way to silence it

Actual Results:  
Konquest plays a sound on each notification and there's no applet or command to adjust the sound volume for it (or any other KDE app),

Expected Results:  
KDE apps sould respect the sound volume set by the user in a different desktop environment or KDE libraries should offer a command to adjust their sound volume (the latter being what I suggest here).
Comment 1 Nicolas Fella 2020-11-23 00:30:43 UTC
Notifications use the special event sound channel that can be configured with tools like pavucontrol. I consider this resolved.
Comment 2 Lucio Crusca 2020-11-23 00:37:39 UTC
Do you mean that notifications always used that channel and this bug never existed or that it's now the case and I should update to the latest version of something?
Comment 3 Nicolas Fella 2020-11-23 00:41:19 UTC
I only now that it's this way now, I don't know since when this is the case
Comment 4 Lucio Crusca 2020-11-23 01:06:31 UTC
Then I think it might be safer to close this bug with status "CLOSED - NOT A BUG". Both KDE 5 and PulseAudio 3 (first to have pavucontrol that I know of) date back years before I opened this bug, and it's likely this kind of architecture hasn't changed withing a KDE major release cycle.