GNOME Bugzilla – Bug 162982
Rhythmbox crash while attempting to play mp3 stream
Last modified: 2005-06-05 11:47:19 UTC
Distribution: Slackware Slackware 10.0.0 Package: rhythmbox Severity: critical Version: GNOME2.8.2 0.8.8 Gnome-Distributor: Dropline Systems Synopsis: Rhythmbox crash while attempting to play mp3 stream Bugzilla-Product: rhythmbox Bugzilla-Component: iradio Bugzilla-Version: 0.8.8 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Choose Internet Radio Station, double click or choose play from dropdown menu, buffering, then "application has unexpectedly crashed" Steps to reproduce the crash: 1. Choose Internet Radio Station for play 2. 3. Expected Results: MP3 stream should play How often does this happen? Every time attempting to run stream. Additional Information: GNOME 2.8.2, Rhythmbox 0.8.8 both from Dropline Systems build for Slackware 10.0 Debugging Information: Backtrace was generated from '/usr/local/bin/rhythmbox' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 3088)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 3088)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 3088)] [New Thread 32769 (LWP 3089)] [New Thread 16386 (LWP 3090)] [New Thread 32771 (LWP 3091)] [New Thread 49156 (LWP 3092)] [New Thread 65541 (LWP 3093)] [New Thread 98310 (LWP 3095)] [New Thread 114695 (LWP 3096)] [New Thread 131080 (LWP 3097)] 0x40e0468b in waitpid () from /lib/libpthread.so.0
+ Trace 54151
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-04 23:42 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "rhythmbox". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was attiladehun@verizon.net. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
This looks like it matches the thread of the stack trace in bug 160835 with the signal handler call--duplicate?
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 168079 ***