Bug 501322 - [Inability to launch] An unhandled exception was thrown: Could not read add-in description
Summary: [Inability to launch] An unhandled exception was thrown: Could not read add-i...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: banshee
Version: rawhide
Hardware: x86_64
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-18 14:48 UTC by Kvikende
Modified: 2009-05-27 13:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-05-27 13:26:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
the exception error message (2.73 KB, text/plain)
2009-05-18 14:50 UTC, Kvikende
no flags Details

Description Kvikende 2009-05-18 14:48:59 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; nn-NO; rv:1.9.1b4) Gecko/20090427 Fedora/3.5-0.20.beta4.fc11 Firefox/3.5b4

When I try to start up Banshee it will show a "Banshee Encountered a Fatal Error" box and not start up.

Reproducible: Always

Steps to Reproduce:
1. Install Banshee-1
2. Open Banshee-1
Actual Results:  
Fatal error

Expected Results:  
A working Banshee player with all its glory

Comment 1 Kvikende 2009-05-18 14:50:08 UTC
Created attachment 344451 [details]
the exception error message

Comment 2 David Nielsen 2009-05-18 17:18:53 UTC
I have seen this one as well, even with git master. I think it is an upstream bug but I am not sure.

Normally for me it happens the first time I launch banshee in a user session, then afterwards it's fine. 

I've pushed this to upstream as 583107

Please follow up on:
http://bugzilla.gnome.org/show_bug.cgi?id=583107

Comment 3 Kvikende 2009-05-27 13:26:07 UTC
I managed to fix the problem by deleting the ~/.config/banshee-1/addin-db-001 folder and all it contained. I believe some files have been corrupted somehow. I wish that Banshee could see that problem and fix it itself.


Note You need to log in before you can comment on or make changes to this bug.