Bug 460686 – crash in Rhythmbox Music Player: trying to play a magnatu...

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 460686 - crash in Rhythmbox Music Player: trying to play a magnatu...


Summary:	crash in Rhythmbox Music Player: trying to play a magnatu...


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-07-26 18:20 UTC by rmorin128
Modified:	2007-07-28 11:32 UTC

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

Description rmorin128 2007-07-26 18:20:16 UTC

What were you doing when the application crashed?
trying to play a magnatune track


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Neutrino
Icon Theme: Bluecurve

Memory status: size: 292909056 vsize: 292909056 resident: 190390272 share: 39534592 rss: 190390272 rss_rlim: 4294967295
CPU usage: start_time: 1185473145 rtime: 16392 utime: 15621 stime: 771 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 -1208636880 (LWP 12360)]
[New Thread -1307030640 (LWP 12554)]
[New Thread -1261335664 (LWP 12396)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 150760

Thread 1 (Thread -1208636880 (LWP 12360))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 __assert_fail
from /lib/libc.so.6
#8 PyEval_EvalCodeEx
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 ??
from /usr/lib/libpython2.5.so.1.0
#12 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#13 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#14 PyInstance_New
from /usr/lib/libpython2.5.so.1.0
#15 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#16 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#17 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#18 ??
from /usr/lib/libpython2.5.so.1.0
#19 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#20 ??
from /usr/lib/libpython2.5.so.1.0
#21 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#22 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#23 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#24 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#25 ??
from /lib/libexpat.so.0
#26 ??
from /lib/libexpat.so.0
#27 ??
from /lib/libexpat.so.0
#28 ??
from /lib/libexpat.so.0
#29 XML_ParseBuffer
from /lib/libexpat.so.0
#30 XML_Parse
from /lib/libexpat.so.0
#31 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#32 PyCFunction_Call
from /usr/lib/libpython2.5.so.1.0
#33 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#34 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#35 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#36 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#37 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#38 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#39 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#40 ??
from /usr/lib/libpython2.5.so.1.0
#41 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#42 ??
from /usr/lib/libpython2.5.so.1.0
#43 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#44 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#45 PyObject_CallObject
from /usr/lib/libpython2.5.so.1.0
#46 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#47 ??
from /lib/libglib-2.0.so.0
#48 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#49 ??
from /lib/libglib-2.0.so.0
#50 g_main_loop_run
from /lib/libglib-2.0.so.0
#51 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#52 main
#0 __kernel_vsyscall



----------- .xsession-errors (548 sec old) ---------------------
(rhythmbox:12360): Rhythmbox-CRITICAL **: egg_sequence_iter_get_position: assertion `iter != NULL' failed
(rhythmbox:12360): Rhythmbox-CRITICAL **: egg_sequence_iter_get_position: assertion `iter != NULL' failed
(rhythmbox:12360): Rhythmbox-CRITICAL **: egg_sequence_iter_get_position: assertion `iter != NULL' failed
(rhythmbox:12360): Rhythmbox-CRITICAL **: egg_sequence_iter_get_position: assertion `iter != NULL' failed
(rhythmbox:12360): Rhythmbox-CRITICAL **: egg_sequence_iter_get_position: assertion `iter != NULL' failed
(rhythmbox:12360): Rhythmbox-CRITICAL **: egg_sequence_iter_get_position: assertion `iter != NULL' failed
(rhythmbox:12360): Rhythmbox-CRITICAL **: egg_sequence_iter_get_position: assertion `iter != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-07-28 11:32:01 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 ***