In GUTSY, unchecking Enable System Beep not completely working

Bug #162719 reported by Ben on 2007-11-14
4
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned

Bug Description

Fresh install of Gutsy on a Dell Latitude D820. Brand new, no other software installed. Fresh out of box.

Navigate 'System' > 'Preferences' > 'Sound'
Click the 'System Beep' tab
Uncheck 'Enable system beep'
Click 'Close' to save the settings
Restart the computer

PROBLEM:
At the logon screen, press 'Backspace' when the Username field is empty = *BEEP*
In a terminal, type 'sudo poweroff' and press enter = *BEEP*

I'm sure there are other places that the system beeps despite the aforementioned checkbox being unchecked and the system volume being muted. This is a regression from Feisty. I have identical Feisty and Gutsy builds on identical HDDs on the same laptop. Feisty does not produce this problem. Gutsy does produce this problem.

Yes, I am aware of the modprobe fix (below) - but isn't the purpose of Ubuntu to become more "user-friendly"... not less user friendly? If so, please don't offer that as the resolution. I would think that this feature in Feisty and Gutsy would work the same.

Thanks for all the hard work!

Ugly manual procedure not fit for Ubuntu:
========================================================================
========================================================================
gedit /etc/modprobe.d/blacklist

And then add:

#silly speaker beep
blacklist pcspkr

Save your file and the speaker beep will be gone when you reboot.
========================================================================
========================================================================

Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers