[ale] aplay runs amok
Michael D. Hirsch
mhirsch at nubridges.com
Wed Feb 25 16:16:36 EST 2004
On Wednesday 25 February 2004 01:26 pm, Jeff Hubbs wrote:
> Geoffrey -
> The line in the ps alx output in question is
> 0 501 17870 2227 16 0 2440 936 - R ? 15:24
> /usr/bin/aplay /usr/share/sounds/KDE_Beep_Beep.wav
I believe that is the default sound in KDE for "Something Special Happened in
the Program"--i.e. a system beep. aplay is the alsa player command.
Does aplay work when you run it command line? Is alsa installed and working?
You might try going into the KDE Control Center, find the "System
Notification" section (for me it is in "Sound & Multimedia") and change the
way sounds are played. Try using a different player from aplay--especially
if you aren't using alsa. KDE usually uses artsd, so I would have expected
> - Jeff
> On Wed, 2004-02-25 at 10:18, Geoffrey wrote:
> > Jeff Hubbs wrote:
> > > On Wed, 2004-02-25 at 06:12, Geoffrey wrote:
> > >>Jeff Hubbs wrote:
> > >>>On my Mandrake 9.1/KDE machine, aplay seems to take the CPU to 100%
> > >>> even though it's not doing anything. I can kill it but it restarts
> > >>> after a few minutes. I can't tell what I might be doing to make this
> > >>> happen, but nothing less than a restart of KDE seems to be required
> > >>> to make it stop and stay stopped. Anyone know what causes this?
> > >>
> > >>I wasn't aware of the toy, but I just fired it up with a wav file, no
> > >>problems. Are you saying it's just running without being invoked?
> > >>
> > >>I don't see any kind of daemon option, I don't know why it would be
> > >>running without being invoked.
> > >
> > > Right. Something's invoking it and it freaks.
> > Can you run ps and trace the ownership via pid to the process that is
> > invoking it?
> > 'ps axl' will provide PPID.
> Ale mailing list
> Ale at ale.org
More information about the Ale