[Touch-packages] [Bug 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
Wontfix. ** Changed in: metacity (Ubuntu) Status: Triaged => Invalid -- 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/486154 Title: System beep broken in Karmic despite heroic efforts to fix it Status in Metacity: New Status in libcanberra package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Confirmed Status in metacity package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Between Jaunty and Karmic, a number of changes were made to keep the PC speaker from beeping. As part of this, system bell events are now captured by metacity, which uses libcanberra to play a sound. For users without speakers, this fails to be useful. The current setup makes restoring the old behavior extremely difficult. The absolute show stopper is that metacity traps audible system bell events. This behavior is, as best we can tell, not configurable. The attached patch keeps metacity from capturing system bell events. It also removes the sound playback capability. As Lucid will be using pulse audio's module-x11-bell to play sounds for system bell events, it is not necessary for this capability to be in metacity. Additionally, this removes the discrepancy between metacity's and compiz's handling of system bell events. There are several other difficulties in enabling the system bell: 1) Even if it is taken out of the blacklist, the pcspkr module may not load properly. Another modprobe may be necessary to get it loaded. See bug #398161. 2) Something in Gnome's startup does the equivalent of `xset b off`, so `xset b on` must be run on every login. (Note that bug #280767 keeps you from setting the bell volume with xset.) 3) A number of settings in gnome-terminal and gconf may keep the shell from sounding system bell events. Comments #28, #34, and #50 give more detailed summaries of the various problems. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/486154/+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 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-lts-xenial (Ubuntu) Status: New => Confirmed -- 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/486154 Title: System beep broken in Karmic despite heroic efforts to fix it Status in Metacity: New Status in libcanberra package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Confirmed Status in metacity package in Ubuntu: Triaged Status in pulseaudio package in Ubuntu: Invalid Bug description: Between Jaunty and Karmic, a number of changes were made to keep the PC speaker from beeping. As part of this, system bell events are now captured by metacity, which uses libcanberra to play a sound. For users without speakers, this fails to be useful. The current setup makes restoring the old behavior extremely difficult. The absolute show stopper is that metacity traps audible system bell events. This behavior is, as best we can tell, not configurable. The attached patch keeps metacity from capturing system bell events. It also removes the sound playback capability. As Lucid will be using pulse audio's module-x11-bell to play sounds for system bell events, it is not necessary for this capability to be in metacity. Additionally, this removes the discrepancy between metacity's and compiz's handling of system bell events. There are several other difficulties in enabling the system bell: 1) Even if it is taken out of the blacklist, the pcspkr module may not load properly. Another modprobe may be necessary to get it loaded. See bug #398161. 2) Something in Gnome's startup does the equivalent of `xset b off`, so `xset b on` must be run on every login. (Note that bug #280767 keeps you from setting the bell volume with xset.) 3) A number of settings in gnome-terminal and gconf may keep the shell from sounding system bell events. Comments #28, #34, and #50 give more detailed summaries of the various problems. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/486154/+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 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
Okay, I submitted bug #1599599 for the same problem on Ubuntu 16.04 Xenial Xerus. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599599 -- 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/486154 Title: System beep broken in Karmic despite heroic efforts to fix it Status in metacity: New Status in libcanberra package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: New Status in metacity package in Ubuntu: Triaged Status in pulseaudio package in Ubuntu: Invalid Bug description: Between Jaunty and Karmic, a number of changes were made to keep the PC speaker from beeping. As part of this, system bell events are now captured by metacity, which uses libcanberra to play a sound. For users without speakers, this fails to be useful. The current setup makes restoring the old behavior extremely difficult. The absolute show stopper is that metacity traps audible system bell events. This behavior is, as best we can tell, not configurable. The attached patch keeps metacity from capturing system bell events. It also removes the sound playback capability. As Lucid will be using pulse audio's module-x11-bell to play sounds for system bell events, it is not necessary for this capability to be in metacity. Additionally, this removes the discrepancy between metacity's and compiz's handling of system bell events. There are several other difficulties in enabling the system bell: 1) Even if it is taken out of the blacklist, the pcspkr module may not load properly. Another modprobe may be necessary to get it loaded. See bug #398161. 2) Something in Gnome's startup does the equivalent of `xset b off`, so `xset b on` must be run on every login. (Note that bug #280767 keeps you from setting the bell volume with xset.) 3) A number of settings in gnome-terminal and gconf may keep the shell from sounding system bell events. Comments #28, #34, and #50 give more detailed summaries of the various problems. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/486154/+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 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
** Also affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: New -- 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/486154 Title: System beep broken in Karmic despite heroic efforts to fix it Status in metacity: New Status in libcanberra package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: New Status in metacity package in Ubuntu: Triaged Status in pulseaudio package in Ubuntu: Invalid Bug description: Between Jaunty and Karmic, a number of changes were made to keep the PC speaker from beeping. As part of this, system bell events are now captured by metacity, which uses libcanberra to play a sound. For users without speakers, this fails to be useful. The current setup makes restoring the old behavior extremely difficult. The absolute show stopper is that metacity traps audible system bell events. This behavior is, as best we can tell, not configurable. The attached patch keeps metacity from capturing system bell events. It also removes the sound playback capability. As Lucid will be using pulse audio's module-x11-bell to play sounds for system bell events, it is not necessary for this capability to be in metacity. Additionally, this removes the discrepancy between metacity's and compiz's handling of system bell events. There are several other difficulties in enabling the system bell: 1) Even if it is taken out of the blacklist, the pcspkr module may not load properly. Another modprobe may be necessary to get it loaded. See bug #398161. 2) Something in Gnome's startup does the equivalent of `xset b off`, so `xset b on` must be run on every login. (Note that bug #280767 keeps you from setting the bell volume with xset.) 3) A number of settings in gnome-terminal and gconf may keep the shell from sounding system bell events. Comments #28, #34, and #50 give more detailed summaries of the various problems. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/486154/+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 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
Hi all, It is six years later and this exact problem is back with Ubuntu 16.04 Xenial Xerus. I unblacklisted pcspkr and loaded the module, plus the overwhelming multitude of other steps. The "beep" command works and "echo blahblah | wall" also works, "but echo -e '\a'" and "printf '\a'" do nothing, nor does the rubout or other keys in terminal and Gedit. I've never submitted a bug before, but I'll try now and reference this bug so we can benefit from all your hard work. -- 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/486154 Title: System beep broken in Karmic despite heroic efforts to fix it Status in metacity: New Status in libcanberra package in Ubuntu: Invalid Status in metacity package in Ubuntu: Triaged Status in pulseaudio package in Ubuntu: Invalid Bug description: Between Jaunty and Karmic, a number of changes were made to keep the PC speaker from beeping. As part of this, system bell events are now captured by metacity, which uses libcanberra to play a sound. For users without speakers, this fails to be useful. The current setup makes restoring the old behavior extremely difficult. The absolute show stopper is that metacity traps audible system bell events. This behavior is, as best we can tell, not configurable. The attached patch keeps metacity from capturing system bell events. It also removes the sound playback capability. As Lucid will be using pulse audio's module-x11-bell to play sounds for system bell events, it is not necessary for this capability to be in metacity. Additionally, this removes the discrepancy between metacity's and compiz's handling of system bell events. There are several other difficulties in enabling the system bell: 1) Even if it is taken out of the blacklist, the pcspkr module may not load properly. Another modprobe may be necessary to get it loaded. See bug #398161. 2) Something in Gnome's startup does the equivalent of `xset b off`, so `xset b on` must be run on every login. (Note that bug #280767 keeps you from setting the bell volume with xset.) 3) A number of settings in gnome-terminal and gconf may keep the shell from sounding system bell events. Comments #28, #34, and #50 give more detailed summaries of the various problems. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/486154/+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
