Bug 394696 – crash in Rhythmbox Music Player: Just trying to start rhy...

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 394696 - crash in Rhythmbox Music Player: Just trying to start rhy...


Summary:	crash in Rhythmbox Music Player: Just trying to start rhy...


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:	2007-01-09 16:58 UTC by stressonthesky
Modified:	2007-01-10 01:41 UTC

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

Description stressonthesky 2007-01-09 16:58:35 UTC

What were you doing when the application crashed?
Just trying to start rhythmbox


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

Memory status: size: 53383168 vsize: 0 resident: 53383168 share: 0 rss: 22384640 rss_rlim: 0
CPU usage: start_time: 1168361912 rtime: 0 utime: 121 stime: 0 cutime:112 cstime: 0 timeout: 9 it_real_value: 0 frequency: 4

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

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

+ Trace 100741

Thread 1 (Thread -1228195648 (LWP 13615))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#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
from /usr/lib/libpython2.4.so.1.0
#10 PyEval_EvalFrame
from /usr/lib/libpython2.4.so.1.0
#11 PyEval_EvalFrame
from /usr/lib/libpython2.4.so.1.0
#12 PyEval_EvalFrame
from /usr/lib/libpython2.4.so.1.0
#13 PyEval_EvalCodeEx
from /usr/lib/libpython2.4.so.1.0
#14 PyClassMethod_New
from /usr/lib/libpython2.4.so.1.0
#15 PyObject_Call
from /usr/lib/libpython2.4.so.1.0
#16 PyClass_IsSubclass
from /usr/lib/libpython2.4.so.1.0
#17 PyObject_Call
from /usr/lib/libpython2.4.so.1.0
#18 PyObject_CallMethod
from /usr/lib/libpython2.4.so.1.0
#19 rb_python_object_get_type
#20 rb_python_object_get_type
#21 rb_plugin_activate
#22 rb_plugins_engine_activate_plugin
#23 rb_plugins_engine_init
#24 rb_uri_handle_recursively
#25 gnome_vfs_directory_open_from_uri
from /usr/lib/libgnomevfs-2.so.0
#26 gnome_vfs_directory_open_from_uri
from /usr/lib/libgnomevfs-2.so.0
#27 gnome_vfs_directory_visit
from /usr/lib/libgnomevfs-2.so.0
#28 rb_uri_handle_recursively
#29 rb_plugins_engine_init
#30 rb_shell_new
#31 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#32 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#33 g_object_new
from /usr/lib/libgobject-2.0.so.0
#34 rb_shell_new
#35 main
#0 __kernel_vsyscall

Comment 1 Alex Lancaster 2007-01-10 01:41:23 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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