On Wed, 10 Oct 2001, Chris Rankin wrote:
> I'm sure; but I haven't installed a Desktop Environment yet. (It's on
> my to-do list.)
>
> There *really*, *really* isn't anything using the audio device.
You might check it with the fuser utility:
ossdevs="/dev/admmidi? /dev/adsp? /dev/amidi? /dev/au
I'm sure; but I haven't installed a Desktop Environment yet. (It's on
my to-do list.)
There *really*, *really* isn't anything using the audio device.
Chris
> On Wed, 10 Oct 2001, James Courtier-Dutton wrote:
> >I think you will find that X likes to play the odd wave file as you click on
> >the
On Wed, 10 Oct 2001, James Courtier-Dutton wrote:
>I think you will find that X likes to play the odd wave file as you click on
>the wrong thing etc.
>It could be X which is using the audio device.
Well, X does not use the audio device. The Dreaded Desktop Environment
(KDE or GNOME or whatever) m
1 03:27
> To: [EMAIL PROTECTED]
> Subject: [Alsa-devel] Update: locked modules with no users...
>
>
> Hi,
>
> A little further study has revealed two additional facts here:
> 1) this happens with xine,
> 2) restarting X (logging out and logging back in again) releases
> the
Hi,
A little further study has revealed two additional facts here:
1) this happens with xine,
2) restarting X (logging out and logging back in again) releases the locks .
This would imply that somehow the ALSA devices are staying open, even
though the user-space processes have (apparently) gone
