Feature changed by: Damien Radtke (kog13) Feature #312765, revision 2 Title: Blacklist the pcspkr module by default openSUSE.org: Unconfirmed Priority Requester: Important Requested by: Damien Radtke (kog13) Partner organization: openSUSE.org Description: The pcspkr module is used to control the computer's internal speaker, which is very rarely used on the desktop. It isn't strong enough to serve as a passable replacement for real sound devices, and it hurts - the user experience more than it helps. I have openSUSE installed on - two computers, my laptop and desktop (11.3 on the laptop, 11.4 - /Tumbleweed on the desktop), and on both computers I've had to disable - the PC speaker because otherwise it would beep very loudly every time I - would shut down or restart. It seems to me that this behavior was - intended more for server than desktop use. + the user experience more than it helps. + I have openSUSE installed on two computers, my laptop and desktop (11.3 + on the laptop, 11.4/Tumbleweed on the desktop), and on both computers + I've had to disable the PC speaker because otherwise it would beep very + loudly every time I would shut down or restart. It seems to me that + this behavior was intended more for server than desktop use. Having to spend the time to learn what the speaker is, what drives it, and how to disable it is obviously not a great experience. I think it would be better for end users to have this module disabled by default, and if any seasoned admins really want it back, they know how to re- enable it. -- openSUSE Feature: https://features.opensuse.org/312765

Feature changed by: Per Jessen (pjessen) Feature #312765, revision 4 Title: Blacklist the pcspkr module by default openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Damien Radtke (kog13) Partner organization: openSUSE.org Description: The pcspkr module is used to control the computer's internal speaker, which is very rarely used on the desktop. It isn't strong enough to serve as a passable replacement for real sound devices, and it hurts the user experience more than it helps. I have openSUSE installed on two computers, my laptop and desktop (11.3 on the laptop, 11.4/Tumbleweed on the desktop), and on both computers I've had to disable the PC speaker because otherwise it would beep very loudly every time I would shut down or restart. It seems to me that this behavior was intended more for server than desktop use. Having to spend the time to learn what the speaker is, what drives it, and how to disable it is obviously not a great experience. I think it would be better for end users to have this module disabled by default, and if any seasoned admins really want it back, they know how to re- enable it. + Discussion: + #1: Per Jessen (pjessen) (2011-08-24 21:04:21) + The pcspkr module should not be getting in the way of a proper + soundcard/-chip (when present). No regular user on regular hardware + should have to disable it. Have you reported this as a bug? -- openSUSE Feature: https://features.opensuse.org/312765

Feature changed by: Per Jessen (pjessen) Feature #312765, revision 6 Title: Blacklist the pcspkr module by default openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Damien Radtke (kog13) Partner organization: openSUSE.org Description: The pcspkr module is used to control the computer's internal speaker, which is very rarely used on the desktop. It isn't strong enough to serve as a passable replacement for real sound devices, and it hurts the user experience more than it helps. I have openSUSE installed on two computers, my laptop and desktop (11.3 on the laptop, 11.4/Tumbleweed on the desktop), and on both computers I've had to disable the PC speaker because otherwise it would beep very loudly every time I would shut down or restart. It seems to me that this behavior was intended more for server than desktop use. Having to spend the time to learn what the speaker is, what drives it, and how to disable it is obviously not a great experience. I think it would be better for end users to have this module disabled by default, and if any seasoned admins really want it back, they know how to re- enable it. Discussion: #1: Per Jessen (pjessen) (2011-08-24 21:04:21) The pcspkr module should not be getting in the way of a proper soundcard/-chip (when present). No regular user on regular hardware should have to disable it. Have you reported this as a bug? #2: Damien Radtke (kog13) (2011-08-25 21:19:51) (reply to #1) Yes I have, and it got nowhere. https://bugzilla.novell.com/show_bug.cgi?id=698148 + #3: Per Jessen (pjessen) (2011-08-26 10:10:18) (reply to #2) + The report has been open for less than three months - have patience, + bugs can take a lot longer to fix. -- openSUSE Feature: https://features.opensuse.org/312765

Feature changed by: Damien Radtke (kog13) Feature #312765, revision 8 Title: Blacklist the pcspkr module by default openSUSE Distribution: Rejected by Andreas Jaeger (a_jaeger) reject reason: Let's discuss in bugzilla. Priority Requester: Important Requested by: Damien Radtke (kog13) Partner organization: openSUSE.org Description: The pcspkr module is used to control the computer's internal speaker, which is very rarely used on the desktop. It isn't strong enough to serve as a passable replacement for real sound devices, and it hurts the user experience more than it helps. I have openSUSE installed on two computers, my laptop and desktop (11.3 on the laptop, 11.4/Tumbleweed on the desktop), and on both computers I've had to disable the PC speaker because otherwise it would beep very loudly every time I would shut down or restart. It seems to me that this behavior was intended more for server than desktop use. Having to spend the time to learn what the speaker is, what drives it, and how to disable it is obviously not a great experience. I think it would be better for end users to have this module disabled by default, and if any seasoned admins really want it back, they know how to re- enable it. Discussion: #1: Per Jessen (pjessen) (2011-08-24 21:04:21) The pcspkr module should not be getting in the way of a proper soundcard/-chip (when present). No regular user on regular hardware should have to disable it. Have you reported this as a bug? #2: Damien Radtke (kog13) (2011-08-25 21:19:51) (reply to #1) Yes I have, and it got nowhere. https://bugzilla.novell.com/show_bug.cgi?id=698148 #3: Per Jessen (pjessen) (2011-08-26 10:10:18) (reply to #2) The report has been open for less than three months - have patience, bugs can take a lot longer to fix. + #6: Damien Radtke (kog13) (2011-08-29 20:55:52) (reply to #3) + I don't believe that a fix is incoming. Nobody else seems to have this + problem, so I don't know what to do. #4: Andreas Jaeger (a_jaeger) (2011-08-28 10:25:32) (reply to #2) That bug is waiting for your comments - it's in state NEEDINFO to you. + #5: Damien Radtke (kog13) (2011-08-29 20:51:26) (reply to #4) + Everything I tried didn't work. One of the last comments is "If it's + the culprit, I see no option to disable it, so the workaround is to + either disable forcibly by removing pcspkr driver or invoking 'setterm - + b0' to disable the beep." + There's nothing else I can do short of hacking /sbin/shutdown to remove + the beep. -- openSUSE Feature: https://features.opensuse.org/312765

Feature changed by: Per Jessen (pjessen) Feature #312765, revision 10 Title: Blacklist the pcspkr module by default openSUSE Distribution: Rejected by Andreas Jaeger (a_jaeger) reject reason: Let's discuss in bugzilla. Priority Requester: Important Requested by: Damien Radtke (kog13) Partner organization: openSUSE.org Description: The pcspkr module is used to control the computer's internal speaker, which is very rarely used on the desktop. It isn't strong enough to serve as a passable replacement for real sound devices, and it hurts the user experience more than it helps. I have openSUSE installed on two computers, my laptop and desktop (11.3 on the laptop, 11.4/Tumbleweed on the desktop), and on both computers I've had to disable the PC speaker because otherwise it would beep very loudly every time I would shut down or restart. It seems to me that this behavior was intended more for server than desktop use. Having to spend the time to learn what the speaker is, what drives it, and how to disable it is obviously not a great experience. I think it would be better for end users to have this module disabled by default, and if any seasoned admins really want it back, they know how to re- enable it. Discussion: #1: Per Jessen (pjessen) (2011-08-24 21:04:21) The pcspkr module should not be getting in the way of a proper soundcard/-chip (when present). No regular user on regular hardware should have to disable it. Have you reported this as a bug? #2: Damien Radtke (kog13) (2011-08-25 21:19:51) (reply to #1) Yes I have, and it got nowhere. https://bugzilla.novell.com/show_bug.cgi?id=698148 #3: Per Jessen (pjessen) (2011-08-26 10:10:18) (reply to #2) The report has been open for less than three months - have patience, bugs can take a lot longer to fix. #6: Damien Radtke (kog13) (2011-08-29 20:55:52) (reply to #3) I don't believe that a fix is incoming. Nobody else seems to have this problem, so I don't know what to do. #4: Andreas Jaeger (a_jaeger) (2011-08-28 10:25:32) (reply to #2) That bug is waiting for your comments - it's in state NEEDINFO to you. #5: Damien Radtke (kog13) (2011-08-29 20:51:26) (reply to #4) Everything I tried didn't work. One of the last comments is "If it's the culprit, I see no option to disable it, so the workaround is to either disable forcibly by removing pcspkr driver or invoking 'setterm - b0' to disable the beep." There's nothing else I can do short of hacking /sbin/shutdown to remove the beep. #7: Tim Edwards (tk83) (2011-08-29 23:22:16) I had a similar problem on a Dell Latitude laptop - every time I used the backspace key in the terminal (konsole) and it got back to the start of the line it'd emit this horrible beep from the speaker, it really annoyed me and the other people in the office. Unfortunately I can't help with fixing it anymore as I've moved on to another job. I reckon the problem is a real bug, but it's hardware dependant - my 2 Acer laptops at home don't have this problem despite having the same Opensuse configuration. + #8: Per Jessen (pjessen) (2011-08-30 13:34:23) (reply to #7) + I have that behaviour too - on my openSUSE 10.3 workstation - except it + beeps through the attached speakers, i.e. through the soundcard. This + is expected of course. -- openSUSE Feature: https://features.opensuse.org/312765