Your message dated Wed, 19 Mar 2008 10:54:23 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#471640: solved
has caused the Debian Bug report #471640,
regarding fails to start: component base:elisa_activity not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
471640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471640
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: elisa
Version: 0.3.5-1
Severity: important
Since the latest upgrade, elisa fails to start, see below traceback:
ComponentNotFound
Python 2.4.5: /usr/bin/python
Wed Mar 19 09:52:15 2008
A problem occurred in a Python script. Here is the sequence of
function calls leading up to the error, in the order they occurred.
/usr/lib/python2.4/site-packages/elisa/core/interface_controller.py in
initialize(self=<elisa.core.interface_controller.InterfaceController
object>)
141 for frontend_path in frontend_paths:
142 try:
143 self._create_frontend(frontend_path)
144 except Exception, exc:
145 path = application.log_traceback()
self = <elisa.core.interface_controller.InterfaceController object>
self._create_frontend = <bound method
InterfaceController._create_fronte...interface_controller.InterfaceController
object>>
frontend_path = 'frontend1'
/usr/lib/python2.4/site-packages/elisa/core/interface_controller.py in
initialize(self=<elisa.core.interface_controller.InterfaceController
object>)
129 for backend_path in backend_paths:
130 try:
131 self._create_backend(backend_path)
132 except Exception, e:
133 path = application.log_traceback()
self = <elisa.core.interface_controller.InterfaceController object>
self._create_backend = <bound method
InterfaceController._create_backen...interface_controller.InterfaceController
object>>
backend_path = 'backend1'
/usr/lib/python2.4/site-packages/elisa/core/interface_controller.py in
_create_backend(self=<elisa.core.interface_controller.InterfaceController
object>, backend_name='backend1')
174
default=[])
175 try:
176 activity =
plugin_registry.create_component(activity_path)
177 except Exception, exc:
178 msg = "Cannot create activity %r for backend %r" %
(activity_path,
activity undefined
plugin_registry = <elisa.core.plugin_registry.PluginRegistry object>
plugin_registry.create_component = <bound method
PluginRegistry.create_component of
<elisa.core.plugin_registry.PluginRegistry object>>
activity_path = 'base:elisa_activity'
/usr/lib/python2.4/site-packages/elisa/core/plugin_registry.py in
create_component(self=<elisa.core.plugin_registry.PluginRegistry
object>, component_path='base:elisa_activity')
562 self.info("Component %s loaded" % component.name)
563 else:
564 raise ComponentNotFound(component_path)
565
566 return component
global ComponentNotFound = <class
elisa.core.plugin_registry.ComponentNotFound>
component_path = 'base:elisa_activity'
ComponentNotFound: Component 'base:elisa_activity' not found
__doc__ = None
__getitem__ = <bound method ComponentNotFound.__getitem__ of
<...core.plugin_registry.ComponentNotFound instance>>
__init__ = <bound method ComponentNotFound.__init__ of
<elisa.core.plugin_registry.ComponentNotFound instance>>
__module__ = 'elisa.core.plugin_registry'
__str__ = <bound method ComponentNotFound.__str__ of
<elisa.core.plugin_registry.ComponentNotFound instance>>
args = ()
component_name = 'base:elisa_activity'
The above is a description of an error in a Python program. Here is
the original traceback:
Traceback (most recent call last):
File
"/usr/lib/python2.4/site-packages/elisa/core/interface_controller.py",
line 143, in initialize
self._create_frontend(frontend_path)
File
"/usr/lib/python2.4/site-packages/elisa/core/interface_controller.py",
line 131, in initialize
self._create_backend(backend_path)
File
"/usr/lib/python2.4/site-packages/elisa/core/interface_controller.py",
line 176, in _create_backend
activity = plugin_registry.create_component(activity_path)
File "/usr/lib/python2.4/site-packages/elisa/core/plugin_registry.py",
line 564, in create_component
raise ComponentNotFound(component_path)
ComponentNotFound: Component 'base:elisa_activity' not found
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages elisa depends on:
ii elisa-plugins-bad 0.3.4-1 Elisa plugins from the "bad" set
ii elisa-plugins-good 0.3.4-1 Elisa plugins from the "good" set
ii python 2.4.4-6 An interactive high-level object-o
ii python-elisa 0.3.5-1 media center solution - Python lib
Versions of packages elisa recommends:
ii elisa-plugins-ugly 0.3.4-1 Elisa plugins from the "ugly" set
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Mar 19, 2008, Johannes Rohr wrote:
> Works for me after dpkg-reconfigure elisa plus rm -rf ~/.elisa
Ok, closing then.
--
Loïc Minier
--- End Message ---
