GNOME Bugzilla – Bug 722551
Banshee crashes on startup (BPM detection: SoundTouch SIGABRT)
Last modified: 2016-10-05 02:44:33 UTC
Created attachment 266658 [details] ~/.config/banshee-1/log I do have the same problem with rhythmbox, so maybe something's wrong with my file library or podcast lists. However, this is not a reason for crashing. I have already tried to recreate the media library by deleting the .db file, but the error returns when I add again the media directory and my favourite podcasts. I attached the log file.
Created attachment 266659 [details] Standard output of banshee --debug
Thank you for your bug report. There seems to be bug in the SoundTouch library, which we use (through GStreamer) to do BPM (Beat Per Minute) detection. See for example: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1193667 According to that bug, the problem should be fixed in soundtouch version 1.7.1-5. Could you check which version you have installed on you system ? The name of the package should be "libsoundtouch0". As a workaround, you can disable BPM detection through the preferences dialog, under Source Specific > Source:Music > Automatically detect BPM Or you can use gconf editor to unset the /apps/banshee-1/plugins/bpm/auto_enabled key
Bingo, my libsoundtouch version is below 1.7.1-5: ii libsoundtouch0 1.7.1-2 amd64 Sound stretching library I disabled BPM detection and it seems to work now. Thank you! Will try to find a newer version of libsoundtouch0 for ubuntu. Best Philipper
Resolved by installing the libsoundtouch0 package 1.7.1-5 from trusty: http://packages.ubuntu.com/trusty/libsoundtouch0 Thank you for your help!
Well, libsoundtouch is not part of Gnome as far as I know, then I will mark this with the proper status :) Thanks for testing, and thanks for informing us.
*** Bug 703367 has been marked as a duplicate of this bug. ***
*** Bug 705468 has been marked as a duplicate of this bug. ***
*** Bug 732119 has been marked as a duplicate of this bug. ***
*** Bug 732417 has been marked as a duplicate of this bug. ***
*** Bug 706951 has been marked as a duplicate of this bug. ***