As a followup to provide more information, I've found that the "aplay"
process shows up whenever I backspace enough to go past the beginning of
the line that I'm on, in one of those Konsole shell windows that KDE
provides you with. When I back up enough, an icon at the bottom of the
window changes to a bell icon, but no sound is ever played. Running Top in
another window shows that aplay shows up, consuming a considerable amount
of CPU. It never stops until you kill it (kill -9). And as long as it's
running, it's tieing up the audio device, so nothing else that wants to
play sounds can do so.
Argh. I don't think I even *had* alsa installed in my 9.0 setup. When I
tried to uninstall the three packages related to alsa (to see if it would
help), I got a message showing how many things depended on one of the
libraries - half of the KDE libraries would have to be removed. Ugh. So
it looks like I'm stuck with it.
So the question now becomes: Is there a place in KDE where I can define
that I want it to use "play" - not "aplay" - for producing sounds in
Konsole (and anywhere else that KDE might want to use aplay). I've just
"cheated" by renaming /usr/bin/aplay to something else, and made a link to
/usr/bin/play called aplay (which seems to work), but I'd prefer to do
something configuration-wise, if possible. :-)
Regardless, replacing aplay with play seems to have done it for the time
being. :-)
--Dave
David Guntner grabbed a keyboard and wrote:
>
> Mike grabbed a keyboard and wrote:
> >
> > On Friday 28 March 2003 12:56 am, Jack Coates wrote:
> > > On Thu, 2003-03-27 at 21:27, David Guntner wrote:
> > > > I've done a clean install of 9.1 on the machine which used to run 9.0.
> > > > In 9.0, I had sound. In 9.1, only silence. No hardware has changed, so
> > > > I'm kind-of hard pressed to figure out why I can't get any sound out of
> > > > 9.1.
> > >
> > > if you run alsamixergui, are all the levels set to zero?
> >
> > When I installed 9.1 the sound was muted.I had to use one of the mixers to
> > turn it up.It can be a little disconcerting until you figure it out.
>
> To say the least. :-) Someone commented that taking the "above" statement
> ouf ot the modules.conf file solved the problem for him (when I posted the
> message showing what is in that file.
>
> I tried that, and low-and-behold, when I logged in to KDE, I got the little
> welcome "starting up" sound. I thought that it was fixed. But after that,
> nothing but silence. Even when I logged out and logged back in - nothing.
>
> After logging out again from the main console, I ssh'ed in from another
> computer, and I just happened to run "top." Low and behold, it showed a
> process running with my user ID, called aplay, which was sucking up a
> considerable amount of CPU. When I killed that process, all of a sudden I
> heard the KDE greeting sound coming out of the speakers again (apparently
> queued up from my previous login at the console).
>
> So it looks like when I log in, it's using aplay to play the greeting
> sound. Unfortunately, aplay just gets stuck at that point never exits,
> which leaves the sound device busy.
>
> Anyone have any ideas what's causing that?
--
David Guntner GEnie: Just say NO!
http://www.akaMail.com/pgpkey/davidg or key server
for PGP Public key
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
