Bug 454347 – crash in Rhythmbox Music Player: rien

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 454347 - crash in Rhythmbox Music Player: rien


Summary:	crash in Rhythmbox Music Player: rien


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-06 17:59 UTC by maehryss
Modified:	2007-07-07 22:44 UTC

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

Description maehryss 2007-07-06 17:59:45 UTC

What were you doing when the application crashed?
rien


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: 251748352 vsize: 251748352 resident: 161611776 share: 20287488 rss: 161611776 rss_rlim: 4294967295
CPU usage: start_time: 1183737131 rtime: 3322 utime: 3179 stime: 143 cutime:2 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 -1209009616 (LWP 3044)]
[New Thread -1289069680 (LWP 3144)]
[New Thread -1322263664 (LWP 3099)]
[New Thread -1267348592 (LWP 3075)]
[New Thread -1220863088 (LWP 3049)]
(no debugging symbols found)
0x00907402 in __kernel_vsyscall ()

+ Trace 146177

Thread 1 (Thread -1209009616 (LWP 3044))

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



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

Comment 1 Jonathan Matthew 2007-07-07 22:44:55 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 ***