Bug 468712 – crash in Rhythmbox Music Player: dlb clicked on song

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 468712 - crash in Rhythmbox Music Player: dlb clicked on song


Summary:	crash in Rhythmbox Music Player: dlb clicked on song


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-08-21 02:09 UTC by AndyHowell
Modified:	2007-08-21 12:37 UTC

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

Description AndyHowell 2007-08-21 02:09:23 UTC

What were you doing when the application crashed?
dlb clicked on song



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.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 741130240 vsize: 741130240 resident: 43069440 share: 21364736 rss: 43069440 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187661118 rtime: 886 utime: 794 stime: 92 cutime:2 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912534553040 (LWP 3356)]
[New Thread 1147169104 (LWP 3951)]
[New Thread 1136679248 (LWP 3950)]
[New Thread 1126189392 (LWP 3948)]
[New Thread 1115699536 (LWP 3947)]
[New Thread 1105209680 (LWP 3945)]
[New Thread 1094719824 (LWP 3944)]
[New Thread 1388435792 (LWP 3941)]
[New Thread 1409415504 (LWP 3939)]
[New Thread 1084229968 (LWP 3363)]
(no debugging symbols found)
0x00002aaaac3f92e6 in poll () from /lib64/libc.so.6

+ Trace 156715

Thread 2 (Thread 1147169104 (LWP 3951))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 __assert_fail
from /lib64/libc.so.6
#6 PyEval_EvalFrameEx
from /usr/lib64/libpython2.5.so.1.0
#7 PyEval_EvalCodeEx
from /usr/lib64/libpython2.5.so.1.0
#8 ??
from /usr/lib64/libpython2.5.so.1.0
#9 PyObject_Call
from /usr/lib64/libpython2.5.so.1.0
#10 ??
from /usr/lib64/libpython2.5.so.1.0
#11 PyObject_CallFunction
from /usr/lib64/libpython2.5.so.1.0
#12 PyErr_WarnEx
from /usr/lib64/libpython2.5.so.1.0
#13 ??
from /usr/lib64/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#14 g_logv
from /lib64/libglib-2.0.so.0
#15 g_log
from /lib64/libglib-2.0.so.0
#16 g_type_check_instance_cast
from /lib64/libgobject-2.0.so.0
#17 ??
from /usr/lib64/gstreamer-0.10/libgstgnomevfs.so
#18 gnome_vfs_module_callback_invoke
from /usr/lib64/libgnomevfs-2.so.0
#19 ??
from /usr/lib64/gnome-vfs-2.0/modules/libhttp.so
#20 ??
from /usr/lib64/gnome-vfs-2.0/modules/libhttp.so
#21 ne_begin_request
from /usr/lib64/gnome-vfs-2.0/modules/libhttp.so
#22 ??
from /usr/lib64/gnome-vfs-2.0/modules/libhttp.so
#23 ??
from /usr/lib64/gnome-vfs-2.0/modules/libhttp.so
#24 ??
from /usr/lib64/gnome-vfs-2.0/modules/libhttp.so
#25 gnome_vfs_open_uri_cancellable
from /usr/lib64/libgnomevfs-2.so.0
#26 ??
from /usr/lib64/libgnomevfs-2.so.0
#27 ??
from /usr/lib64/libgnomevfs-2.so.0
#28 ??
from /usr/lib64/libgnomevfs-2.so.0
#29 ??
from /lib64/libglib-2.0.so.0
#30 ??
from /lib64/libglib-2.0.so.0
#31 start_thread
from /lib64/libpthread.so.0
#32 clone
from /lib64/libc.so.6

Comment 1 Jonathan Matthew 2007-08-21 12:37:21 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 ***