Bug 567471

Summary: Eliminate PC speaker beep from GTK+ applications
Product: [openSUSE] openSUSE 11.2 Reporter: Tristan Miller <psychonaut>
Component: GNOMEAssignee: E-mail List <gnome-bugs>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: andreas_nordal_4, dimstar
Version: Final   
Target Milestone: ---   
Hardware: All   
OS: openSUSE 11.2   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Tristan Miller 2009-12-28 22:47:09 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.6) Gecko/20091210 SUSE/2.0.1-1.2 SeaMonkey/2.0.1

I use KDE 4 but often run GTK+ applications, like SeaMonkey and XEmacs, which insist on using the "PC speaker beep" as a system bell instead of the default KDE system notification.  This problem is compounded by the fact that on some computers it is impossible to lower the volume of the PC speaker to an acceptable level. On my system, even at its lowest setting, it literally hurts my ears when the PC speaker beeps through my headphones.

Is there not some way of automatically configuring GNOME/GTK+ to use the KDE system notification for its system bell?

Reproducible: Always

Steps to Reproduce:
1. Load a GTK+ app, such as XEmacs.
2. Do something to cause a system bell, such as trying to scroll up past the beginning of the buffer in XEmacs.

Actual Results:  
3. Annoying, ear-splittingly loud noise emanates from the PC speaker channel.

Expected Results:  
3. The default system notification sound should have been played.
Comment 1 Tristan Miller 2010-09-17 16:45:37 UTC 
Problem still exists in OpenSUSE 11.3.
Comment 2 Andreas Nordal 2011-06-16 07:45:19 UTC 
Problem still exists in OpenSUSE 11.4.

Wireshark, which is also a GTK+ application, was hurting the ears of me and my colleagues, even though I had blacklisted pcspkr. "xset b off" solved it. Other tricks you can try:
http://crunchbanglinux.org/forums/topic/8543/turning-off-system-beeps/
Comment 3 Dominique Leuenberger 2012-07-31 20:41:07 UTC 
Sorry, this bug did not get the attention it deserved.

Not likely, you have already upgraded to newer versions of openSUSE, which had
a lot more bug fixes.

We believe that this specific bug has been fixed during one of the release cycles; as such, I close the bug as 'FIXED'.

Should you be able to reproduce this issue on a newer openSUSE version, please
feel to report it again.