Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 17185 - System bell does not work in KDE with Alsa sbawe (emu8k) driver
Summary: System bell does not work in KDE with Alsa sbawe (emu8k) driver
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-10 00:27 UTC by Stuart W. Finlayson
Modified: 2003-04-28 06:57 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stuart W. Finlayson 2003-03-10 00:27:15 UTC
The system bell works in CLI and IceWM.  However, when in KDE the system bell 
does not work--all sounds sent to aplay are heard.  I am using the Alsa sbawe 
(emu8k) driver and have 'set bell-style audible' in my /etc/inputrc. 

Reproducible: Always
Steps to Reproduce:
1.  Have a machine with a Soundblaster 32/AWE and KDE installed 
2.  Open a terminal window in KDE, and issue 'echo -e "\a" 
3. 
Actual Results:  
Nothing 

Expected Results:  
A beep will be generated from the motherboard speaker. 

Portage 2.0.47-r8 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r2) 
================================================================= 
System uname: 2.4.20-gentoo-r1 i686 Pentium III (Coppermine) 
GENTOO_MIRRORS="ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo" 
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config 
/usr/kde/2/share/config /usr/kde/3/share/config 
/usr/X11R6/lib/X11/xkb:/usr/kde/3.1/share/config:/usr/share/config" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" 
PORTDIR="/usr/portage" 
DISTDIR="/usr/portage/distfiles" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR_OVERLAY="" 
USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg libg++ mikmod mmx mpeg 
ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gtkhtml alsa 
gdbm berkdb slang readline arts tetex bonobo svga java guile X sdl gpm tcpd pam 
libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl mozilla 
ethereal gtk2 innodb mysql odbc postgres" 
COMPILER="gcc3" 
CHOST="i686-pc-linux-gnu" 
CFLAGS="-O2 -mcpu=i686 -pipe" 
CXXFLAGS="-O2 -mcpu=i686 -pipe" 
ACCEPT_KEYWORDS="x86" 
MAKEOPTS="-j2" 
AUTOCLEAN="yes" 
SYNC="rsync://rsync.gentoo.org/gentoo-portage" 
FEATURES="sandbox ccache"
Comment 1 Gregorio Guidi (RETIRED) gentoo-dev 2003-03-10 06:30:26 UTC
Konsole (the Kde console) usually sends the beeps to the soundcard and not to the 
motherboard beeper, so to hear them you must have arts (the Kde sound system) up and 
running. 
For example, can you play music through Noautun (includede in kdemultimedia)? or simply 
play sounds doing 
# artsplay <somefile>.wav 
 
Comment 2 Stuart W. Finlayson 2003-03-10 13:19:32 UTC
artsd is up and running, and I can play sound with 'artsplay 
<somefile>.wav'.  But, for some reason in Konsole the alert is never sent 
anywhere.  So, echo -e "\a" yields no more than an empty line and turn the 
icon on the shell "toggle button" to a bell. 
 
I have also tried setting the the "System Bell" in "Control Center" to "Use 
system bell instead of system notification" and this did not work either. 
 
Is there any additional information that I have not provided that could 
prove useful in figuring out what is wrong? 
Comment 3 Paul de Vrieze (RETIRED) gentoo-dev 2003-04-24 14:37:08 UTC
Does your pc speaker work at all? To test, go to a virtual console, login and just type the backspace key some times.
Comment 4 Stuart W. Finlayson 2003-04-24 18:18:48 UTC
I have solved the problem the "Use System Bell" option was checked in  
"Control Center" > "Regional & Accessibility" > "Accessibility".  I unchecked  
it, clicked "Apply", then checked it, clicked "Apply", and now it works...  I  
haven't a clue as to why unchecking and re-checking it worked, but there  
you have it. 
 
Although I've managed to get this working, I haven't closed this bug, as 
there is an underlying issue--in that the configuration being shown in this 
instance was not the configuration being used. 
Comment 5 Michele Balistreri (RETIRED) gentoo-dev 2003-04-28 06:57:15 UTC
closing as fixed