After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 637674 - Encountered a Fatal Error when launching Banshee
Encountered a Fatal Error when launching Banshee
Status: RESOLVED DUPLICATE of bug 621057
Product: banshee
Classification: Other
Component: general
1.9.0
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-12-20 16:21 UTC by Casey
Modified: 2010-12-20 16:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Banshee error log b running kill -s QUIT $(pidof banshee-1); cp ~/.config/banshee-1/log ~/Desktop/banshee.log (8.62 KB, text/plain)
2010-12-20 16:21 UTC, Casey
Details

Description Casey 2010-12-20 16:21:29 UTC
Created attachment 176768 [details]
Banshee error log b running kill -s QUIT $(pidof banshee-1); cp ~/.config/banshee-1/log ~/Desktop/banshee.log

This is the first bug report I've filed.  I'm getting better at using linux systems. I am running ubuntu 11  Natty Narwal .. thought I was on Maverick.

This message appears when I startup Banshee. I 've attached the error log report to this post.



An unhandled exception was thrown: Object reference
Comment 1 Michael Martin-Smucker 2010-12-20 16:32:51 UTC
From this line in the debug log:

> Sqlite error 11: database disk image is malformed

it looks like the database got corrupted (possibly by a system crash or a loss of power).  Luckily, recovering from this issue is usually pretty straightforward.  For simple step-by-step instructions, see the bottom of this page: http://banshee.fm/support/faq/

Really, it would be ideal for Banshee to attempt to recover from this kind of error automatically, so I'm marking this bug report as a duplicate of bug 621057.

Thanks for taking the time to report this.  Also, the problem isn't fixed after following those steps, feel free to reopen this report, or open new reports for any other issues you find.  Thanks!

*** This bug has been marked as a duplicate of bug 621057 ***