This sounds straight out of Windows, so I thought I'd see if anyone else has noticed behavior along these lines.

I just installed Suse 9.3 on my athlong 64 system. I have an HP 5550 usb printer. Suse emasculates xine so it can't play anything. I followed Mad Penguins Suse 9.2 advice to fix this, although I did not use apt to install libxine, because apt failed to install the codec. After I had Xine up and running, and able to play some wmv files, my daughter reported that she couldn't print. Sure enough, I couldn't either. I know the printer worked before, because I printed out the Mad Penguin directions.

So, I removed my printer and reconfigured it using Yast. Now I can print, but Xine is funky. It will play, but an mov3 trailer that my daughter downloaded had no sound, I received a "not supported codec" message, and I got the Suse error message. (Along the lines of "due to potential copyright violations, we emasculated Xine.") My wmv files play, but are really funky, and also diplay the messages.

Anybody else have similar problems? I also post this in the Suse forum, in case it is a Suse problem.

i can't imagine what that is -- i mean xine and cups have absolutely nothing to do with one another
run
xine-check
and show us what it says

I mouthed similar sentiments myself, foo_bar_foo, but less PG. I can only imagine that they share some header file, but I think if someone had asked me to pick two applications with nothing in common, those are the two I would pick.

I'll run xine-check tomorrow. (I'm not likely to get to use my PC until then.)