GNOME Bugzilla – Bug 375107
crash in Rhythmbox Music Player:
Last modified: 2006-11-16 00:52:37 UTC
What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.17-1.2187_FC5smp #1 SMP Mon Sep 11 01:32:34 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Disabled ----------- .xsession-errors (486 sec old) --------------------- Introspect error: The name edu.duke.linux.yum was not provided by any .service files Unable to connect to yum-updatesd... ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name (gnome-panel:2637): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -187 and height 24 Unable to connect to yum-updatesd... Unable to connect to yum-updatesd... Unable to connect to yum-updatesd... Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800022 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Unable to connect to yum-updatesd... Unable to connect to yum-updatesd... Unable to connect to yum-updatesd... Unable to connect to yum-updatesd... Unable to connect to yum-updatesd... -------------------------------------------------- Memory status: size: 177635328 vsize: 0 resident: 177635328 share: 0 rss: 41156608 rss_rlim: 0 CPU usage: start_time: 1163510290 rtime: 0 utime: 6738 stime: 0 cutime:6397 cstime: 0 timeout: 341 it_real_value: 0 frequency: 4 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 -1208465696 (LWP 4314)] [New Thread -1326867568 (LWP 9935)] [New Thread -1240040560 (LWP 9934)] [New Thread -1295004784 (LWP 9920)] [New Thread -1315984496 (LWP 9916)] [New Thread -1263535216 (LWP 4471)] [New Thread -1250952304 (LWP 4452)] [New Thread -1284514928 (LWP 4451)] [New Thread -1222026352 (LWP 4320)] (no debugging symbols found) 0x00962402 in __kernel_vsyscall ()
+ Trace 86360
Thread 2 (Thread -1326867568 (LWP 9935))
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug. Also, unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
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 375093 ***