[glux] problema con elisa-extra

[Simone]

ma hai usato i pacchetti debian da fluendo o l'hai compilato da sorgenti?

2008/4/5, Ermes Pittore <ermes.pittore@gmail.com>:
>
> Ciao a tutti, ho un problema con elisa-extra su ubuntu 7.10, non riesco
> proprio a farlo partire, cercando in giro ho trovato qualcosa, però non ho
> risolto niente.
> Il problema è che inizia ad avviarsi (solo il rettangolo con su scritto
> elisa media center, logo etc..), gira per un 5secondi il mouse e poi niente,
> da terminale invece mi escono alcuni errori (si ferma sull'ultima riga di
> WARN MainThread, chiudo con ctrl+c,e poi mi scrive il resto):
>
> ermes@ermes-desktop:~$ elisa
> > WARN  MainThread      media_manager               apr 05 14:37:05
> > Creating provider media_ugly:shoutcast_media failed. A full traceback can be
> > found at /tmp/elisa_nG5YYl.txt (elisa/core/manager.py:103)
> > WARN  MainThread      service_manager             apr 05 14:37:05
> > Creating provider coherence_plugin:coherence_service failed. A full
> > traceback can be found at /tmp/elisa_t_FSxx.txt (elisa/core/manager.py:103)
> > WARN  MainThread      metadata_manager            apr 05 14:37:05
> > Creating provider media_good:gst_metadata failed. A full traceback can be
> > found at /tmp/elisa_abW2oY.txt (elisa/core/manager.py:103)
> > WARN  MainThread      media_manager               apr 05 14:37:05
> > Initializing fspot:fspot_media failed: Component fspot_media failed to
> > initialize: FSpot DB not found at '/home/ermes/.gnome2/f-spot/photos.db'.
> > (elisa/core/manager.py:95)
> > WARN  MainThread      media_manager               apr 05 14:37:05
> > Creating provider coherence_plugin:upnp_media failed. A full traceback can
> > be found at /tmp/elisa_iOwUp_.txt (elisa/core/manager.py:103)
> > WARN  MainThread      media_manager               apr 05 14:37:05
> > Creating provider media_bad:ipod_media failed. A full traceback can be found
> > at /tmp/elisa_4CaDFW.txt (elisa/core/manager.py:103)
> > WARN  MainThread      metadata_manager            apr 05 14:37:05
> > Creating provider media_good:taglib_metadata failed. A full traceback can be
> > found at /tmp/elisa_mdFGF3.txt (elisa/core/manager.py:103)
> > WARN  MainThread      metadata_manager            apr 05 14:37:05
> > Creating provider media_good:cover_in_dir failed. A full traceback can be
> > found at /tmp/elisa_n6Uq9I.txt (elisa/core/manager.py:103)
> > WARN  MainThread      media_manager               apr 05 14:37:05
> > Creating provider media_good:elisa_media failed. A full traceback can be
> > found at /tmp/elisa_7gpS7L.txt (elisa/core/manager.py:103)
> > WARN  MainThread      metadata_manager            apr 05 14:37:05
> > Creating provider media_good:cover_cache failed. A full traceback can be
> > found at /tmp/elisa_67RuDs.txt (elisa/core/manager.py:103)
> > WARN  MainThread      metadata_manager            apr 05 14:37:05
> > Creating provider media_good:amazon_covers failed. A full traceback can be
> > found at /tmp/elisa__-KJf1.txt (elisa/core/manager.py:103)
> > WARN  MainThread      media_manager               apr 05 14:37:05
> > Creating provider media_good:gnomevfs_media failed. A full traceback can be
> > found at /tmp/elisa_NdJg9a.txt (elisa/core/manager.py:103)
> > WARN  MainThread      interface_controller        apr 05 14:37:05
> > Cannot create activity 'base:elisa_activity' for backend 'backend1'
> > (elisa/core/interface_controller.py:180)
> > WARN  MainThread      interface_controller        apr 05 14:37:05  An
> > error occured causing backend 'backend1' creation to fail. A full traceback
> > can be found here: /tmp/elisa_UIcmoU.txt
> > (elisa/core/interface_controller.py:136)
> > WARN  MainThread      interface_controller        apr 05 14:37:05
> > Backend 'backend1' not existing for frontend 'frontend1'
> > (elisa/core/interface_controller.py:233)
> > WARN  MainThread      interface_controller        apr 05 14:37:05  An
> > error occured causing frontend 'frontend1' creation to fail. A full
> > traceback can be found here: /tmp/elisa_dJfilm.txt
> > (elisa/core/interface_controller.py:148)
> > WARN  MainThread      twisted                     apr 05 14:41:30  A
> > twisted traceback occurred. (twisted/internet/defer.py:402)
> >
> > Twisted traceback:
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.5/site-packages/twisted/internet/base.py", line
> > 343, in stop
> >     self.fireSystemEvent("shutdown")
> >   File "/usr/lib/python2.5/site-packages/twisted/internet/base.py", line
> > 400, in fireSystemEvent
> >     DeferredList(defrList).addBoth(self._cbContinueSystemEvent,
> > eventType)
> >   File "/usr/lib/python2.5/site-packages/twisted/internet/defer.py",
> > line 210, in addBoth
> >     callbackKeywords=kw, errbackKeywords=kw)
> >   File "/usr/lib/python2.5/site-packages/twisted/internet/defer.py",
> > line 182, in addCallbacks
> >     self._runCallbacks()
> > --- <exception caught here> ---
> >   File "/usr/lib/python2.5/site-packages/twisted/internet/defer.py",
> > line 317, in _runCallbacks
> >     self.result = callback(self.result, *args, **kw)
> >   File "/usr/lib/python2.5/site-packages/twisted/internet/base.py", line
> > 406, in _cbContinueSystemEvent
> >     self._continueSystemEvent(eventType)
> >   File "/usr/lib/python2.5/site-packages/twisted/internet/base.py", line
> > 411, in _continueSystemEvent
> >     for callList in sysEvtTriggers[1], sysEvtTriggers[2]:
> > exceptions.TypeError: 'NoneType' object is unsubscriptable
> > ermes@ermes-desktop:~$
>
>
> nel caso che non riuscissi a farlo funzionare avete altre alternative da
> consigliarmi?
>
> Ciao,
> Ermes
>
> PS: dovrebbe essere questo stesso problema<http://ubuntuforums.org/showthread.php?p=4532404#post4532404>, ma non dà nessuna soluzione
>
> _______________________________________________
> glux mailing list
> glux@lists.linux.it
> http://lists.linux.it/listinfo/glux
> http://www.lecco.linux.it
>
-------------- parte successiva --------------
Un allegato HTML è stato rimosso...
URL: http://lists.linux.it/pipermail/glux/attachments/20080405/132accde/attachment.htm