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 610383 - Rhythmbox hangs at regular intervals: Internal GStreamer error: pad problem
Rhythmbox hangs at regular intervals: Internal GStreamer error: pad problem
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.25
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-02-18 18:19 UTC by cupp
Modified: 2010-12-01 01:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description cupp 2010-02-18 18:19:56 UTC
About once every day or every other day, Rhythmbox hangs while in playback.  The following error window pops up:

Couldn't start playback
Internal GStreamer error: pad problem.  Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.

The song indicated to play next has a red "x" icon indicating a bad input file.  However, each time the song in question has played previously and plays again after a re-start of Rhythmbox.

When the error window is closed and after that Rhythmbox is (manually) closed, Rhythmbox automatically re-launches and is ready to play.

I can send additional details or try to capture additional information if I know what any developer would find useful in this situation.
Comment 1 Sebastian Dröge (slomo) 2010-02-22 19:15:37 UTC
Is this somehow reproducible? Maybe always the same files or something?
Comment 2 cupp 2010-02-22 22:27:53 UTC
Sorry, I have not been able to find anything in common about the events which cause Rhythmbox to hang.  When I ceases playing the song involved is still in view (i.e., the interface does not crash).  As soon as Rhythmbox is manually closed it re-launches and each time I've tested it the song displayed on hang-up plays just fine.

I've also tried to correlate it to other events, e.g., other apps open, etc.  Nothing common noted yet.  I can't even tie to something within Rhythmbox, e.g., a plugin.  

If I find anything in common, I will add it here.
Comment 3 Hubert Furey 2010-02-28 02:25:59 UTC
I am having exact same problem. Have been using ubuntu and rb for years now.  Updated to 9.10 and get same problem as described above. No problems with earlier versions. Start playing some tunes and it will eventually stop playing the music with the error message above. Restart RB and can attempt to continue. 

Is there a log file or somewhere you can point me for troubleshooting basics?
Comment 4 Hubert Furey 2010-03-15 22:47:01 UTC
My problem appears resolved.  Had a log file indicating a problem with Pulseaudio crashing when RB would stop playing songs.  Ubuntu 9.04 distribution upgrade.  Followed steps in this link and my problem appears resolved, RB plays music no problems now.   
http://ubuntuforums.org/showthread.php?t=789578

Hope it helps..
Comment 5 cupp 2010-03-16 03:09:15 UTC
I have previously configured PulseAudio in my Fedora installation.  (I followed a guide document on FedoraForums.org.)  After said configuration, PulseAudio has performed well and all sound events work as expected.

I don't think this Rhythmbox problem stems from PulseAudio.

Can anyone guide me to what log(s) to pull and send copies for troubleshooting?
Comment 6 Hubert Furey 2010-03-19 01:39:40 UTC
I know nothing for Fedora.... Under Ubuntu (System > Admin > Log File Viewer) the problem appeared in the kern.log and /or syslog files...Don't remember which one.  You should also check out the dmesg command for checking log info from the kernal.  Again, I don't know much beyond Ubuntu, and very little at that.  

Check out where your system logs are and start there.
Comment 7 Tim-Philipp Müller 2010-10-08 17:51:14 UTC
We would need a GST_DEBUG log to figure out what the problem is.

You would need to start rhythmbox from the commandline/terminal like this:

 $ GST_DEBUG=*:5 rhythmbox 2>&1 | grep -v REFCOUNT | tail -n 10000 >dbg.log

and then reproduce the error. When you get the error dialog, you stop rhythmbox using Control-C in the terminal. Then attach the dbg.log file to this bug report.


What Fedora version are you using? Have you tried the latest/upcoming Fedora version to see if the problem still exists?
Comment 8 Fabio Durán Verdugo 2010-12-01 01:43:54 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!