Bug 450492 – crash in Rhythmbox Music Player: opened magnatune and dou...

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 450492 - crash in Rhythmbox Music Player: opened magnatune and dou...


Summary:	crash in Rhythmbox Music Player: opened magnatune and dou...


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-23 23:16 UTC by ll15039
Modified:	2007-06-23 23:50 UTC

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

Description ll15039 2007-06-23 23:16:44 UTC

What were you doing when the application crashed?
opened magnatune and double clicked on one of their songs


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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 158363648 vsize: 158363648 resident: 48689152 share: 19398656 rss: 48689152 rss_rlim: 4294967295
CPU usage: start_time: 1182640299 rtime: 4843 utime: 4345 stime: 498 cutime:4 cstime: 4 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 -1208767952 (LWP 29335)]
[New Thread -1281922160 (LWP 29388)]
[New Thread -1323881584 (LWP 29373)]
[New Thread -1224483952 (LWP 29353)]
[New Thread -1246520432 (LWP 29347)]
(no debugging symbols found)
0x009c7402 in __kernel_vsyscall ()

+ Trace 143234

Thread 1 (Thread -1208767952 (LWP 29335))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 PyObject_RichCompare
from /usr/lib/libpython2.5.so.1.0
#5 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#6 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#7 ??
from /usr/lib/libpython2.5.so.1.0
#8 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#9 ??
from /usr/lib/libpython2.5.so.1.0
#10 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#11 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#12 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#13 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#14 ??
from /lib/libexpat.so.0
#15 ??
from /lib/libexpat.so.0
#16 ??
from /lib/libexpat.so.0
#17 ??
from /lib/libexpat.so.0
#18 XML_ParseBuffer
from /lib/libexpat.so.0
#19 XML_Parse
from /lib/libexpat.so.0
#20 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#21 PyCFunction_Call
from /usr/lib/libpython2.5.so.1.0
#22 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#23 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#24 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#25 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#26 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#27 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#28 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#29 ??
from /usr/lib/libpython2.5.so.1.0
#30 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#31 ??
from /usr/lib/libpython2.5.so.1.0
#32 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#33 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#34 PyObject_CallObject
from /usr/lib/libpython2.5.so.1.0
#35 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#36 ??
from /lib/libglib-2.0.so.0
#37 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#38 ??
from /lib/libglib-2.0.so.0
#39 g_main_loop_run
from /lib/libglib-2.0.so.0
#40 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#41 main
#0 __kernel_vsyscall



----------- .xsession-errors (20 sec old) ---------------------
    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/lib/python2.5/site-packages/_xmlplus/dom/expatbuilder.py:812: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
  assert curNode.nodeName == name, \
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x64
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-06-23 23:50:10 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 ***