On Sat, 16 Aug 2003, Alec Berryman wrote: > When getting something abnormal like this (XMMS ought to be able to do > XMMS), the first thing I'd try would be run it in a console. Does it > give any signifigant output? Next, do a quick recompile with more > conservative options. Try -O2 instead of -O3, take out the "fast" math, > and all that fun stuff. I bet that fixes it, but if it doesn't, and > you're feeling adventurous, get 'strace' and run 'strace xmms file.wav' > and see if anything interesting comes up. > > I bet the recompile will do it, but there's an endless amount of fun to > be had. > It works now, with no recompiling! Go figure... The documentation of xmms is better than average, but still it is difficult to get the big picture. I think I can guess (more or less) what happened: I use KDE, and the aRts server is started at login and suspended if inactive for 60 seconds. Since I tried to start artsd from the command line (without -s option), the server remained active indefinitelly. It seems that xmms cannot interact with the aRts server (I suppose that is what the xmms-arts plugin is for, but it is masked), whence the trouble (it shouldn't just freeze, though...). I don't understand what reset the normal state (I opened the KDE sound control panel, but could that be enough to restart the aRts server with the 60 sec. option?) Also, I'm guessing that xmms has a built-in server (or something like that) that works when nothing else holds the hardware yet... Could this be wright? Regards,
-- Jorge Almeida -- [EMAIL PROTECTED] mailing list
