Bug 460144 – crash in Rhythmbox Music Player:

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


Summary:	crash in Rhythmbox Music Player:


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-25 08:42 UTC by john
Modified:	2007-07-25 11:46 UTC

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

Description john 2007-07-25 08:42:22 UTC

What were you doing when the application crashed?



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

Memory status: size: 125591552 vsize: 125591552 resident: 51712000 share: 23666688 rss: 51712000 rss_rlim: 4294967295
CPU usage: start_time: 1185352867 rtime: 963 utime: 921 stime: 42 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 -1209050576 (LWP 2871)]
[New Thread -1233753200 (LWP 2876)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 150394

Thread 1 (Thread -1209050576 (LWP 2871))

#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_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#18 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#19 PyEval_EvalCodeEx
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 ??
from /usr/lib/libpython2.5.so.1.0
#23 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#24 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#25 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#26 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#27 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#28 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#29 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#30 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#31 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#32 ??
from /usr/lib/libpython2.5.so.1.0
#33 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#34 ??
from /usr/lib/libpython2.5.so.1.0
#35 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#36 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#37 PyObject_CallObject
from /usr/lib/libpython2.5.so.1.0
#38 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#39 ??
from /lib/libglib-2.0.so.0
#40 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#41 ??
from /lib/libglib-2.0.so.0
#42 g_main_loop_run
from /lib/libglib-2.0.so.0
#43 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#44 main
#0 __kernel_vsyscall



----------- .xsession-errors (9 sec old) ---------------------
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
sys:1: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
sys:1: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
** 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
rhythmbox: Python/ceval.c:2626: PyEval_EvalCodeEx: Assertion `tstate != ((void *)0)' failed.
/usr/lib/python2.5/site-packages/_xmlplus/dom/minidom.py:1419: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
  return Document()
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-07-25 11:46:30 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 ***