Overuse of system beep without volume control
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Fix Released
|
High
|
Unassigned | ||
libgnome (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt | ||
Karmic |
Fix Released
|
Medium
|
Martin Pitt | ||
linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
Karmic |
Won't Fix
|
Medium
|
Unassigned | ||
module-init-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Karmic |
Fix Released
|
Undecided
|
Unassigned | ||
pulseaudio (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Karmic |
Won't Fix
|
Medium
|
Luke Yelavich |
Bug Description
System 'beeps' have become omnipresent in gnome. When I unplug my power cord, the notification system emits a system beep. When I try to do quick find in Firefox and I type a word that doesn't exist in the document, it beeps. When I tab-autocomplete in a gnome-terminal, it beeps if there are no completions. There are numerous other software packages that behave similarly.
This is a problem for multiple reasons.
First of all, there are some cases where the beep is used inappropriately -- I really *don't care* that my power cord is unplugged - in fact I unplugged it! I appreciate the technology advances that gnome-power-
Second of all, I can't control the volume of the beep, or disable it in all cases. In the case of the gnome-terminal I can disable the console "bell", but that only solves a single instance of the problem. In most other cases, there is nothing I can do to prevent the beeps. This can be very obtrusive in quite environments, and simply annoying in other cases. On my laptop (recent Dell Latitude D620) the beep is incredibly loud - it is very noticeable. It would be great to have a toggle button in the system "sound" preferences, or better yet, a volume slider for the system bell.
This is a large problem, affecting multiple packages and systems - I don't know the best way to fix it, but I do know that it is definitely an overall gnome UI issue. I've read that some programs literally just have the ASCII "BEL" coded into the source, so in some cases the problem may be unavoidable - I don't know enough of the technical details to recognize an appropriate solution.
Any help dividing this into specific fixes for multiple projects or identifying the best place for an overall fix would be appreciated.
Changed in hundredpapercuts: | |
status: | New → Confirmed |
Changed in hundredpapercuts: | |
milestone: | none → round-3 |
Changed in hundredpapercuts: | |
status: | Confirmed → Fix Released |
Changed in ayatana: | |
status: | New → Invalid |
Changed in module-init-tools (Ubuntu): | |
status: | Fix Released → New |
Changed in hundredpapercuts: | |
status: | Fix Released → New |
tags: | added: regression-potential |
Changed in linux (Ubuntu Karmic): | |
assignee: | Canonical Kernel Team (canonical-kernel-team) → Andy Whitcroft (apw) |
tags: |
added: regression-release removed: regression-potential |
tags: | added: karmic |
affects: | alsa-lib (Ubuntu) → pulseaudio (Ubuntu) |
Changed in linux (Ubuntu): | |
assignee: | Andy Whitcroft (apw) → nobody |
Changed in linux (Ubuntu Karmic): | |
assignee: | Andy Whitcroft (apw) → nobody |
Changed in pulseaudio (Ubuntu): | |
assignee: | Luke Yelavich (themuso) → nobody |
Thanks for your comment. The changes you are requesting require more
discussion and should rather be done on an appropriate mailing list or
forum.
http:// www.ubuntu. com/community/ forums/ might be a good start.