[Touch-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2017-02-03 Thread Ubuntu Foundations Team Bug Bot
The attachment "debdiff for pulseaudio: upload bell.ogg" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/769314

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in gnome-media package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Invalid

Bug 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

To manage notifications about this bug go to:

[Touch-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2017-02-03 Thread Iiro Laiho
Present in 16.04.

Is the silence of the X11 bell intentional behavior? This is a really
weird case. I mean, the bug has been open for longer than half a decade
and triaged for a couple of years as well. The fix also is very simple
and there are proposed patches.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/769314

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in gnome-media package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Invalid

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/769314/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : 

[Touch-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2016-01-11 Thread Michael J. Ford
This bug is still present in Ubuntu 14.04 "pulseaudio-module-x11"
version "1:4.0-0ubuntu11.1"

Worked around by running the following steps as outline here:
https://askubuntu.com/questions/96511/getting-the-pc-speaker-to-beep

1. Load the module pcspkr in /etc/modprobe.d/blacklist.conf (comment it out)
2. Remove the package pulseaudio-module-x11 (that seems to absorb all XBell 
events)
3. Place options snd-hda-intel beep_mode=2 into 
/etc/modprobe.d/enable-beep.conf 
4. reboot

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/769314

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in gnome-media package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Invalid

Bug 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

To manage notifications about this bug go to:

[Touch-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2015-12-13 Thread Nicola Larosa
Some additional information.

In the patch to /usr/bin/start-pulseaudio-x11:
http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/wily/pulseaudio/wily/view/head:/debian/patches/0006
-load-module-x11-bell.patch

line #9 should say "sample=x11-bell", rather than "sample=bell.ogg".

One additional change is needed to /etc/pulse/default.pa:
http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/wily/pulseaudio/wily/view/head:/src/daemon/default.pa.in

line #29 should be uncommented, to load an audio file as a sample named
"x11-bell".

Note that line #178 in the same file would use the "x11-bell" sample
name: however it should NOT be uncommented, as explained in comments
right above. module-x11-bell will be loaded by X running the /usr/bin
/start-pulseaudio-x11 command, via /etc/xdg/autostart/pulseaudio.desktop
.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/769314

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in gnome-media package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Invalid

Bug 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 

[Touch-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2015-12-13 Thread Nicola Larosa
** Changed in: pulseaudio (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/769314

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in gnome-media package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Invalid

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/769314/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2015-05-22 Thread Alberto Mardegan
This is still broken in 14.04. The workaround from point #4 fixes the
issue for me:

pactl upload-sample /usr/share/sounds/ubuntu/stereo/bell.ogg bell.ogg

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/769314

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in gnome-media package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Invalid

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/769314/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2014-12-02 Thread David D Lowe
I just want to say, what a superbly written bug report, and I hope this
gets fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/769314

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in gnome-media package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Invalid

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/769314/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2014-09-29 Thread Hontvári József Levente
There is still no bell in gterm on Ubuntu 14.04. Workaround in #18 does
not help.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/769314

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in “gnome-media” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/769314/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 769314] Re: System bell broken in Natty/Unity (despite heroic...)

2014-09-29 Thread Hontvári József Levente
Workaround in #10 does work in Ubuntu 14.04. After applying it, there is
a bell sound in gterm.

(#18 is also good, but note that in that example actual-bell.ogg must
be  a path to a real ogg file, while bell.ogg seems to be a build-in
identifier which must not be touched.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/769314

Title:
  System bell broken in Natty/Unity (despite heroic...)

Status in Unity:
  Invalid
Status in “gnome-media” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Invalid

Bug 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/769314/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   :