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 586905 - hangs when attempting to play mp3 files with cross-fading plugin enabled
hangs when attempting to play mp3 files with cross-fading plugin enabled
Status: RESOLVED INCOMPLETE
Product: rhythmbox
Classification: Other
Component: playback
0.12.x
Other Linux
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-06-25 02:38 UTC by Michael Norrish
Modified: 2009-12-17 18:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Norrish 2009-06-25 02:38:21 UTC 
As per the summary line: if I attempt to play an mp3 file, the program hangs and has to be "force quit"-ed.  The mp3 file plays successfully if I disable the cross-fading plugin and restart.  It is not enough to just disable it: attempting to play the mp3 file without the restart causes the hang.

This is my attempt to report the essence of the problem reported at https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/373534

This used to work in Ubuntu 8.10, but while the MP3 file played alright, the seekbar didn't progress.  I believe this is why some of the comments in that link talk about that, and not the failure to play the MP3 file at all.
Comment 1 Jonathan Matthew 2009-06-25 02:44:57 UTC 
The "(requires restart)" next to the "use crossfading backend" should be a bit of a clue that you need to restart rhythmbox when you change that setting.

Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Javier Jardón (IRC: jjardon) 2009-12-17 18:04:13 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!