Well, just make an strace -ff aplay somesound.wav | grep -i "alsa\|asound" and look what config files it is trying to open. What I don't understand is, why on this sound chip the root should has access if an user has the sound device open. I assume that happens by fluke, because artsd opens the sound device, but if it's not needed for some seconds, it releases the device... But that's only a wild guess and depends if you are using xmms over arts or alsa directly or oss or something else... But judging from the type of audio device which is on the intel 845 boards, then it's for sure that the device can only handle one open at a time. I use such a board at work, too. Greets, Daniel Zitat von Steve King <stevenking66@yahoo.co.uk>:
On Monday 28 June 2004 09:11, Daniel Eckl wrote:
I found this page: http://www.pseudorandom.co.uk/2004/debian/alsa/
And it worked on my SuSE 9.1 out of the box. You only need to create the /etc/asound.conf with the shown content and that's all. Forget the modules, they are alright on SuSE 9.1. Just use the asound.conf.
I have just the same situation as Bojan regarding availability of sound to root and to two ordinary users. I am running SuSE 9.0 and it was the same when I ran SuSE 7.3, so I have come to believe that this is just how it has to be.
I am running KDE 3.2.3.But again, it has been like this for KDE2, KDE 3.1, etc.
I tried adding /etc/asound.conf but it makes no difference. This is true for the version suggested by Daniel and for the version suggested by Victor. I am assuming (but only assuming) that my system is taking no notice of /etc/asound.conf at all.
Does anyone have a solution that works for SuSE 9.0?
I'd like to fix this if possible because my daughters keep leaving themselves logged on and I hardly ever get to hear my MP3s!
Steve Dundee, UK
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e