Bug 382322 – crash in Rhythmbox Music Player: launching rhythmbox

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 382322 - crash in Rhythmbox Music Player: launching rhythmbox


Summary:	crash in Rhythmbox Music Player: launching rhythmbox


Status:	RESOLVED DUPLICATE of bug 362488

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.9.6
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-04 18:05 UTC by steve
Modified:	2006-12-04 21:38 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description steve 2006-12-04 18:05:33 UTC

What were you doing when the application crashed?
launching rhythmbox


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 54378496 vsize: 0 resident: 54378496 share: 0 rss: 22274048 rss_rlim: 0
CPU usage: start_time: 1165255445 rtime: 0 utime: 248 stime: 0 cutime:220 cstime: 0 timeout: 28 it_real_value: 0 frequency: 19

Backtrace was generated from '/usr/local/bin/rhythmbox'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1229092672 (LWP 10970)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 91573

Thread 1 (Thread -1229092672 (LWP 10970))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 874
#3 <signal handler called>
#4 init_gobject
from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
#5 init_gobject
from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
#6 init_gobject
from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
#7 init_gobject
from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
#8 init_gobject
from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
#9 PyCFunction_Call
at ../Objects/methodobject.c line 108
#10 PyEval_EvalFrame
at ../Python/ceval.c line 3568
#11 PyEval_EvalCodeEx
at ../Python/ceval.c line 2741
#12 function_call
at ../Objects/funcobject.c line 548
#13 PyObject_Call
at ../Objects/abstract.c line 1795
#14 instancemethod_call
at ../Objects/classobject.c line 2532
#15 PyObject_Call
at ../Objects/abstract.c line 1795
#16 PyObject_CallMethod
#17 call_python_method
at rb-python-plugin.c line 48
#18 impl_activate
at rb-python-plugin.c line 118
#19 rb_plugin_activate
at rb-plugin.c line 153
#20 rb_plugins_engine_activate_plugin
at rb-plugins-engine.c line 489
#21 rb_plugins_engine_load_cb
at rb-plugins-engine.c line 290
#22 rb_uri_handle_recursively_cb
at rb-file-helpers.c line 662
#23 directory_visit_internal
at gnome-vfs-directory.c line 401
#24 gnome_vfs_directory_visit
at gnome-vfs-directory.c line 535
#25 rb_uri_handle_recursively
at rb-file-helpers.c line 690
#26 rb_plugins_engine_init
at rb-plugins-engine.c line 299
#27 rb_shell_constructor
at rb-shell.c line 1354
#28 IA__g_object_newv
at gobject.c line 937
#29 IA__g_object_new_valist
at gobject.c line 1022
#30 IA__g_object_new
at gobject.c line 795
#31 rb_shell_new
at rb-shell.c line 958
#32 main
at main.c line 305
#0 __kernel_vsyscall

Comment 1 Steve Frécinaux 2006-12-04 18:11:29 UTC

A priori this crash is due to the AlarmClock plugin, but it shouldn't crash at first hand, even if the python plugin makes bad things...

Comment 2 Jonathan Matthew 2006-12-04 21:38:02 UTC

Apparently it's due to something weird/bad in the rhythmbox class hierarchy.



*** This bug has been marked as a duplicate of 362488 ***