Bug 516816 - increase beep rate limit from 1/1s to 1/100ms
Summary: increase beep rate limit from 1/1s to 1/100ms
Keywords:
Status: CLOSED DUPLICATE of bug 498608
Alias: None
Product: Fedora
Classification: Fedora
Component: metacity
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-11 15:37 UTC by Chris Adams
Modified: 2018-04-11 09:05 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-16 16:26:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Chris Adams 2009-08-11 15:37:49 UTC
I'm not sure if xorg-x11-server is the right place to file this, but I can't figure out a better place.  Please feel free to redirect me.

Starting with Fedora 11, under the GNOME desktop, in both plain old xterm and gnome-terminal, the terminal bell (e.g. from tab completion, "ping -a", etc.) is now captured by GNOME and plays a sound effect instead of just beeping the PC speaker.  I guess that's nice if you like sound effects and/or your PC speaker doesn't work, but I want the plain old beep back.  How do I get that?

If I go to Preferences->Sound, I can only change the sound effect or disable it; I can't get the PC speaker to beep.  I guess I'd like to leave the GNOME "alert sound" to a sound effect (I don't really care about it); I just want my xterms to beep at me like they have for the last 18 years.

The sound effects really suck for "ping -a"; they are all a little too long (most of the time), so instead of a regular beep-per-second, you get intermittent sound effects and silence.

I have tried tracing down where this is happening, but I can't figure it out.

Comment 1 Matěj Cepl 2009-08-11 17:18:02 UTC
Not sure exactly, but hopefully this is better direction.

Comment 2 Lennart Poettering 2009-08-11 18:26:29 UTC
It's metacity which converts XBell into a libcanberra call. Reassigning to metacity. But honestly I believe the PC speaker should just die, die die.

If you think the default alert sound is too long then consider replacing it by a shorter one.

Comment 3 Chris Adams 2009-08-11 18:36:38 UTC
I have computers with no speakers attached.  On most of the others, the speakers are usually off (or turned down low), unless I am listening to music, watching a video, etc.  I thought the beep was just gone again until I realized it wasn't just xterm.

Why are things that have worked for years (decades?) removed just because you don't like them?

Comment 4 Chris Adams 2009-08-11 18:49:53 UTC
Also, shouldn't it be libcanberra that should support beeping the speaker for an alert message, not metacity?  There should be only one place to set sound preferences.

Comment 5 Chris Adams 2009-08-12 19:15:16 UTC
The length of the sound file has nothing to do with the missing sounds either.  Something (I guess libcanberra) is rate-limiting the alert sound to a maximum of one per second.  Something beeping right at 1Hz will get random drops (as some will come in early and some late).  Beeping at 1.001Hz will get every beep; beeping at .49Hz will get every other beep, and so on.

An arbitrary rate-limit like this is broken by design.

Comment 6 Lennart Poettering 2009-08-13 14:24:58 UTC
libcanberra does not rate limit. We do limit them max number of concurrent events though.

So what do you actually want? That metacity's Xbell to libcanberra mapping should be optional? Or do you think lc is buggy and rate limits event sounds? If it's the latter then the titlte of the bug should be changed.

Comment 7 Lennart Poettering 2009-09-29 03:26:28 UTC
metacity was doing the rate limiting. In rawhide I have now increased the rate from 1/1s to 1/100ms. While this still makes sure that we don't end up in a "beep storm" it shouldn't feel anymore as if we lose beeps.

Comment 8 Chris Adams 2009-09-30 13:45:17 UTC
Thanks for the update; sorry I missed that it was metacity doing the rate limiting.  Any chance that change could be pushed in an F11 update?  "ping -a" is rather annoying without it.

As for the beep (the primary issue for this ticket): IMHO, the PC speaker would be an option at libcanberra (just like other types of sounds).  If it was a metacity option, there'd have to be some new way to configure it, separate from the current "set the alert sound" screen, which would be confusing.  How hard would it be for libcanberra to have an option to pass the alert sound back to the X server for the old-style beep?

Comment 9 Lennart Poettering 2009-10-02 09:10:58 UTC
(In reply to comment #8)
> Thanks for the update; sorry I missed that it was metacity doing the rate
> limiting.  Any chance that change could be pushed in an F11 update?  "ping -a"
> is rather annoying without it.

Uh, I am not really that fond of doing backports. Will reassign to metacity now, maybe someone there wants to do that.

> As for the beep (the primary issue for this ticket): IMHO, the PC speaker would
> be an option at libcanberra (just like other types of sounds).  If it was a
> metacity option, there'd have to be some new way to configure it, separate from
> the current "set the alert sound" screen, which would be confusing.  How hard
> would it be for libcanberra to have an option to pass the alert sound back to
> the X server for the old-style beep?  

That wouldn't really work. We lose the context information of the bell event, so we cannot forward that to the beep hw anymore. 

Also, I really don't think the hw bell is desirable. Unless someone supplies me with a clean patch that is worth to be merged I am not spending time on this, sorry.

Comment 10 Owen Taylor 2009-11-16 16:26:41 UTC
Marking as a dup on the original Metacity bug. (Not going to do the backport to F11 at this point, since F12 is almost out.)

*** This bug has been marked as a duplicate of bug 498608 ***


Note You need to log in before you can comment on or make changes to this bug.