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 705468 - [BPM] Crash on start, even after preference reset
[BPM] Crash on start, even after preference reset
Status: RESOLVED DUPLICATE of bug 722551
Product: banshee
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-08-04 23:10 UTC by swbusche
Modified: 2014-03-12 00:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Both logs together. (27.44 KB, text/x-log)
2013-08-04 23:11 UTC, swbusche 		Details

Description swbusche 2013-08-04 23:10:50 UTC 
I recently install Linux Mint 15 - Cinnamon x64.

Upon importing my music from a mounted volume, banshee crashed. Deleting the config file and again reimporting, it now crashes after about five seconds.

I'm attaching the kill process log as well as the actual output of the program when I run it with `banshee -debug`.

Let me know if you need more information. I was previously using the same mount point and music files on Debian (Testing) with Banshee with no issues.
Comment 1 swbusche 2013-08-04 23:11:12 UTC 
Created attachment 250823 [details]
Both logs together.
Comment 2 Bertrand Lorentz 2013-08-05 13:21:15 UTC 
Thank you for your bug report.

It looks like the crash is caused by the soundtouch library, which used to do the "beat per minute" detection.
Could you try to disable this feature ?

Go to Edit > Preferences, in the Sources tab, make sure the Music source is selected, and uncheck the "Automatically detect BPM for all songs" box. You might also have to disable the "BPM Detection" extension (in the Extensions tab).

I think this extension might be disabled by default on Debian, because of this bug.
Comment 3 swbusche 2013-08-05 21:56:57 UTC 
It worked on Debian suprisingly.

I've disabled both the BPM detection option and the addon and it appears to be working now.

Thanks.
Comment 4 Andrés G. Aragoneses (IRC: knocte) 2013-08-06 06:53:35 UTC 
I think Debian bundles a packager-patch to disable BPM.

IMHO we should make BPM be off by default, moving forward. I wanted to use the "anonymous usage data" feature to find out the percentage of people using this feature, to make a more informed decision, but I haven't had time to look into it yet.
Comment 5 Andrés G. Aragoneses (IRC: knocte) 2014-03-12 00:12:35 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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