Bug 442825 – crash in Rhythmbox Music Player: firefox

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


Summary:	crash in Rhythmbox Music Player: firefox


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-01 07:55 UTC by gpfei96
Modified:	2007-06-03 10:35 UTC

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

Description gpfei96 2007-06-01 07:55:39 UTC

What were you doing when the application crashed?
firefox


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: 269029376 vsize: 269029376 resident: 94097408 share: 16089088 rss: 94097408 rss_rlim: 4294967295
CPU usage: start_time: 1180683697 rtime: 7823 utime: 7075 stime: 748 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 -1208600016 (LWP 29343)]
[New Thread -1321596016 (LWP 29790)]
[New Thread -1300350064 (LWP 29763)]
[New Thread -1267733616 (LWP 29416)]
(no debugging symbols found)
0x00467402 in __kernel_vsyscall ()

+ Trace 137177

Thread 1 (Thread -1208600016 (LWP 29343))

#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 PyObject_CallObject
from /usr/lib/libpython2.5.so.1.0
#12 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#13 g_closure_invoke
from /lib/libgobject-2.0.so.0
#14 ??
from /lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#16 g_signal_emit
from /lib/libgobject-2.0.so.0
#17 gtk_widget_size_allocate
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#20 ??
from /lib/libgobject-2.0.so.0
#21 g_closure_invoke
from /lib/libgobject-2.0.so.0
#22 ??
from /lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#24 g_signal_emit
from /lib/libgobject-2.0.so.0
#25 gtk_widget_size_allocate
from /usr/lib/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib/libgtk-x11-2.0.so.0
#27 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#28 ??
from /lib/libgobject-2.0.so.0
#29 g_closure_invoke
from /lib/libgobject-2.0.so.0
#30 ??
from /lib/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#32 g_signal_emit
from /lib/libgobject-2.0.so.0
#33 gtk_widget_size_allocate
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#36 ??
from /lib/libgobject-2.0.so.0
#37 g_closure_invoke
from /lib/libgobject-2.0.so.0
#38 ??
from /lib/libgobject-2.0.so.0
#39 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#40 g_signal_emit
from /lib/libgobject-2.0.so.0
#41 gtk_widget_size_allocate
from /usr/lib/libgtk-x11-2.0.so.0
#42 ??
from /usr/lib/libgtk-x11-2.0.so.0
#43 g_cclosure_marshal_VOID__BOXED
from /lib/libgobject-2.0.so.0
#44 ??
from /lib/libgobject-2.0.so.0
#45 g_closure_invoke
from /lib/libgobject-2.0.so.0
#46 ??
from /lib/libgobject-2.0.so.0
#47 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#48 g_signal_emit
from /lib/libgobject-2.0.so.0
#49 gtk_widget_size_allocate
from /usr/lib/libgtk-x11-2.0.so.0
#50 gtk_container_resize_children
from /usr/lib/libgtk-x11-2.0.so.0
#51 ??
from /usr/lib/libgtk-x11-2.0.so.0
#52 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#53 ??
from /lib/libgobject-2.0.so.0
#54 g_closure_invoke
from /lib/libgobject-2.0.so.0
#55 ??
from /lib/libgobject-2.0.so.0
#56 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#57 g_signal_emit
from /lib/libgobject-2.0.so.0
#58 gtk_container_check_resize
from /usr/lib/libgtk-x11-2.0.so.0
#59 ??
from /usr/lib/libgtk-x11-2.0.so.0
#60 ??
from /lib/libglib-2.0.so.0
#61 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#62 ??
from /lib/libglib-2.0.so.0
#63 g_main_loop_run
from /lib/libglib-2.0.so.0
#64 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#65 main
#0 __kernel_vsyscall



----------- .xsession-errors (7 sec old) ---------------------
warning: .dynamic section for "/usr/lib/libogg.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgstaudio-0.10.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libvorbisenc.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libvorbis.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Philip Withnall 2007-06-03 10:35:46 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 ***