Bug 454761 – crash in Rhythmbox Music Player: Playing a radio station

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 454761 - crash in Rhythmbox Music Player: Playing a radio station


Summary:	crash in Rhythmbox Music Player: Playing a radio station


Status:	RESOLVED DUPLICATE of bug 436498

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.10.0
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-08 07:38 UTC by no
Modified:	2007-07-08 12:25 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description no 2007-07-08 07:38:38 UTC

What were you doing when the application crashed?
Playing a radio station


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 133332992 vsize: 133332992 resident: 32382976 share: 18788352 rss: 32382976 rss_rlim: 4294967295
CPU usage: start_time: 1183880109 rtime: 479 utime: 255 stime: 224 cutime:4 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208313296 (LWP 2571)]
[New Thread -1265964144 (LWP 2587)]
[New Thread -1276454000 (LWP 2586)]
[New Thread -1255474288 (LWP 2584)]
[New Thread -1255208048 (LWP 2583)]
[New Thread -1244324976 (LWP 2578)]
(no debugging symbols found)
0x00217402 in __kernel_vsyscall ()

+ Trace 146453

Thread 3 (Thread -1276454000 (LWP 2586))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /usr/lib/libgstbase-0.10.so.0
#5 ??
from /usr/lib/libgstreamer-0.10.so.0
#6 gst_pad_get_caps
from /usr/lib/libgstreamer-0.10.so.0
#7 ??
from /usr/lib/libgstreamer-0.10.so.0
#8 ??
from /usr/lib/libgstreamer-0.10.so.0
#9 gst_pad_get_caps
from /usr/lib/libgstreamer-0.10.so.0
#10 ??
from /usr/lib/libgstreamer-0.10.so.0
#11 ??
from /usr/lib/libgstreamer-0.10.so.0
#12 gst_pad_get_caps
from /usr/lib/libgstreamer-0.10.so.0
#13 ??
from /usr/lib/libgstreamer-0.10.so.0
#14 ??
from /usr/lib/libgstreamer-0.10.so.0
#15 gst_pad_get_caps
from /usr/lib/libgstreamer-0.10.so.0
#16 gst_pad_peer_get_caps
from /usr/lib/libgstreamer-0.10.so.0
#17 ??
from /usr/lib/libgstbase-0.10.so.0
#18 ??
from /usr/lib/libgstreamer-0.10.so.0
#19 gst_pad_get_caps
from /usr/lib/libgstreamer-0.10.so.0
#20 gst_pad_peer_get_caps
from /usr/lib/libgstreamer-0.10.so.0
#21 ??
from /usr/lib/libgstbase-0.10.so.0
#22 ??
from /usr/lib/libgstreamer-0.10.so.0
#23 gst_pad_get_caps
from /usr/lib/libgstreamer-0.10.so.0
#24 gst_pad_peer_get_caps
from /usr/lib/libgstreamer-0.10.so.0
#25 ??
from /usr/lib/libgstbase-0.10.so.0
#26 ??
from /usr/lib/libgstreamer-0.10.so.0
#27 gst_pad_get_caps
from /usr/lib/libgstreamer-0.10.so.0
#28 ??
from /usr/lib/libgstreamer-0.10.so.0
#29 ??
from /usr/lib/libgstreamer-0.10.so.0
#30 gst_pad_link
from /usr/lib/libgstreamer-0.10.so.0
#31 ??
from /usr/lib/libgstreamer-0.10.so.0
#32 gst_element_link_pads
from /usr/lib/libgstreamer-0.10.so.0
#33 ??
from /usr/lib/gstreamer-0.10/libgstplaybin.so
#34 ??
from /usr/lib/gstreamer-0.10/libgstplaybin.so
#35 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#36 g_closure_invoke
from /lib/libgobject-2.0.so.0
#37 ??
from /lib/libgobject-2.0.so.0
#38 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#39 g_signal_emit
from /lib/libgobject-2.0.so.0
#40 gst_element_no_more_pads
from /usr/lib/libgstreamer-0.10.so.0
#41 ??
from /usr/lib/gstreamer-0.10/libgstdecodebin.so
#42 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#43 g_closure_invoke
from /lib/libgobject-2.0.so.0
#44 ??
from /lib/libgobject-2.0.so.0
#45 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#46 g_signal_emit
from /lib/libgobject-2.0.so.0
#47 gst_element_no_more_pads
from /usr/lib/libgstreamer-0.10.so.0
#48 ??
from /usr/lib/gstreamer-0.10/libgstogg.so
#49 ??
from /usr/lib/gstreamer-0.10/libgstogg.so
#50 ??
from /usr/lib/gstreamer-0.10/libgstogg.so
#51 ??
from /usr/lib/gstreamer-0.10/libgstogg.so
#52 ??
from /usr/lib/libgstreamer-0.10.so.0
#53 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#54 ??
from /usr/lib/gstreamer-0.10/libgstcoreelements.so
#55 ??
from /usr/lib/gstreamer-0.10/libgstcoreelements.so
#56 ??
from /usr/lib/libgstreamer-0.10.so.0
#57 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#58 ??
from /usr/lib/libgstreamer-0.10.so.0
#59 ??
from /usr/lib/libgstreamer-0.10.so.0
#60 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#61 ??
from /usr/lib/libgstbase-0.10.so.0
#62 ??
from /usr/lib/libgstreamer-0.10.so.0
#63 ??
from /lib/libglib-2.0.so.0
#64 ??
from /lib/libglib-2.0.so.0
#65 start_thread
from /lib/libpthread.so.0
#66 clone
from /lib/libc.so.6



----------- .xsession-errors (25 sec old) ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2281
Loading "installonlyn" plugin
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2
Importing GPG key 0x4F2A6FD2 "Fedora Project <fedora@redhat.com>" from /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora
Xlib: unexpected async reply (sequence 0xb783)!
--------------------------------------------------

Comment 1 palfrey 2007-07-08 12:25:24 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 436498 ***