Bug 452120 – crash in Rhythmbox Music Player: browsing 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 452120 - crash in Rhythmbox Music Player: browsing magnatune


Summary:	crash in Rhythmbox Music Player: browsing 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 02:34 UTC by wrenchin.dodges
Modified:	2007-06-29 22:57 UTC

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

Description wrenchin.dodges 2007-06-29 02:34:31 UTC

What were you doing when the application crashed?
browsing magnatune


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 288399360 vsize: 288399360 resident: 176230400 share: 26456064 rss: 176230400 rss_rlim: 4294967295
CPU usage: start_time: 1183084212 rtime: 12445 utime: 12179 stime: 266 cutime:8 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208706512 (LWP 3299)]
[New Thread -1328931952 (LWP 3444)]
[New Thread -1265992816 (LWP 3324)]
[New Thread -1253188720 (LWP 3310)]
[New Thread -1255146608 (LWP 3306)]
(no debugging symbols found)
0x00d46402 in __kernel_vsyscall ()

+ Trace 144507

Thread 1 (Thread -1208706512 (LWP 3299))

#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 PyObject_RichCompareBool
from /usr/lib/libpython2.5.so.1.0
#6 ??
from /usr/lib/libpython2.5.so.1.0
#7 PyDict_GetItem
from /usr/lib/libpython2.5.so.1.0
#8 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#9 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#10 ??
from /lib/libexpat.so.0
#11 ??
from /lib/libexpat.so.0
#12 ??
from /lib/libexpat.so.0
#13 ??
from /lib/libexpat.so.0
#14 XML_ParseBuffer
from /lib/libexpat.so.0
#15 XML_Parse
from /lib/libexpat.so.0
#16 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#17 PyCFunction_Call
from /usr/lib/libpython2.5.so.1.0
#18 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#19 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#20 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#21 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#22 PyEval_EvalCodeEx
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 ??
from /usr/lib/libpython2.5.so.1.0
#26 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#27 ??
from /usr/lib/libpython2.5.so.1.0
#28 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#29 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#30 PyObject_CallObject
from /usr/lib/libpython2.5.so.1.0
#31 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#32 ??
from /lib/libglib-2.0.so.0
#33 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#34 ??
from /lib/libglib-2.0.so.0
#35 g_main_loop_run
from /lib/libglib-2.0.so.0
#36 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#37 main
#0 __kernel_vsyscall



----------- .xsession-errors (8 sec old) ---------------------
** 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
** 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:223: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
  parser.Parse(string, True)
/usr/lib/python2.5/site-packages/_xmlplus/dom/expatbuilder.py:223: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
  parser.Parse(string, True)
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-06-29 22:57:45 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 ***