suse9.3pro 64bit..
haven't yet found out why i can't get sound to work as a user - when it's ok as root..
i'm sure it's a simple setting which i have not yet discovered..

how is that done guys..?

krgds

I had similar problem with my Debian.
Problem was permission of sound device file (/dev/***). I do not remember what it was.

chmod 666 /dev/dsp?

i'm not quite sure how to interpret your reply equinox..?
do i understand you correct that i need to change permission for the file specified..? i checked if the file is where you noted - but when looking at permissions in that one - it says permissions cannot be set - it a link..?

krgds

Paste the output of this command for me:

all right..

i got your hint - i suspect that with this output - you wanted to see which of the dsp files is the active one..?

i opened the dsp0 - and in permissions i checked rwx for group - which belongs to the audio group..

was this what you were aiming at..?

one thing that baffles me is: shouldn't it be possible to arrange this through yast or control-panel..?
and why isn't sound automatically accessible to users during install - is there some security item involved..?

ohh - and btw - sound works fine now - for users..

I've never thought about that. If you find out, please post here.

will do..

Are you in the audio group?

Read these: http://kreiger.linuxgods.com/kiki/?l...nd-permissions and http://www.linuxquestions.org/questi...?postid=241216

yes - because i could not get the sound to work being a member of users - i selected to be member of the audio group - in order to try and get the sound - but at no avail..

now - i have just changed myself back into the users group - deselected audio - so now there is only ticks in users, dialup and video..which is the default setting..i guess..?

..and there is no sound as user..

I assume that I think that I suppose that I guess that

because sound is connected to speaker which exists physically (for some reason, this has to exist at one place and usually does not move around)

and that "users" can connect to penguin box electronically through network which means user can be anywhere,

so that to avoid non-existing user to play MP3 file at your speaker,
/dev/dsp is NOT other-writable. (If I have an account on your comp, I can play music at your speaker. For unknown reason, I cannot appreciate. Furthermore, you may not like.

therefore, smart penguin did not set permission for others. Only users, who can exist near speaker belongs to "audio" group.

When two speaker systems are connected in different place, two device file and two different groups.

I feel I am right. I am positive if I am correct.

yezzz - you certainly have a valid point there - makes sence..

howdy