GNOME Bugzilla – Bug 392637
crash in Rhythmbox Music Player: Trying to open Rhythmbox...
Last modified: 2007-01-05 08:15:03 UTC
What were you doing when the application crashed? Trying to open Rhythmbox on FC6. Program fails to open. Tried remove and reinstall, but that did not work. 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.2869.fc6 #1 SMP Wed Dec 20 14:51:46 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- (nautilus:2758): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists. (nautilus:2758): Eel-WARNING **: Trying to add a callback for preferences/background_set that already exists. (nautilus:2758): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists. (nautilus:2758): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists. (rhythmbox:4148): Rhythmbox-WARNING **: Couldn't get menu widget for /BrowserSourcePopup RhythmDB-ERROR **: file rhythmdb-tree.c: line 248 (rhythmdb_tree_parser_start_element): should not be reached aborting... ** (bug-buddy:4261): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 80318464 vsize: 0 resident: 80318464 share: 0 rss: 23777280 rss_rlim: 0 CPU usage: start_time: 1167894770 rtime: 0 utime: 217 stime: 0 cutime:189 cstime: 0 timeout: 28 it_real_value: 0 frequency: 10 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 -1208273184 (LWP 4255)] [New Thread -1240171632 (LWP 4259)] (no debugging symbols found) 0x0025b402 in __kernel_vsyscall ()
+ Trace 99239
Thread 2 (Thread -1240171632 (LWP 4259))
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 ***