Hi! This is the expected behavior. Your Miro instance is configured to use the xine renderer which was removed in Miro 3.0. Thus, when Miro 3.0 (and later) start up, they try to load the xine renderer, that kicks up an ImportError, Miro logs that error to the log file, and then loads the GStreamer renderer.
So, to summarize, this is just a message logged to the file so that the log file has a correct account of what happened when Miro loaded. Other than that, it has no effect on you. Thank you for taking the time to point it out, though. I do agree the logged error message sounds fatal. I'll toss around how to make it less fatal sounding in a future version. /will -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
