GNOME Bugzilla – Bug 389334
crash in Rhythmbox Music Player:
Last modified: 2006-12-25 03:12:44 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.18-1.2868.fc6 #1 SMP Fri Dec 15 17:32:54 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". ** (bug-buddy:3392): WARNING **: Couldn't load icon for Open Folder Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3400024 (Music Play) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". -------------------------------------------------- Memory status: size: 99799040 vsize: 0 resident: 99799040 share: 0 rss: 17510400 rss_rlim: 0 CPU usage: start_time: 1167009928 rtime: 0 utime: 46 stime: 0 cutime:43 cstime: 0 timeout: 3 it_real_value: 0 frequency: 2 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 -1208719648 (LWP 3402)] [New Thread -1267070064 (LWP 3406)] (no debugging symbols found) 0x00af1402 in __kernel_vsyscall ()
+ Trace 96775
Thread 2 (Thread -1267070064 (LWP 3406))
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 350304 ***