Bug 414813 – crash in Rhythmbox Music Player:

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


Summary:	crash in Rhythmbox Music Player:


Status:	RESOLVED DUPLICATE of bug 362488

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-05 07:34 UTC by usinglinux365
Modified:	2007-03-05 08:11 UTC

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

Description usinglinux365 2007-03-05 07:34:35 UTC

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2911.6.4.fc6 #1 SMP Sat Feb 24 14:03:48 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 392654848 vsize: 392654848 resident: 26570752 share: 14462976 rss: 26570752 rss_rlim: -1
CPU usage: start_time: 1173080069 rtime: 63 utime: 56 stime: 7 cutime:11 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912498534144 (LWP 3579)]
(no debugging symbols found)
0x0000003a2be0d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 115934

Thread 1 (Thread 46912498534144 (LWP 3579))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
from /usr/lib64/python2.4/site-packages/gtk-2.0/gobject/_gobject.so
#4 ??
from /usr/lib64/python2.4/site-packages/gtk-2.0/gobject/_gobject.so
#5 ??
from /usr/lib64/python2.4/site-packages/gtk-2.0/gobject/_gobject.so
#6 ??
from /usr/lib64/python2.4/site-packages/gtk-2.0/gobject/_gobject.so
#7 PyEval_EvalFrame
from /usr/lib64/libpython2.4.so.1.0
#8 PyEval_EvalCodeEx
from /usr/lib64/libpython2.4.so.1.0
#9 PyClassMethod_New
from /usr/lib64/libpython2.4.so.1.0
#10 PyObject_Call
from /usr/lib64/libpython2.4.so.1.0
#11 PyClass_IsSubclass
from /usr/lib64/libpython2.4.so.1.0
#12 PyObject_Call
from /usr/lib64/libpython2.4.so.1.0
#13 PyObject_CallMethod
from /usr/lib64/libpython2.4.so.1.0
#14 rb_python_object_get_type
#15 rb_python_object_get_type
#16 rb_plugins_engine_activate_plugin
#17 rb_uri_handle_recursively
#18 gnome_vfs_directory_close
from /usr/lib64/libgnomevfs-2.so.0
#19 gnome_vfs_directory_visit
from /usr/lib64/libgnomevfs-2.so.0
#20 rb_uri_handle_recursively
#21 rb_plugins_engine_init
#22 rb_shell_new
#23 g_object_newv
from /lib64/libgobject-2.0.so.0
#24 g_object_new_valist
from /lib64/libgobject-2.0.so.0
#25 g_object_new
from /lib64/libgobject-2.0.so.0
#26 rb_shell_new
#27 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (30 sec old) ---------------------
localuser:lincmpuser being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3246
** (eggcups:3358): WARNING **: IPP request failed with status 1030
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x45 specified for 0xc00a44 ().
(rhythmbox:3499): libglade-WARNING **: could not find glade file '/usr/lib64/rhythmbox/plugins/rb-alarmclock.glade'
TypeError: Cannot create a consistent method resolution
order (MRO) for bases TreeModel, GInterface, TreeDragSource, __main__.RbTreeDragDest
** (bug-buddy:3503): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Comment 1 Alex Lancaster 2007-03-05 08:11:04 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 362488 ***