GNOME Bugzilla – Bug 503303
crash in Dictionary: I looked up the word "ca...
Last modified: 2007-12-17 22:33:03 UTC
Version: 2.18.1 What were you doing when the application crashed? I looked up the word "catalogued" Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 266424320 vsize: 266424320 resident: 18132992 share: 14565376 rss: 18132992 rss_rlim: 18446744073709551615 CPU usage: start_time: 1197484638 rtime: 6 utime: 5 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-dictionary' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496383712 (LWP 27248)] (no debugging symbols found) 0x00000036f000d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 181695
Thread 1 (Thread 46912496383712 (LWP 27248))
----------- .xsession-errors (263728 sec old) --------------------- ** (totem-video-thumbnailer:14615): WARNING **: Add decoder dsicinaudio (86045) please ** (totem-video-thumbnailer:14615): WARNING **: Add decoder imc (86046) please ** (totem-video-thumbnailer:14615): WARNING **: Add decoder gsm (86037) please ** (totem-video-thumbnailer:14615): WARNING **: Add decoder gsm_ms (86049) please ** (totem-video-thumbnailer:14615): WARNING **: Add decoder mpc sv7 (86047) please ** (totem-video-thumbnailer:14615): WARNING **: Add decoder smackaud (86042) please ** (totem-video-thumbnailer:14615): WARNING **: Add decoder wavpack (86044) please ...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 we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 465336 ***