wow, talk about annoying...
lets start with this: in /etc/rc.d i have a script called rc.artsd (which is obvious what it does). this script runs correctly when i run kde. but in fluxbox, i have to keep starting it manually. could it be only an issue of permissions?? if so, why is that not happening in kde.

second problem: when i finally start artsd manually, skype will tell me that theres another program using /dev/dsp1, which is bogus. when i first ran flux, i was able to run arts and talk in skype with no problems at all. it seems to be very strange because last night, after about 30 mins of just sitting here, the issue of me being able to run artsd and talk in skype suddenly became non-existant...
i really have a tough time trying to pinpoint where the problem might be. but any help here would be greatly appreciated.

allow me to rephrase that first part. i just recently created that /etc/rc.d/artsd script due to that fact that arts wasnt starting in flux as it does in kde. so, that means that kde will run artsd at startup with no script (that i wrote) telling it to do so.

thanks for your time fellas.

Just because an executable script exists in /etc/rc.d does not mean it will be automatically run. It has to be referenced by some other script. That's the way all the scripts in /etc/rc.d work.

My advice would to be to add a Slackware style call to the script in /etc/rc.d/rc.local. Like so:

Then, rc.M will call rc.local which will call rc.artsd. Make rc.local or rc.artsd -x to disable them.

About the second problem... Artsd will release /dev/dsp after a certain amount of sound inactivity. Default is 60 seconds I believe. You have these options: make skype use artsd, start skype with artswrapper, or disable artsd before starting skype.

--Shade

cheers Shade. as far as my skype problem goes, 'artsdsp skype' works great as ive just found out a few minutes ago. i guess it basically redirects all its sound to arts, therefore im able to run mp3s in xmms (given that it uses arts) and skype at the same time .

as for the first part about the scripts in your response... i must ask now. before i wrote that /etc/rc.d/rc.artsd script, kde was starting artsd right at startup. what was it using to do that, and how can i get flux to do the same without having to write a script. or will i have to write one now??
if thats the case, then can we explain why flux started artsd yesterday morning for me? there was no script at that time telling it to do so. unless there is another script somewhere else??

thanks for your response though, it does help alot

A application could also start arts.
KDE always starts it by default unless you tell it not to (there's an option to do this), it just runs it, no science there.
As far as I remember Fluxbox has a file where you can put things to be started when it does, try putting arts there.

thanks for your help guys, ill let you know in a while how i turned out . im so happy i found out about that 'artsdsp' command, now i will never have sound issues.. EVERYTHING arts weeee! -_-

hehe, thanks again

Alright fellas. getting artsd to startup isnt an issue at all now. however the problem of getting skype to run correctly when artsd is running is a huge problem. im not sure where to start on getting a fix for this. but i do know for a fact that this problem does not exist in kde. so i guess i could figure out what kde is doing that my fluxbox isnt doing, then go from there. however, ive tried that before and i received no love.

the error i get is basically telling me that /dev/dsp-1 is already in use or is busy, is there a way to find out what application is using /dev/dsp1? i tried ps -aux | grep /dev/dsp, and again, received no love.

Note: running artsdsp (application here) works fine for skype as far as receiving sound, but for talking (using the mic) that sound will not go through.

if anyone has any idea on how to go about correcting this. please feel free to post i hate foolish liddew prollems like these.

try :
lsof | grep /dev/dsp

ofcourse theres nothing using it. why in the world would it be so easy?! on neither command did i receive any love. something so simple is becoming tougher than i thought it would be.

You need to start artsd in full-duplex mode. KDE settings probably already have that option enabled, but starting artsd from command line probably does not.

man artsd ?

--Shade

wow. yeah, i thought the same... artsd -d = full duplex, and its the same problem as before. more or less, i would just like to know what the hell is using /dev/dsp 0_o . the lsof command didnt help. maybe its just lying to me?

whats kde doing that flux isnt?

arts wasnt auto suspending properlly, what confused me is that kde was auto suspending automatically (some setting in the control panel). i cant believe i forgot about that. anyway, thanks for the help guys. "artsd -ds 1" helped alot.

im an idiot some days, and often forget the small stuff, forgive me.