| 2011-04-23 01:44:27 |
Robert Schroll |
bug |
|
|
added bug |
| 2011-04-23 01:45:04 |
Robert Schroll |
bug task added |
|
unity |
|
| 2011-04-23 01:52:08 |
Robert Schroll |
bug task added |
|
pulseaudio (Ubuntu) |
|
| 2011-04-23 01:52:43 |
Robert Schroll |
bug task added |
|
gnome-media (Ubuntu) |
|
| 2011-04-23 02:34:29 |
pablomme |
bug |
|
|
added subscriber pablomme |
| 2011-04-24 07:54:52 |
Bilal Akhtar |
unity (Ubuntu): status |
New |
Invalid |
|
| 2011-04-24 07:54:58 |
Bilal Akhtar |
unity: status |
New |
Invalid |
|
| 2011-04-25 00:08:08 |
Robert Schroll |
description |
Binary package hint: unity
This bug is about problems using the system bell in Unity or another Compiz-based environment. For problems using the system bell in Ubuntu Classic or a Metacity-based environment, please see bug #486154.
The system bell (that beep when you backspace on an empty line on a terminal, i.e.) is badly broken using the Unity environment in the Natty beta 2. By default, no sound is produced, and several misconfigurations make it difficult to produce sound either from the PC speaker or Pulse Audio's module-x11-bell. Not knowing what the desired behavior is, I can't say exactly what needs to be fixed. But the combination of the following issues makes the system quite obviously broken.
1) pcskpr is blacklisted.
The pcspkr module is necessary for the PC speaker to produce sound. It is blacklisted, so regular users cannot turn the bell on. It would be nice for this to be fixed, but the attitudes displayed in #77010 suggest that it won't be. Nonetheless, I note it here because it interacts with some of the following.
2) The X bell volume is set to 0.
As reported by `xset q`, the bell volume is 0 when Unity is started. Both the PC speaker and module-x11-bell respect this setting, so the volume must be turned up (with `xset b on` or `xset b 100`) for either to work. Since both the PC speaker and module-x11-bell are disabled by default, this setting only serves to frustrate attempts to turn them on; it never prevents unwanted sound.
3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11
This is a system file, not a user file, so users cannot decide whether they want this module loaded or not. They could write a script to unload the module at login (and hope the module number doesn't vary between boots), but it would be much cleaner to have the modules loaded from a user file, possibly with defaults if the user file doesn't exist.
4) Sample bell.ogg is not loaded.
When module-x11-bell is loaded, it is told to use the sample bell.ogg. But no sample is loaded into Pulse Audio. Thus, module-x11-bell traps system bell events (keeping them from going to the PC speaker) without producing any sound. If module-x11-bell is loaded, the sample it calls on should be loaded as well. (To fix this, run `pactl upload-sample /usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.)
5) gnome-volume-control doesn't.
The "Sound Effects" tab of gnome-volume-control offers to set the volume and sound for system bell events, but these have no effect. This is because gnome-volume-control is trying to control system bells through metacity. Ideally, it should be rewritten to control module-x11-bell instead, but a temporary fix could be to simply disable this tab.
6) System bell settings don't transfer to the Ubuntu Classic environment.
Because that is using metacity, which has it's own set of problems. See bug #486154.
This has been from testing in a VM (virtualbox), but all of these behaviors have also been seen in Compiz in various previous versions of Ubuntu running on various hardware.
I have reported this bug against several components, as it is really an integration issue. The eventual fix may not involve your component, but please do not mark this bug as invalid until we have at least a roadmap for fixing it. Otherwise, I fear responsibility will be passed from component to component without anything being fixed. Rationales:
Unity - As the overarching environment, Unity should be responsible for getting everything integrated. Additionally, some of the problems relate to session startup settings.
Pulse Audio - module-x11-bell is not loaded intelligently or correctly.
Gnome Media - Own gnome-volume-control.
Versions (but note the same behavior has been seen in many earlier versions):
unity: 3.8.10-0ubuntu2
pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3
gnome-media: 2.32.0-0ubuntu7 |
Binary package hint: unity
This bug is about problems using the system bell in Unity or another Compiz-based environment. For problems using the system bell in Ubuntu Classic/Metacity or another Metacity-based environment, please see bug #486154.
The system bell (that beep when you backspace on an empty line on a terminal, i.e.) is badly broken using the Unity environment in the Natty beta 2. By default, no sound is produced, and several misconfigurations make it difficult to produce sound either from the PC speaker or Pulse Audio's module-x11-bell. Not knowing what the desired behavior is, I can't say exactly what needs to be fixed. But the combination of the following issues makes the system quite obviously broken.
1) pcskpr is blacklisted.
The pcspkr module is necessary for the PC speaker to produce sound. It is blacklisted, so regular users cannot turn the bell on. It would be nice for this to be fixed, but the attitudes displayed in #77010 suggest that it won't be. Nonetheless, I note it here because it interacts with some of the following.
2) The X bell volume is set to 0.
As reported by `xset q`, the bell volume is 0 when Unity is started. Both the PC speaker and module-x11-bell respect this setting, so the volume must be turned up (with `xset b on` or `xset b 100`) for either to work. Since both the PC speaker and module-x11-bell are disabled by default, this setting only serves to frustrate attempts to turn them on; it never prevents unwanted sound.
3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11
This is a system file, not a user file, so users cannot decide whether they want this module loaded or not. They could write a script to unload the module at login (and hope the module number doesn't vary between boots), but it would be much cleaner to have the modules loaded from a user file, possibly with defaults if the user file doesn't exist.
4) Sample bell.ogg is not loaded.
When module-x11-bell is loaded, it is told to use the sample bell.ogg. But no sample is loaded into Pulse Audio. Thus, module-x11-bell traps system bell events (keeping them from going to the PC speaker) without producing any sound. If module-x11-bell is loaded, the sample it calls on should be loaded as well. (To fix this, run `pactl upload-sample /usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.)
5) gnome-volume-control doesn't.
The "Sound Effects" tab of gnome-volume-control offers to set the volume and sound for system bell events, but these have no effect. This is because gnome-volume-control is trying to control system bells through metacity. Ideally, it should be rewritten to control module-x11-bell instead, but a temporary fix could be to simply disable this tab.
6) System bell settings don't transfer to the Ubuntu Classic environment.
Because that is using metacity, which has it's own set of problems. See bug #486154.
This has been from testing in a VM (virtualbox), but all of these behaviors have also been seen in Compiz in various previous versions of Ubuntu running on various hardware.
I have reported this bug against several components, as it is really an integration issue. The eventual fix may not involve your component, but please do not mark this bug as invalid until we have at least a roadmap for fixing it. Otherwise, I fear responsibility will be passed from component to component without anything being fixed. Rationales:
Unity - As the overarching environment, Unity should be responsible for getting everything integrated. Additionally, some of the problems relate to session startup settings.
Pulse Audio - module-x11-bell is not loaded intelligently or correctly.
Gnome Media - Own gnome-volume-control.
Versions (but note the same behavior has been seen in many earlier versions):
unity: 3.8.10-0ubuntu2
pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3
gnome-media: 2.32.0-0ubuntu7 |
|
| 2011-05-12 20:51:35 |
Juha Siltala |
bug |
|
|
added subscriber Juha Siltala |
| 2011-05-15 12:29:13 |
Chris Boot |
bug |
|
|
added subscriber Chris B |
| 2011-05-22 02:21:34 |
Marek Blahuš |
bug |
|
|
added subscriber Marek Blahuš |
| 2011-06-01 06:22:15 |
Emily Strickland |
bug |
|
|
added subscriber Emily Strickland |
| 2011-06-17 15:16:33 |
Emily Strickland |
branch linked |
|
lp:~hypodermia/ubuntu/oneiric/compiz/fix-for-bug-301174 |
|
| 2011-06-18 19:46:49 |
eris23 |
bug |
|
|
added subscriber eris23 |
| 2011-09-22 00:40:01 |
Launchpad Janitor |
gnome-media (Ubuntu): status |
New |
Confirmed |
|
| 2011-09-22 00:40:01 |
Launchpad Janitor |
pulseaudio (Ubuntu): status |
New |
Confirmed |
|
| 2011-10-31 11:20:37 |
Khamoon |
bug |
|
|
added subscriber Khamoon |
| 2011-11-26 01:18:44 |
Rafał Krypa |
bug |
|
|
added subscriber Rafał Krypa |
| 2012-01-22 00:50:17 |
Matthew Newton |
bug |
|
|
added subscriber Matthew Newton |
| 2012-02-15 04:45:28 |
Pieter van der Merwe |
bug |
|
|
added subscriber Pieter van der Merwe |
| 2012-02-15 04:45:29 |
cleary |
bug |
|
|
added subscriber cleary |
| 2012-02-15 05:11:14 |
Billrobo |
bug |
|
|
added subscriber Billrobo |
| 2012-03-30 00:30:38 |
Kevin Masaryk |
bug |
|
|
added subscriber Kevin Masaryk |
| 2012-05-08 18:00:07 |
Ben Williams |
bug |
|
|
added subscriber Ben Williams |
| 2012-05-16 17:36:39 |
Paddy Launch |
bug |
|
|
added subscriber Paddy Launch |
| 2013-07-12 09:14:29 |
Ben Cracknell |
bug |
|
|
added subscriber Ben Cracknell |
| 2014-04-22 17:43:14 |
Matthew Newton |
removed subscriber Matthew Newton |
|
|
|
| 2014-04-28 11:09:30 |
Vladimir Pycha |
bug watch added |
|
https://bugzilla.redhat.com/show_bug.cgi?id=607393 |
|
| 2014-04-28 11:13:04 |
Vladimir Pycha |
bug |
|
|
added subscriber Vladimir Pycha |
| 2014-09-29 19:52:28 |
Hontvári József Levente |
bug |
|
|
added subscriber Hontvári József Levente |
| 2014-11-07 05:12:31 |
Daniel Hahler |
pulseaudio (Ubuntu): status |
Confirmed |
Triaged |
|
| 2014-11-07 05:28:09 |
Daniel Hahler |
attachment added |
|
debdiff for pulseaudio: upload bell.ogg https://bugs.launchpad.net/ubuntu/+source/unity/+bug/769314/+attachment/4255002/+files/pulseaudio_4.0-0ubuntu23.dsc.debdiff |
|
| 2014-11-07 05:31:20 |
Daniel Hahler |
pulseaudio (Ubuntu): importance |
Undecided |
High |
|
| 2014-11-07 08:21:18 |
Ubuntu Foundations Team Bug Bot |
tags |
|
patch |
|
| 2015-12-14 07:22:16 |
Nicola Larosa |
pulseaudio (Ubuntu): status |
Triaged |
In Progress |
|
| 2016-01-07 20:44:12 |
Michael J. Ford |
bug |
|
|
added subscriber Michael J. Ford |
| 2016-07-10 04:29:06 |
Shaleen Jain |
bug |
|
|
added subscriber Shaleen Jain |
| 2017-02-03 20:29:09 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2017-02-03 22:19:25 |
Iiro Laiho |
summary |
System bell broken in Natty/Unity (despite heroic...) |
System bell completely silent because PulseAudio sample file undefined by default |
|
| 2017-02-03 22:42:42 |
Iiro Laiho |
tags |
patch |
patch xenial |
|
| 2017-02-03 22:46:21 |
Iiro Laiho |
description |
Binary package hint: unity
This bug is about problems using the system bell in Unity or another Compiz-based environment. For problems using the system bell in Ubuntu Classic/Metacity or another Metacity-based environment, please see bug #486154.
The system bell (that beep when you backspace on an empty line on a terminal, i.e.) is badly broken using the Unity environment in the Natty beta 2. By default, no sound is produced, and several misconfigurations make it difficult to produce sound either from the PC speaker or Pulse Audio's module-x11-bell. Not knowing what the desired behavior is, I can't say exactly what needs to be fixed. But the combination of the following issues makes the system quite obviously broken.
1) pcskpr is blacklisted.
The pcspkr module is necessary for the PC speaker to produce sound. It is blacklisted, so regular users cannot turn the bell on. It would be nice for this to be fixed, but the attitudes displayed in #77010 suggest that it won't be. Nonetheless, I note it here because it interacts with some of the following.
2) The X bell volume is set to 0.
As reported by `xset q`, the bell volume is 0 when Unity is started. Both the PC speaker and module-x11-bell respect this setting, so the volume must be turned up (with `xset b on` or `xset b 100`) for either to work. Since both the PC speaker and module-x11-bell are disabled by default, this setting only serves to frustrate attempts to turn them on; it never prevents unwanted sound.
3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11
This is a system file, not a user file, so users cannot decide whether they want this module loaded or not. They could write a script to unload the module at login (and hope the module number doesn't vary between boots), but it would be much cleaner to have the modules loaded from a user file, possibly with defaults if the user file doesn't exist.
4) Sample bell.ogg is not loaded.
When module-x11-bell is loaded, it is told to use the sample bell.ogg. But no sample is loaded into Pulse Audio. Thus, module-x11-bell traps system bell events (keeping them from going to the PC speaker) without producing any sound. If module-x11-bell is loaded, the sample it calls on should be loaded as well. (To fix this, run `pactl upload-sample /usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.)
5) gnome-volume-control doesn't.
The "Sound Effects" tab of gnome-volume-control offers to set the volume and sound for system bell events, but these have no effect. This is because gnome-volume-control is trying to control system bells through metacity. Ideally, it should be rewritten to control module-x11-bell instead, but a temporary fix could be to simply disable this tab.
6) System bell settings don't transfer to the Ubuntu Classic environment.
Because that is using metacity, which has it's own set of problems. See bug #486154.
This has been from testing in a VM (virtualbox), but all of these behaviors have also been seen in Compiz in various previous versions of Ubuntu running on various hardware.
I have reported this bug against several components, as it is really an integration issue. The eventual fix may not involve your component, but please do not mark this bug as invalid until we have at least a roadmap for fixing it. Otherwise, I fear responsibility will be passed from component to component without anything being fixed. Rationales:
Unity - As the overarching environment, Unity should be responsible for getting everything integrated. Additionally, some of the problems relate to session startup settings.
Pulse Audio - module-x11-bell is not loaded intelligently or correctly.
Gnome Media - Own gnome-volume-control.
Versions (but note the same behavior has been seen in many earlier versions):
unity: 3.8.10-0ubuntu2
pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3
gnome-media: 2.32.0-0ubuntu7 |
Binary package hint: unity
This bug is about problems using the system bell in Unity or another Compiz-based environment. For problems using the system bell in Ubuntu Classic/Metacity or another Metacity-based environment, please see bug #486154.
The system bell (that beep when you backspace on an empty line on a terminal, i.e.) is badly broken using the Unity environment in the Natty beta 2. By default, no sound is produced, and several misconfigurations make it difficult to produce sound either from the PC speaker or Pulse Audio's module-x11-bell. Not knowing what the desired behavior is, I can't say exactly what needs to be fixed. But the combination of the following issues makes the system quite obviously broken.
1) pcskpr is blacklisted.
The pcspkr module is necessary for the PC speaker to produce sound. It is blacklisted, so regular users cannot turn the bell on. It would be nice for this to be fixed, but the attitudes displayed in #77010 suggest that it won't be. Nonetheless, I note it here because it interacts with some of the following.
2) The X bell volume is set to 0. (no more true in xenial)
As reported by `xset q`, the bell volume is 0 when Unity is started. Both the PC speaker and module-x11-bell respect this setting, so the volume must be turned up (with `xset b on` or `xset b 100`) for either to work. Since both the PC speaker and module-x11-bell are disabled by default, this setting only serves to frustrate attempts to turn them on; it never prevents unwanted sound.
3) module-x11-bell is loaded by /usr/bin/start-pulseaudio-x11
This is a system file, not a user file, so users cannot decide whether they want this module loaded or not. They could write a script to unload the module at login (and hope the module number doesn't vary between boots), but it would be much cleaner to have the modules loaded from a user file, possibly with defaults if the user file doesn't exist.
4) Sample bell.ogg is not loaded.
When module-x11-bell is loaded, it is told to use the sample bell.ogg. But no sample is loaded into Pulse Audio. Thus, module-x11-bell traps system bell events (keeping them from going to the PC speaker) without producing any sound. If module-x11-bell is loaded, the sample it calls on should be loaded as well. (To fix this, run `pactl upload-sample /usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg`.)
5) gnome-volume-control doesn't.
The "Sound Effects" tab of gnome-volume-control offers to set the volume and sound for system bell events, but these have no effect. This is because gnome-volume-control is trying to control system bells through metacity. Ideally, it should be rewritten to control module-x11-bell instead, but a temporary fix could be to simply disable this tab.
6) System bell settings don't transfer to the Ubuntu Classic environment.
Because that is using metacity, which has it's own set of problems. See bug #486154.
This has been from testing in a VM (virtualbox), but all of these behaviors have also been seen in Compiz in various previous versions of Ubuntu running on various hardware.
I have reported this bug against several components, as it is really an integration issue. The eventual fix may not involve your component, but please do not mark this bug as invalid until we have at least a roadmap for fixing it. Otherwise, I fear responsibility will be passed from component to component without anything being fixed. Rationales:
Unity - As the overarching environment, Unity should be responsible for getting everything integrated. Additionally, some of the problems relate to session startup settings.
Pulse Audio - module-x11-bell is not loaded intelligently or correctly.
Gnome Media - Own gnome-volume-control.
Versions (but note the same behavior has been seen in many earlier versions):
unity: 3.8.10-0ubuntu2
pulseaudio: 1:0.9.22+stable-queue-24-g67d18-0ubuntu3
gnome-media: 2.32.0-0ubuntu7 |
|
| 2017-02-03 23:11:57 |
Paddy Launch |
removed subscriber Paddy Launch |
|
|
|
| 2017-02-04 16:52:36 |
Alberto Salvia Novella |
pulseaudio (Ubuntu): importance |
High |
Medium |
|
| 2017-02-04 16:52:38 |
Alberto Salvia Novella |
gnome-media (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-02-04 16:52:40 |
Alberto Salvia Novella |
unity (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-02-04 16:52:43 |
Alberto Salvia Novella |
pulseaudio (Ubuntu): status |
In Progress |
Confirmed |
|
| 2017-03-23 04:13:00 |
Drew R. |
bug |
|
|
added subscriber Drew Rosoff |
| 2017-03-29 18:47:14 |
Michael Terry |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2017-03-29 18:47:19 |
Michael Terry |
bug |
|
|
added subscriber Michael Terry |
| 2017-03-30 01:22:36 |
Launchpad Janitor |
pulseaudio (Ubuntu): status |
Confirmed |
Fix Released |
|
