Bug 302929 - Systemsettings bell: should warn user if the module (pcspkr/snd-pcsp) isn't loaded
Summary: Systemsettings bell: should warn user if the module (pcspkr/snd-pcsp) isn't l...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_bell (show other bugs)
Version: 4.8.80 (beta1)
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-02 22:14 UTC by Richard Neill
Modified: 2015-01-21 20:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Neill 2012-07-02 22:14:39 UTC
The system bell config module has a helpful test button, which doesn't always do anything. Usually this is because a well-meaning distro has blacklisted the beep module.
May I suggest that the kcm_bell module should check whether the module is loaded, and if not, warn the user. 

For example:
    grep -Eq '^(pcspkr|snd_pcsp)'  /proc/modules  || echo $msg
where msg might be:

The system bell (PC Speaker) is a buzzer mounted on the motherboard, or a small speaker inside the case of the PC, which can produce beeps. For laptops, this is usually wired through the main speakers. Your pcspkr is currently disabled, because the kernel module is not loaded. To load it, modprobe pcspkr.
(To ensure it loads at boot time, check it is not blacklisted in /etc/modprobe.d )

Reproducible: Always

Steps to Reproduce:
1. Install a distro  (virtually any mainstream one) with the default settings.
2.Go to SystemSettings -> System Bell. Click test.
3. Hear no beep.
Comment 1 Graeme Hewson 2013-11-07 11:58:12 UTC
I agree (after wasting time tracking down the lack of sound).
Comment 2 David Edmundson 2015-01-21 20:27:52 UTC
This has been removed in Plasma 5