Under preferences when u choose alsasound driver and config...it hard locks and cannot be killed. this was fixed in an earlier alsa....Don't know if it was a problem with alsa-xmms package, xmms itself, or the alsa that is built into the newest mjc-sources...thanks
Does -r11 work with mjc-sources-r1 and alsa?
Must be a bug with how alsa is applied in the mjc -r1 kernel. Seems to affect -r11 also...
Brad, is the new alsa-xmms working for you?
I have just had to compile every thing pertaining to alsa in the kernel as modules....nothing compiled in...no hard locks anymore, but under the configure it doesn't show my sound module...maybe something to do with the ebuild, or maybe the kernel alsa places the modules somewhere different than the alsa ebuild....either way...I'm not gonna worry about it anymore..I have alot more important bugs that seem to not have a fix..ie..the mozilla-r3 ebuild seems to have problems on gcc3 and 2.95.3 THXS
I'm not sure if this is related, but on my build completed ~four days ago (Gentoo 1.2 and KDE 3.02), XMMS works fine if I load .mp3s from it's "add>dir" button. However, if I try to drag and drop files from a local directory, or a network directory, XMMS hangs for about a minute, and then begins to play the file. I *can* kill XMMS during the hang. XMMS also displays identical one minute or so hanging behavior when I click on a SHOUTcast stream in mozilla1.0 (after setting the mime type XMMS in mozilla preferences). For now my workaround has been to switch to noatun -- but I prefer XMMS by far and hope that it starts working correctly someday. As a side note, under Mandrake8.2 on my other box, the above described hanging behavior does not occur. My Gentoo box specs: Gateway OEM MSI 6330 motherboard Athlon 950 128 megs 10gig Creative branded AudioPCI w/1373 printed on chip (using 1370 driver?) Some kind of random OEM Gforce2/32meg. ALSA? ((I'm pretty sure I installed ALSA. Was there some other way I might have done it?) I'll check if someone says this info is important. I can't get to the Gentoo box right now.)
Oh heck. Maybe I didn't install ALSA. I may have just added ES1370 support directly into the kernel when compiling? I'll check this tomorrow.
OK, the problem is fixed. Here is what I did: I installed arts, which had not been installed. HOWEVER, under xmms options>preferences>output plugin, I leave it as OSS. XMMS works perfectly now. I can drag an mp3 file a disk mounted across the network, or click a streaming link through shoutcast (with the proper mozilla helper settings of course) and it starts playing immediately.
I mean I installed the arts xmms plugin.
So look here is a suggestion: If KDE3 is installed, then the xmms arts plugin should be a dependancy for an xmms install.
Dan, what is your thoughts on the last comment?
Taking an action based on whether something is installed is obviously against rules. We could make xmms depend on xmms-arts if the arts use flag is enabled; that sounds reasonable. I don't use xmms myself except when noatun breaks in the kde cvs, so I don't have a formed opinion :-) But I see no raeson not to do it if you think it appropriate. But why did you assign it to me? And do you want me to try to understand the other comments (all but the last one)? I only skimmed them.
OK, please do this yourself if you want to. It's your ebuild & responsibility :-) You'll probably also want to consider adding a dep on xmms-alsa if alsa is in use, etc etc.
Adding dependencies to plugins in the xmms ebuild won't work becuse it creates circular dependencies.
