GNOME Bugzilla – Bug 389660
crash in Rhythmbox Music Player:
Last modified: 2006-12-26 18:47: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: Permissive Accessibility: Disabled ----------- .xsession-errors --------------------- rhythmbox: error while loading shared libraries: libgnutls.so.12: cannot open shared object file: No such file or directory rhythmbox: error while loading shared libraries: libgnutls.so.12: cannot open shared object file: No such file or directory (rhythmbox:7087): Rhythmbox-WARNING **: eel_strdup_strftime does not support non-standard escape code %k RhythmDB-ERROR **: file rhythmdb-tree.c: line 248 (rhythmdb_tree_parser_start_element): should not be reached aborting... ** (bug-buddy:7099): WARNING **: GNOME メニュー・エディタ のアイコンを読み込めませんでした ** (bug-buddy:7099): WARNING **: Marlin sample editor のアイコンを読み込めませんでした ** (bug-buddy:7099): WARNING **: フォルダを開く のアイコンを読み込めませんでした ** (bug-buddy:7099): WARNING **: 暗号化の設定 のアイコンを読み込めませんでした -------------------------------------------------- Memory status: size: 121720832 vsize: 0 resident: 121720832 share: 0 rss: 32550912 rss_rlim: 0 CPU usage: start_time: 1167112969 rtime: 0 utime: 349 stime: 0 cutime:324 cstime: 0 timeout: 25 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 -1208953120 (LWP 7087)] [New Thread -1268810864 (LWP 7094)] (no debugging symbols found) 0x00802402 in __kernel_vsyscall ()
+ Trace 97013
Thread 2 (Thread -1268810864 (LWP 7094))
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 350304 ***