Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Everytime I try to make a rescan, Banshee keeps crashing. The songs it was able to discover are added to library list on the next start up of Banshee. Then, it crashes again if I am to try rescan.

Any ideas?

share|improve this question

closed as off topic by Jorge Castro, Oli, Marco Ceppi Nov 10 '10 at 22:55

Questions on Ask Ubuntu are expected to relate to Ubuntu within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

This should be reported as a bug report to – Jorge Castro Nov 8 '10 at 13:58
Is it always just adding the same list of music, or does it discover more each time? – Adam Nov 8 '10 at 13:58
up vote 2 down vote accepted

This is a common bug with banshee's database. To solve it, delete your banshee.db in ~/.config/Banshee-1. The next time you scan it should work without crashing.

EDIT: forgot to mention, you should make sure that you export playlists when you create them as they are stored in the database.

share|improve this answer
Thanks, that's worked. – seed Nov 8 '10 at 14:23
Play counts, skip counts, ratings, and a lot more are also stored in the database, so do this with care. IIRC, the crash usually happens when Banshee tries update the smart playlists while rescanning. There's an open bug report for this, and even a working patch, I think. – Michael Martin-Smucker Aug 8 '11 at 18:05
@MichaelMS: yes all of that data is stored in the database, but also in the files (so long as you enable the option to write metadata to the files, which you should do). – RolandiXor Aug 8 '11 at 18:20

Try running banshee from a terminal and then running a scan. This should output the error that is causing the program to crash. Without this, theres not much we can do.

Hope this helps, Bodsda

share|improve this answer
for those trying to find out a bit more try banshee --debug, as that will produce a bit more detail and normally gives an answer at the point of the crash. – Adam Nov 8 '10 at 14:38

Not the answer you're looking for? Browse other questions tagged or ask your own question.