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 591044 - Tracks with a picture of null dimensions embed in the tag can't be imported into Rhythmbox
Tracks with a picture of null dimensions embed in the tag can't be imported i...
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
0.10.22
Other All
: Normal minor
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-08-07 10:22 UTC by Hyogapag
Modified: 2010-02-23 00:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Hyogapag 2009-08-07 10:22:59 UTC
Please describe the problem:
I had some tracks (mp3) I could not import into Rhythmbox (0.12.0), and the alleged cause was "a Gstreamer internal error". So I thought these files were heavily corrupted. Just to check if it was an id3tag problem, I opened them with easytag. I saw there was a picture embed in it, but easytag refused to display it, saying : "Error : the picture can't be displayed because its length is null". Nevertheless, I was able to delete this picture from easytag. After that, Rhythmbox imported the tracks.

Steps to reproduce:
1. Create a picture with null dimensions.
2. Put this picture into an mp3 file.
3. Try to import this file into Rhythmbox.


Actual results:
Rhythmbox is not able to import the file, so it can't be played.

Expected results:
Rhythmbox should import the file, and just ignore the picture.

Does this happen every time?
Yes, afaik.

Other information:
Comment 1 Tim-Philipp Müller 2009-08-07 10:43:30 UTC
Could you make the file available please. The beginning of the file with the tag should do as well: head --bytes=250k foo.mp3 > head.mp3

 
Comment 2 Tim-Philipp Müller 2010-02-23 00:42:22 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!