Bug 459213 – crash in Rhythmbox Music Player: Started Rhythmbox Music ...

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 459213 - crash in Rhythmbox Music Player: Started Rhythmbox Music ...


Summary:	crash in Rhythmbox Music Player: Started Rhythmbox Music ...


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-22 05:12 UTC by jjones277
Modified:	2007-07-24 12:06 UTC

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

Description jjones277 2007-07-22 05:12:43 UTC

What were you doing when the application crashed?
Started Rhythmbox Music Player on newly installed Fedora machine.


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

Memory status: size: 139419648 vsize: 139419648 resident: 48754688 share: 17334272 rss: 48754688 rss_rlim: 4294967295
CPU usage: start_time: 1185081031 rtime: 1518 utime: 1459 stime: 59 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 -1209128400 (LWP 19071)]
[New Thread -1363731568 (LWP 19124)]
[New Thread -1246758000 (LWP 19081)]
[New Thread -1233831024 (LWP 19076)]
(no debugging symbols found)
0x00d10402 in __kernel_vsyscall ()

+ Trace 149730

Thread 1 (Thread -1209128400 (LWP 19071))

#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 (2393 sec old) ---------------------
(gnome-background-properties:3964): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
(gnome-background-properties:3964): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
(gnome-background-properties:3964): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed
(gnome-background-properties:3964): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
(gnome-background-properties:3964): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
(gnome-background-properties:3964): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed
(gnome-background-properties:3964): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-07-24 12:06:12 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 ***