Bug 454717 – crash in Rhythmbox Music Player: ????

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 454717 - crash in Rhythmbox Music Player: ????


Summary:	crash in Rhythmbox Music Player: ????


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 00:49 UTC by sailing
Modified:	2007-07-08 12:25 UTC

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

Description sailing 2007-07-08 00:49:49 UTC

What were you doing when the application crashed?
播放音乐


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: 157818880 vsize: 157818880 resident: 33587200 share: 19693568 rss: 33587200 rss_rlim: 4294967295
CPU usage: start_time: 1183884569 rtime: 512 utime: 321 stime: 191 cutime:122 cstime: 8 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 -1208460752 (LWP 3146)]
[New Thread -1268782192 (LWP 3169)]
[New Thread -1258292336 (LWP 3168)]
[New Thread -1242903664 (LWP 3162)]
[New Thread -1290732656 (LWP 3161)]
[New Thread -1279272048 (LWP 3156)]
(no debugging symbols found)
0x00572402 in __kernel_vsyscall ()

+ Trace 146422

Thread 3 (Thread -1258292336 (LWP 3168))

#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/libgstreamer-0.10.so.0
#56 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#57 ??
from /usr/lib/libgstreamer-0.10.so.0
#58 ??
from /usr/lib/libgstreamer-0.10.so.0
#59 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#60 ??
from /usr/lib/libgstbase-0.10.so.0
#61 ??
from /usr/lib/libgstreamer-0.10.so.0
#62 ??
from /lib/libglib-2.0.so.0
#63 ??
from /lib/libglib-2.0.so.0
#64 start_thread
from /lib/libpthread.so.0
#65 clone
from /lib/libc.so.6



----------- .xsession-errors (14 sec old) ---------------------
Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
GTK Panel of SCIM 1.4.5
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2947
** (gnome-session:2947): WARNING **: Esound failed to start.
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Xlib: unexpected async reply (sequence 0x5976)!
--------------------------------------------------

Comment 1 palfrey 2007-07-08 12:25:11 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 ***