Package: miro
Version: 3.0-1
Severity: minor
Miro runs fine, but after starting, I get an exception message:
set_renderer: couldn't load xinerenderer: Traceback (most recent call last):
File /usr/lib/pymodules/python2.5/miro/plat/renderers/__init__.py, line 53,
in set_renderer
pkg =
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
On 2010-04-11 13:48, will kahn-greene wrote:
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.
Something like did not find x-renderer, using y-renderer instead
3 matches
Mail list logo