Bug 452196 – crash in Rhythmbox Music Player: 选择magnatune列表，播放里面的内容时

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 452196 - crash in Rhythmbox Music Player: 选择magnatune列表，播放里面的内容时


Summary:	crash in Rhythmbox Music Player: 选择magnatune列表，播放里面的内容时


Status:	RESOLVED DUPLICATE of bug 436456

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-06-29 10:21 UTC by fengyujiancheng
Modified:	2007-06-29 23:02 UTC

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

Description fengyujiancheng 2007-06-29 10:21:09 UTC

What were you doing when the application crashed?
选择magnatune列表，播放里面的内容时


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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 720519168 vsize: 720519168 resident: 76042240 share: 24358912 rss: 76042240 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183112226 rtime: 1554 utime: 1444 stime: 110 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496380480 (LWP 4956)]
[New Thread 1126189392 (LWP 4976)]
[New Thread 1126455632 (LWP 4972)]
[New Thread 1094719824 (LWP 4967)]
[New Thread 1105209680 (LWP 4964)]
(no debugging symbols found)
0x0000003781e0d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 144571

Thread 1 (Thread 46912496380480 (LWP 4956))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 PyEval_EvalFrameEx
from /usr/lib64/libpython2.5.so.1.0
#4 PyEval_EvalCodeEx
from /usr/lib64/libpython2.5.so.1.0
#5 ??
from /usr/lib64/libpython2.5.so.1.0
#6 PyObject_Call
from /usr/lib64/libpython2.5.so.1.0
#7 ??
from /usr/lib64/libpython2.5.so.1.0
#8 PyObject_Call
from /usr/lib64/libpython2.5.so.1.0
#9 PyEval_CallObjectWithKeywords
from /usr/lib64/libpython2.5.so.1.0
#10 ??
from /usr/lib64/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#11 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#12 ??
from /lib64/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#14 g_signal_emit
from /lib64/libgobject-2.0.so.0
#15 gtk_widget_size_allocate
from /usr/lib64/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#17 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#18 ??
from /lib64/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#20 g_signal_emit
from /lib64/libgobject-2.0.so.0
#21 gtk_widget_size_allocate
from /usr/lib64/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#23 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#24 ??
from /lib64/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#26 g_signal_emit
from /lib64/libgobject-2.0.so.0
#27 gtk_widget_size_allocate
from /usr/lib64/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#29 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#30 ??
from /lib64/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#32 g_signal_emit
from /lib64/libgobject-2.0.so.0
#33 gtk_widget_size_allocate
from /usr/lib64/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#35 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#36 ??
from /lib64/libgobject-2.0.so.0
#37 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#38 g_signal_emit
from /lib64/libgobject-2.0.so.0
#39 gtk_widget_size_allocate
from /usr/lib64/libgtk-x11-2.0.so.0
#40 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#41 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#42 ??
from /lib64/libgobject-2.0.so.0
#43 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#44 g_signal_emit
from /lib64/libgobject-2.0.so.0
#45 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#46 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#47 ??
from /lib64/libglib-2.0.so.0
#48 g_main_loop_run
from /lib64/libglib-2.0.so.0
#49 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#50 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
    yield self.loader.get_url (str (url), plexer.send ())
  File "/usr/lib64/rhythmbox/plugins/rb/Loader.py", line 54, in get_url
    gnomevfs.async.open (url, self.open_cb, data=("", callback, args))
TypeError: Cannot build a gnomevfs.URI
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
/usr/lib64/rhythmbox/plugins/artdisplay/__init__.py:146: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
  self.window.process_updates (True)
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-06-29 23:02:00 UTC

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 436456 ***