Bug 375130

Summary:	the sound settings are ignored and restored back to defaults
Product:	[Frameworks and Libraries] frameworks-knotifications	Reporter:	acn481
Component:	general	Assignee:	Martin Klapetek <mklapetek>
Status:	RESOLVED FIXED
Severity:	normal	CC:	elvis.angelaccio, kdelibs-bugs-null, nate, thomas.roell
Priority:	NOR
Version First Reported In:	5.27.0
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description acn481 2017-01-16 07:54:45 UTC

In the playback devices I've put my audio volume to 15% (Built-in Audio Analog Stereo), and also disabled "Notification Sounds" in the Audio Settings.

Now, when I press Shift-Delete in Dolphin to delete some file, the confirmation dialog appears. The sound of notification is played and audio volume is 100% again.

There is no such problem when I do the same on the KDE Desktop.

KDE Plasma 5.8.2
KDE Frameworks 5.27.0
kernel 4.8.0-2-amd64

Comment 1 Elvis Angelaccio 2017-01-16 09:46:02 UTC

Can you try to do the same (Shift+Del) with Gwenview? I don't think this is Dolphin-specific.

Comment 2 acn481 2017-01-16 10:36:30 UTC

(In reply to Elvis Angelaccio from comment #1)
> Can you try to do the same (Shift+Del) with Gwenview? I don't think this is
> Dolphin-specific.

Elvis, You're right. I've tried this on Gwenview with the same result. Probably the problem is elsewhere. I'll try to gather more info about this bug.

Comment 3 Elvis Angelaccio 2017-01-16 10:37:46 UTC

Thanks. Moving to knotifications for more investigations.

Comment 4 thomas.roell 2017-02-15 16:19:30 UTC

when I press Shift-Delete in Dolphin, or use the context-menu, to delete some file, the confirmation dialog appears and Sound is played at 100%;
Sound settings appear unchanged to me;
In Gwenview Shift-Delete doesnt work( misconf? ), with context-menu no Sound.
In sysconf->notifications found no matching entry

Comment 5 Nate Graham 2021-08-09 16:55:40 UTC

This was fixed a long time ago. The only remaining related issue to my knowledge is that the defualt value is not read correctly; see Bug 425974.