Bug 1047388 - Rhythmbox crashes when loading album art
Summary: Rhythmbox crashes when loading album art
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-30 21:07 UTC by Matt Hirsch
Modified: 2015-06-29 13:58 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 13:58:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
rhythmbox -d output (7.97 KB, text/plain)
2013-12-30 21:07 UTC, Matt Hirsch
no flags Details

Description Matt Hirsch 2013-12-30 21:07:09 UTC
Created attachment 843542 [details]
rhythmbox -d output

Description of problem:

When I play a song that has corresponding album art, rhythmbox gets and Aborted. I deleted all rhythmbox settings and caches in .local and .config and .cache and let the f20 version of rhythmbox regenerate these. I get this output running rhythmbox and playing a song which rhythmbox has downloaded album covers:

rhythmbox: cairo-pattern.c:1062: cairo_pattern_reference: Assertion `((*&(&pattern->ref_count)->ref_count) > 0)' failed.
Aborted

I've attached the relevant rhythmbox -d output.

Version-Release number of selected component (if applicable):
rhythmbox-3.0.1-2.fc20.x86_64

How reproducible:
always

Steps to Reproduce:
1. play a mp3 with album art

Actual results:
Aborted

Expected results:
Music

Additional info:

Comment 1 Matt Hirsch 2013-12-30 21:12:25 UTC
Just to clarify, this seems to occur when the mp3 has embedded album art in an id3 tag, not when rhythmbox downloads the art. Here's the id3info for the file:

*** Tag information for 01 ''Bang Bang (My Baby Shot Me Down)''.mp3
=== APIC (Attached picture): ()[, 0]: image/bmp, 270054 bytes
=== NCON ():  frame
=== TRCK (Track number/Position in set): 01
=== TPUB (Publisher): Maverick
=== TALB (Album/Movie/Show title): Kill Bill (Volume One)
=== TLEN (Length): 159000
=== TIT2 (Title/songname/content description): ''Bang Bang (My Baby Shot Me Down)''
=== TPE1 (Lead performer(s)/Soloist(s)): Nancy Sinatra
=== COMM (Comments): (iTunNORM)[eng]:  000000F3 00000465 0000081A 00001AC3 00009C85 00015FBE 000053E5 00006306 00009C85 000111B5
=== TCON (Content type): (99)
*** mp3 info
MPEG1/layer III
Bitrate: 192KBps
Frequency: 44KHz

Comment 2 Fedora End Of Life 2015-05-29 10:14:55 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-06-29 13:58:11 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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