[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#540831: marked as done (alsa-base: Please blacklist pcspkr by default)

Your message dated Tue, 4 Jun 2013 19:43:45 +0200
with message-id <20130604174345.GA4567@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #540831,
regarding alsa-base: Please blacklist pcspkr by default
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
540831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540831
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: alsa-base
Version: 1.0.20+dfsg-1
Severity: normal

Please consider blacklisting pcspkr by default.

"How do I make my system stop beeping" represents a fairly common
question.  A quick search for "pcspkr" primarily gives results from
people wanting to stop it from loading.  The PC speaker makes a loud and
annoying beep on many systems, and not all of those provide a way to
mute it via the soundcard.  Many applications end up triggering the PC
speaker when they ring the system bell, notably terminal emulators and
the console.

Adding "blacklist pcspkr" to a file in /etc/modprobe.d/ represents one
of the few configuration changes I still have to make to every Debian
system I install.

(Previously reported against udev since it owns
/etc/modprobe.d/blacklist.conf.  Marco d'Itri suggested that alsa seemed
like a better package to handle this.  If you believe this bug should
not get fixed in alsa-base, I'd appreciate any suggestions about what
package should handle this issue.)

Thanks,
Josh Triplett

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: