Description of problem: When trying to play an mp3 file or internet radio, rhythmbox fails with: rhythmbox: cairo-pattern.c:1062: cairo_pattern_reference: Assertion `((*&(&pattern->ref_count)->ref_count) > 0)' failed. Aborted Version-Release number of selected component (if applicable): rhythmbox.x86_64 3.0.1-2.fc20 @updates How reproducible: Always: - Internet radio always - mp3 playback sometimes works the first song, but then crashes when starting the next song Steps to Reproduce: 1. in an X-terminal type: rhythmbox 2. click on an mp3 file or an internet radio channel for playback 3. Actual results: [gert@jupiter tmp]$ rhythmbox (rhythmbox:2857): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid). Unable to remove object from construction_objects list, so memory was probably just leaked. Please use GInitable instead. (rhythmbox:2857): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid). Unable to remove object from construction_objects list, so memory was probably just leaked. Please use GInitable instead. (rhythmbox:2857): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid). Unable to remove object from construction_objects list, so memory was probably just leaked. Please use GInitable instead. rhythmbox: cairo-pattern.c:1062: cairo_pattern_reference: Assertion `((*&(&pattern->ref_count)->ref_count) > 0)' failed. Aborted [gert@jupiter tmp]$ Expected results: Playback of the selected mp3 file or internet radio station without abort. Additional info:
I'm on Fedora 20 and I'm affected by this bug. It seems to be a regression between 3.0-3.fc20 and 3.0.1-2.fc20, introduced as a byproduct of the fix for #1043259. #1047018 may be a duplicate of this bug.
For me also the problem was introduced after upgrading to 3.0.1-2.fc20. Looking at the backtrace in bug #1047018 also crashes at cairo-pattern.c:1062, it looks indeed that this is the same bug.
*** This bug has been marked as a duplicate of bug 1047018 ***