Bug 451024 – crash in Rhythmbox Music Player: playing the magnatune pl...

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 451024 - crash in Rhythmbox Music Player: playing the magnatune pl...


Summary:	crash in Rhythmbox Music Player: playing the magnatune pl...


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-25 19:29 UTC by hughc
Modified:	2007-06-25 22:34 UTC

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

Description hughc 2007-06-25 19:29:10 UTC

What were you doing when the application crashed?
playing the magnatune playlist


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

Memory status: size: 128593920 vsize: 128593920 resident: 54345728 share: 24408064 rss: 54345728 rss_rlim: 4294967295
CPU usage: start_time: 1182799630 rtime: 2253 utime: 2126 stime: 127 cutime:4 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 -1208743376 (LWP 6049)]
[New Thread -1331729520 (LWP 6137)]
[New Thread -1237320816 (LWP 6056)]
(no debugging symbols found)
0x005d1402 in __kernel_vsyscall ()

+ Trace 143661

Thread 1 (Thread -1208743376 (LWP 6049))

#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 ??
from /usr/lib/libpython2.5.so.1.0
#9 ??
from /usr/lib/libpython2.5.so.1.0
#10 ??
from /usr/lib/libpython2.5.so.1.0
#11 _PyObject_GC_Malloc
from /usr/lib/libpython2.5.so.1.0
#12 _PyObject_GC_New
from /usr/lib/libpython2.5.so.1.0
#13 ??
from /usr/lib/libpython2.5.so.1.0
#14 PyObject_GetIter
from /usr/lib/libpython2.5.so.1.0
#15 PyEval_EvalFrameEx
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_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#20 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#21 ??
from /usr/lib/libpython2.5.so.1.0
#22 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#23 ??
from /usr/lib/libpython2.5.so.1.0
#24 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#25 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#26 PyObject_CallObject
from /usr/lib/libpython2.5.so.1.0
#27 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#28 ??
from /lib/libglib-2.0.so.0
#29 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#30 ??
from /lib/libglib-2.0.so.0
#31 g_main_loop_run
from /lib/libglib-2.0.so.0
#32 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#33 main
#0 __kernel_vsyscall

Comment 1 Jonathan Matthew 2007-06-25 22:34:47 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 ***