Bug 337061 - tunepimp: Cannot decode file. (Decoder crashed)
Summary: tunepimp: Cannot decode file. (Decoder crashed)
Alias: None
Product: Fedora
Classification: Fedora
Component: libtunepimp
Version: 8
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-10-18 04:37 UTC by Sean Bruno
Modified: 2008-03-02 13:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-03-02 13:45:29 UTC

Attachments (Terms of Use)
This is an MP3 file that crashes libmusicbrainz on my machine (3.65 MB, audio/mpeg)
2007-10-18 04:37 UTC, Sean Bruno
no flags Details

System ID Priority Status Summary Last Updated
KDE Software Compilation 158434 None None None Never

Description Sean Bruno 2007-10-18 04:37:32 UTC
Description of problem:
Amarok is failing to tag files via libmusicbrainz.  More specifically it is
reporting a crash of the musicbrainz backend.

Version-Release number of selected component (if applicable):
[sean@home-desk ~]$ rpm -q -a|grep musicbrainz
[sean@home-desk ~]$ rpm -q -a|grep amarok

How reproducible:
Seems to happen every time.

Steps to Reproduce:
1. Attempt to tag a file with libmusicbrainz
Actual results:
Crash dialog:
Tunepimp (MusicBrainz tagging library) returned the following
error: "Cannot decode file. (Decoder crashed)".

Once it crashes, you cannot tag that file with libmusicbrainz again until you
restart Amarok.  You can however, tag other files.

Expected results:
It tags the file if the data is found at musicbrainz.org

Additional info:

Comment 1 Sean Bruno 2007-10-18 04:37:32 UTC
Created attachment 230651 [details]
This is an MP3 file that crashes libmusicbrainz on my machine

Comment 2 Rex Dieter 2008-02-25 12:44:30 UTC
$ rpm -q amarok libtunepimp libtunepimp-extras-nonfree

Comment 3 Rex Dieter 2008-02-25 12:50:16 UTC
Fwiw, I just tried importing the provided, mp3, and I can edit tags as well as
"Fill in tags using MusicBrainz".

Comment 4 Sean Bruno 2008-02-25 15:52:12 UTC
The same issue affects my F8 installations:

[sean@home-desk ~]$ rpm -q amarok libtunepimp libtunepimp-extras-nonfree

Tagging will fail after some amount of editing.  This amount is not fixed and
changes.  I can't seem to edit more than 20 files before I run into this issue.

Comment 5 Rex Dieter 2008-02-25 16:01:51 UTC
Can you try updating this:

Comment 6 Sean Bruno 2008-02-25 16:21:32 UTC
That didn't help with the crash. 

I selected 8 untagged MP3's.  I then selected the Fill-in tags using Musicbrainz
button.  After a few moments, the crash dialog appears.

Comment 7 Rex Dieter 2008-02-25 16:32:36 UTC
OK, I can confirm now (appears to be x86_64 specific?).  
Would appear that libtunepimp/libmusicbrainz support is just (a bit, at least) 

Comment 8 Fedora Update System 2008-02-26 00:25:24 UTC
taglib-1.5-1.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update taglib'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-1960

Comment 9 Sean Bruno 2008-02-26 01:13:10 UTC
I installed the update referenced in comment #8 when it was suggested in Comment
#5.  No change to behavior noted and the same error persists.

Comment 10 Rex Dieter 2008-02-26 01:17:38 UTC
Sean, looks like we've tried most everything we can do here packaging-wise, it
would be a good idea at this point to escalate the issue to amarok's developers
by reporting this upstream to bugs.kde.org.

Comment 11 Sean Bruno 2008-02-26 04:41:32 UTC
As per request, I have filed this upstream with the kde folks:


Comment 12 Sean Bruno 2008-02-26 05:07:28 UTC
Just for the record, a libtunepimp update appeared
today(libtunepimp-0.5.3-11.fc8).  This had no effect on behavior after I
restarted Amarok.

Comment 13 Rex Dieter 2008-03-02 13:45:29 UTC
We'll continue to track this upstream, thanks for the report.

Note You need to log in before you can comment on or make changes to this bug.