Bug 501322 - [Inability to launch] An unhandled exception was thrown: Could not read add-in description
[Inability to launch] An unhandled exception was thrown: Could not read add-i...
Product: Fedora
Classification: Fedora
Component: banshee (Show other bugs)
x86_64 Linux
low Severity urgent
: ---
: ---
Assigned To: Michel Alexandre Salim
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-05-18 10:48 EDT by Kvikende
Modified: 2009-05-27 09:26 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-05-27 09:26:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description Kvikende 2009-05-18 10:48:59 EDT
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 10:50:08 EDT
Created attachment 344451 [details]
the exception error message
Comment 2 David Nielsen 2009-05-18 13:18:53 EDT
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:
Comment 3 Kvikende 2009-05-27 09:26:07 EDT
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.