starting elisa after upgrade fails

Bug #233762 reported by Thomas Vander Stichele
2
Affects Status Importance Assigned to Milestone
Moovida
Won't Fix
Undecided
Unassigned

Bug Description

This is a clean install of FC7.

I installed elisa 0.3.1 from packages. I created a config that worked.

Then I installed 0.3.5 from source (elisa, good and bad) in $HOME/prefix and started it.

I get this:
WARN MainThread service_manager Apr 18 23:34:59 Creating provider base:hal_service failed. A full traceback can be found at /tmp/elisa_eJdA6a.txt (elisa/core/manager.py:103)
WARN MainThread media_manager Apr 18 23:34:59 Creating provider base:upnp_media failed. A full traceback can be found at /tmp/elisa_o8v_Wc.txt (elisa/core/manager.py:103)
WARN MainThread metadata_manager Apr 18 23:34:59 Creating provider base:gst_metadata failed. A full traceback can be found at /tmp/elisa_dAvDU1.txt (elisa/core/manager.py:103)
WARN MainThread media_manager Apr 18 23:34:59 Creating provider base:ipod_media failed. A full traceback can be found at /tmp/elisa_j4-E1B.txt (elisa/core/manager.py:103)
WARN MainThread media_manager Apr 18 23:34:59 Creating provider base:elisa_media failed. A full traceback can be found at /tmp/elisa_5lZoBB.txt (elisa/core/manager.py:103)
WARN MainThread metadata_manager Apr 18 23:34:59 Creating provider base:taglib_metadata failed. A full traceback can be found at /tmp/elisa_Dot4vv.txt (elisa/core/manager.py:103)
WARN MainThread metadata_manager Apr 18 23:34:59 Creating provider base:cover_in_dir failed. A full traceback can be found at /tmp/elisa_LV8YyZ.txt (elisa/core/manager.py:103)
WARN MainThread media_manager Apr 18 23:34:59 Creating provider base:gnomevfs_media failed. A full traceback can be found at /tmp/elisa_p7FeLN.txt (elisa/core/manager.py:103)
WARN MainThread media_manager Apr 18 23:34:59 Creating provider base:audiocd failed. A full traceback can be found at /tmp/elisa_bviWtq.txt (elisa/core/manager.py:103)
WARN MainThread metadata_manager Apr 18 23:34:59 Creating provider base:cover_cache failed. A full traceback can be found at /tmp/elisa_ckJP7R.txt (elisa/core/manager.py:103)
WARN MainThread metadata_manager Apr 18 23:34:59 Creating provider base:amazon_covers failed. A full traceback can be found at /tmp/elisa_Tju7OX.txt (elisa/core/manager.py:103)
WARN MainThread interface_controller Apr 18 23:34:59 Cannot create activity 'base:elisa_activity' for backend 'backend1' (elisa/core/interface_controller.py:180)
WARN MainThread interface_controller Apr 18 23:34:59 An error occured causing backend 'backend1' creation to fail. A full traceback can be found here: /tmp/elisa_pZm2Bc.txt (elisa/core/interface_controller.py:136)
WARN MainThread interface_controller Apr 18 23:34:59 Backend 'backend1' not existing for frontend 'frontend1' (elisa/core/interface_controller.py:233)
WARN MainThread interface_controller Apr 18 23:34:59 An error occured causing frontend 'frontend1' creation to fail. A full traceback can be found here: /tmp/elisa_pcdQue.txt (elisa/core/interface_controller.py:148)

and then it hangs without displaying anything else.

Revision history for this message
Philippe Normand (philn) wrote :

Elisa 0.3.5 is unsupported

Changed in elisa:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.