GNOME Bugzilla – Bug 444702
crash in Rhythmbox Music Player:
Last modified: 2007-06-06 22:48:33 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks_Cairo-GNOME Icon Theme: Fedora Memory status: size: 171159552 vsize: 171159552 resident: 37007360 share: 19951616 rss: 37007360 rss_rlim: 4294967295 CPU usage: start_time: 1181134218 rtime: 67 utime: 62 stime: 5 cutime:2 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209169360 (LWP 3659)] [New Thread -1240712304 (LWP 3665)] (no debugging symbols found) 0x00e43402 in __kernel_vsyscall ()
+ Trace 138734
Thread 1 (Thread -1209169360 (LWP 3659))
----------- .xsession-errors (7 sec old) --------------------- (rhythmbox:3659): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %e (rhythmbox:3659): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %e (rhythmbox:3659): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %e (rhythmbox:3659): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %e (rhythmbox:3659): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %e (rhythmbox:3659): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %e (rhythmbox:3659): Rhythmb ...Too much output, ignoring rest... --------------------------------------------------
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 409540 ***