GNOME Bugzilla – Bug 126372
Crash when playing Internet radio station
Last modified: 2004-12-22 21:47:04 UTC
Package: rhythmbox Severity: normal Version: 0.5.4 Synopsis: Crash when playing Internet radio station Bugzilla-Product: rhythmbox Bugzilla-Component: General BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of Problem: some part of rhythmbox dropped to bug-buddy while I was starting to play a radio station (the gui appears to continue running) Steps to reproduce the problem: unsure, but I think this is what I did: 1. select radio station (KCRW, I think) 2. immediately click the notification area icon 3. station begins loading 4. Then crash How often does this happen? this was the first time Additional Information: hopefully the stacktrace will be of use Debugging Information: Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 10033)] [New Thread 32769 (LWP 10064)] [New Thread 16386 (LWP 10065)] [New Thread 32771 (LWP 10066)] [New Thread 638980 (LWP 13986)] [New Thread 655365 (LWP 13987)] [New Thread 671750 (LWP 13988)] [New Thread 114695 (LWP 12440)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x409c6bdb in waitpid () from /lib/libpthread.so.0
+ Trace 41508
Thread 7 (Thread 671750 (LWP 13988))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-06 10:37 ------- Reassigning to the default owner of the component, rhythmbox-maint@bugzilla.gnome.org.
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 125749 ***