Hi Jerry, That elisa depends on elisa-plugins-good *and* elisa-plugins-bad is a known issue. Bad essentially mean that the quality of the code and the associated documentation are not high enough to go into good, but it does not mean that the plugins themselves are bad or work badly. In fact the normal lifecycle of a plugin is to begin in bad, and then when it's mature enough, stable and well documented, move to -good.
Regards, Olivier Jerry Yu wrote: > Hi, > > If I only installed elisa and elisa-plugins-good, elisa can't be started > up. Elisa I tried is the latest 0.5.15, and my system is Solaris. > > > Attached is a traceback file and below is the warning messages: > bash-3.2$ elisa > > (elisa:18111): Gdk-CRITICAL **: file gdkdisplay-x11.c: line 539: > assertion `GDK_IS_DISPLAY (display)' failed > > (elisa:18111): Gdk-CRITICAL **: file gdkscreen-x11.c: line 133: > assertion `GDK_IS_SCREEN (screen)' failed > > (elisa:18111): Gdk-CRITICAL **: file gdkdisplay-x11.c: line 539: > assertion `GDK_IS_DISPLAY (display)' failed > > (elisa:18111): Gdk-CRITICAL **: file gdkscreen-x11.c: line 151: > assertion `GDK_IS_SCREEN (screen)' failed > > (elisa:18111): Gdk-CRITICAL **: file gdkdisplay-x11.c: line 539: > assertion `GDK_IS_DISPLAY (display)' failed > > (elisa:18111): Gdk-CRITICAL **: file gdkscreen-x11.c: line 133: > assertion `GDK_IS_SCREEN (screen)' failed > > (elisa:18111): Gdk-CRITICAL **: file gdkdisplay-x11.c: line 539: > assertion `GDK_IS_DISPLAY (display)' failed > > (elisa:18111): Gdk-CRITICAL **: file gdkscreen-x11.c: line 151: > assertion `GDK_IS_SCREEN (screen)' failed > WARN MainThread plugin_registry Oct 21 18:16:52 plugin > conflict vobject 0.7.1 (elisa/core/plugin_registry.py:224) > WARN MainThread service_manager Oct 21 18:16:52 > Creating > elisa.plugins.gnome.gnome_screensaver_service:GnomeScreensaverService > failed. A full traceback can be found at /tmp/elisa_a1n0GA.txt > (elisa/core/manager.py:82) > WARN MainThread interface_controller Oct 21 18:16:52 > creating frontend frontend1 failed. A full traceback can be found at > [Failure instance: Traceback: exceptions.AttributeError: 'module' object > has no attribute 'pigment' > /usr/lib/python2.4/site-packages/twisted/internet/gtk2reactor.py:226:simulate > > /usr/lib/python2.4/site-packages/twisted/internet/base.py:705:runUntilCurrent > > /usr/lib/python2.4/site-packages/twisted/internet/task.py:251:_tick > /usr/lib/python2.4/site-packages/elisa/core/interface_controller.py:104:load_frontends_iter > > --- <exception caught here> --- > /usr/lib/python2.4/site-packages/elisa/core/plugin_registry.py:410:create_component > > /usr/lib/python2.4/site-packages/twisted/python/reflect.py:432:namedAny > ] (elisa/core/interface_controller.py:87) > WARN MainThread interface_controller Oct 21 18:16:52 Could > not load any frontend (elisa/core/interface_controller.py:123) > > > And if also installed elisa-plugins-bad, elisa works well. As I think, > elisa should not depends on -plugins-bad. And it should works well > without -plugins-bad installed. > > Thanks, > Jerry
