GNOME Bugzilla – Bug 120858
seeking/playing some songs sometimes causes "Could not set caps..."
Last modified: 2004-12-22 21:47:04 UTC
Changing the position of the currently playing song using the slider causes rhythmbox to display an error message and then lock-up. "could not set caps on source pad, aborting..." The app then is not responsive. I am using the i686 glibc on RH9, gstreamer-0.6.3, rhythmbox HEAD.
Created attachment 19558 [details] backtrace after lockup
I need the output of "thread apply all bt", not just "bt".
Created attachment 19560 [details] thread apply all bt
Created attachment 19574 [details] thread apply all bt
File specs that bring up error: mp3 (encoded as mpeg 2 layer 1) Bitrate: 112 kb/s Samplerate 24000 Hz 77066 frames (extremely high compared to my other mp3's) Only mp3 in my collection encoded this way. Only song to bring about error.
William: These backtraces don't have the information we need, and I think I know why. Instead of waiting for the error dialog, could you instead set a breakpoint on monkey-media-player-gst-tmp.c:error_cb, wait for it to hit, and then do a "thread apply all bt" from there?
Created attachment 19584 [details] bt from monkey-media-player-gst-tmp.c:error_cb
error message emanates from gst-plugins/ext/mad/gstmad.c:1154
This problem appears to be fixed in CVS HEAD. I imagine this is due to: Revision: walters@rhythmbox.org--2003/rhythmbox--mainline--1.0--patch-54 Hardcode use of mad/vorbisfile/flacdec, until spider works Colin, thank you, thank you!
Closing based on the last comment.