nate@Liberator:~/kde/src/breeze-gtk$ (master) grep -ri bell . ./src/settings.ini:4:gtk-error-bell=0 nate@Liberator:~/kde/src/breeze-gtk$ (master) gri bell ~/.config/gtk* [no output] Not sure whether this is a bug in the theme itself, or in kde-gtk-config, or in the style KCM. But regardless, it isn't getting exported anymore, so my GTK applications are making disturbing sounds again.
"gtk-error-bell" was never exported in kde-gtk-config AFAIK.
Indeed this is not exported by kde-gtk-config, it is present in /usr/share/themes/Breeze/settings.ini. I do not know if/when Gtk loads this file though.
Hmm, I can confirm that it looks good on my system. Maybe GTK stopped reading that file? Is that possible?
Maybe kde-gtk-config can export that file to the settings.ini file in the user's homedir, where we can be sure it does get read?
(In reply to Alois Wohlschlager from comment #2) > Indeed this is not exported by kde-gtk-config, it is present in > /usr/share/themes/Breeze/settings.ini. I do not know if/when Gtk loads this > file though. Looks like it's set in breeze-gtk's ini file: https://invent.kde.org/plasma/breeze-gtk/-/blob/master/src/settings.ini
Looked into doing this in kde-gtk-config, and it works, but it just didn't feel like the right place to do it, as this would result in overriding user settings in the case that a user liked the bell and forced it to on. Ultimately the best solution here is for the system to load the pulseaudio-x11-bell or pipewire-x11-bell module, both of which translate the awful bell sound into something nice. For PipeWire, this module is not loaded by default: https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/src/daemon/pipewire.conf.in#L162 I'll submit a patch to load it by default at the PipeWire level. If it's rejected, I'll ask distros to do it. :)
https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1375