ReplayGain plugin makes Rhythmbox turn all grey

Bug #1492348 reported by Coeur Noir
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hi.

I was randomly playing songs from my "whole" library.

Some of the songs were less loud than others so I activated

replay-gain plugin

and restarted Rhythmbox.

Now Rhythmbox plays one or two songs and then freezes, turns all grey and I have to force-quit it.

Everything work fine again as soon as I disable replay-gain.

(I thought that bug with replay gain was fixed with RB 3.0.1)

By the way I'm using RB 3.0.2 in Ubuntu 14.04 / unity DE.

Revision history for this message
Coeur Noir (coeur-noir) wrote :

Also note that I did on all my mp3 and ogg files a :

mp3gain -s d

assuming it could delete some maybe wrong datas about replay-gain (?)

Here is what terminal displays when Rhythmbow is freezing :

_______________________________

~$ rhythmbox

(rhythmbox:13849): Gtk-CRITICAL **: gtk_css_provider_load_from_path: assertion 'path != NULL' failed

(rhythmbox:13849): GLib-GObject-CRITICAL **: object SoupServer 0x28f60b0 finalized while still in-construction

(rhythmbox:13849): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid). Please use GInitable instead.

(rhythmbox:13849): GLib-GObject-CRITICAL **: object SoupServer 0x28f6150 finalized while still in-construction

(rhythmbox:13849): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid). Please use GInitable instead.

(rhythmbox:13849): GLib-GObject-CRITICAL **: object SoupServer 0x28f6150 finalized while still in-construction

(rhythmbox:13849): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid). Please use GInitable instead.

(rhythmbox:13849): GStreamer-CRITICAL **: gst_segment_to_stream_time: assertion 'segment->format == format' failed

(rhythmbox:13849): GStreamer-WARNING **: gstpad.c:4555:store_sticky_event:<sink:proxypad0> Sticky event misordering, got 'caps' before 'stream-start'

(rhythmbox:13849): GStreamer-WARNING **: gstpad.c:4555:store_sticky_event:<rgvolume-volume:src> Sticky event misordering, got 'caps' before 'stream-start'

(rhythmbox:13849): GStreamer-WARNING **: gstpad.c:4555:store_sticky_event:<rgvolume0:src> Sticky event misordering, got 'caps' before 'stream-start'

(rhythmbox:13849): GStreamer-WARNING **: gstpad.c:4555:store_sticky_event:<src:proxypad1> Sticky event misordering, got 'caps' before 'stream-start'

(rhythmbox:13849): GStreamer-WARNING **: gstpad.c:4555:store_sticky_event:<rgvolume-volume:sink> Sticky event misordering, got 'caps' before 'stream-start'

(rhythmbox:13849): GStreamer-WARNING **: gstpad.c:4555:store_sticky_event:<rgvolume0:sink> Sticky event misordering, got 'caps' before 'stream-start'

(rhythmbox:13849): GStreamer-CRITICAL **: gst_segment_to_stream_time: assertion 'segment->format == format' failed

_______________________________

…which seems to confirm there's a problem with replay-gain (rgvolume).

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in rhythmbox (Ubuntu):
status: New → Confirmed
Revision history for this message
rithik g (gkrithi) wrote :

Is this still an issue ?

Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue using a maintained version of Ubuntu please let us know otherwise this report can be left to expire in approximately 60 days time.

Paul White
[Ubuntu Bug Squad]

Changed in rhythmbox (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]

Changed in rhythmbox (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.