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 664831 - Failed to link new stream into GStreamer pipeline
Failed to link new stream into GStreamer pipeline
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: playback
HEAD
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-11-25 18:03 UTC by Sven Arvidsson
Modified: 2012-01-14 22:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace (50.87 KB, text/plain)
2011-11-25 18:03 UTC, Sven Arvidsson
Details
truncated log (555.30 KB, application/x-gzip)
2011-11-26 17:11 UTC, Sven Arvidsson
Details

Description Sven Arvidsson 2011-11-25 18:03:09 UTC
Created attachment 202148 [details]
backtrace

Hi,

I'm frequently having a problem where on a track change, Rhythmbox will either log an error (showing a warning icon next to the track) and go on playing, or simply stop. It doesn't hang at this point, but is refusing to play anything else (I can double click a new track, artist name and title is displayed but nothing happens and the slider stays at 0:00). However if I try to quit, Rhythmbox hangs and needs to be killed.

The error logged is "Failed to link new stream into GStreamer pipeline". 

I haven't found a way to reliably reproduce the bug, sometimes track changes work fine, sometimes they don't, but I usually can't listen to a complete album without triggering the bug. 

File type does not seem to matter, it's happened with both FLAC and Mp3, but I _think_ it's limited to the crossfading backend.

This bug started occurring with the git snapshots packaged in Debian,  at least as far back as 2dfea6

I have attached a backtrace from the hang mentioned above.
Comment 1 Jonathan Matthew 2011-11-26 00:35:40 UTC
Unfortunately the stack trace doesn't tell me much.  If you can reproduce this with 'GST_DEBUG=*:4 rhythmbox -D player' that might help.  Probably a race condition that won't occur with so much debug output, though..
Comment 2 Sven Arvidsson 2011-11-26 17:11:40 UTC
Created attachment 202195 [details]
truncated log 

I did manage to reproduce the bug with logging enabled (though for some reason I did not get a warning icon in Rhythmbox).

The log file is quite large so I have only attached the last 10M. In case you need the full log I have uploaded it here: http://dl.dropbox.com/u/28577999/rb.log.gz  (90M compressed).
Comment 3 Brian Marshall 2012-01-06 00:00:38 UTC
I have the same problem, is there any more information or help needed? I tried to produce a log file with "GST_DEBUG=*:4 rhythmbox -D player", but there was too much disk thrashing (making playback sluggish) and the file quickly ballooned to 2.5GB after only a song and a half. =\
Comment 4 Jonathan Matthew 2012-01-14 14:05:58 UTC
I've fixed the 'failed to link new stream' error in commit a5940fd, but I suspect some of the symptoms you're seeing are caused by other bugs. This particular bug only occurred on track changes within the same album with crossfading enabled, which mostly matches your description, but I never saw it cause the whole process to hang. Please reopen if you still have problems like this with the forthcoming rhythmbox 2.95 or anything past that.
Comment 5 Sven Arvidsson 2012-01-14 22:40:16 UTC
Thanks!

I have been running rb for a couple of hours now with the patch applied and it seems to be working fine.