GNOME Bugzilla – Bug 374542
crash in Rhythmbox Music Player:
Last modified: 2006-11-13 07:00:51 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.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Disabled ----------- .xsession-errors (9805 sec old) --------------------- (evolution:5558): libebook-WARNING **: invalid escape, passing it through (evolution:5558): libebook-WARNING **: invalid escape, passing it through (evolution:5558): libebook-WARNING **: invalid escape, passing it through (firestarter:4791): GLib-CRITICAL **: g_str_has_suffix: assertion `str != NULL' failed (firestarter:4791): GLib-CRITICAL **: g_str_has_suffix: assertion `str != NULL' failed (firestarter:4791): GLib-CRITICAL **: g_str_has_suffix: assertion `str != NULL' failed (firestarter:4791): GLib-CRITICAL **: g_str_has_suffix: assertion `str != NULL' failed (firestarter:4791): GLib-CRITICAL **: g_str_has_suffix: assertion `str != NULL' failed -------------------------------------------------- Memory status: size: 187277312 vsize: 0 resident: 187277312 share: 0 rss: 31100928 rss_rlim: 0 CPU usage: start_time: 1163377579 rtime: 0 utime: 20406 stime: 0 cutime:17526 cstime: 0 timeout: 2880 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 -1209223456 (LWP 28445)] [New Thread 146152336 (LWP 31786)] [New Thread 55778192 (LWP 31784)] [New Thread 66268048 (LWP 31783)] [New Thread 76757904 (LWP 31782)] [New Thread 30571408 (LWP 28454)] (no debugging symbols found) 0x006f5402 in __kernel_vsyscall ()
+ Trace 85963
Thread 3 (Thread 55778192 (LWP 31784))
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 348455 ***