GNOME Bugzilla – Bug 502212
crash in Computer: une recherche
Last modified: 2007-12-07 16:53:37 UTC
Version: 2.18.3 What were you doing when the application crashed? une recherche 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 94089216 vsize: 94089216 resident: 41439232 share: 21454848 rss: 41439232 rss_rlim: 4294967295 CPU usage: start_time: 1196952816 rtime: 558 utime: 494 stime: 64 cutime:92 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (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 -1208604960 (LWP 2543)] [New Thread -1211221104 (LWP 4929)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 181044
Thread 2 (Thread -1211221104 (LWP 4929))
----------- .xsession-errors (6 sec old) --------------------- ** (totem-video-thumbnailer:4909): WARNING **: Add decoder gsm (86037) please ** (totem-video-thumbnailer:4909): WARNING **: Add decoder gsm_ms (86049) please ** (totem-video-thumbnailer:4909): WARNING **: Add decoder mpc sv7 (86047) please ** (totem-video-thumbnailer:4909): WARNING **: Add decoder smackaud (86042) please ** (totem-video-thumbnailer:4909): WARNING **: Add decoder wavpack (86044) please ** (totem-video-thumbnailer:4909): WARNING **: Add decoder adpcm_thp (69650) please (nautilus:2543): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x8b3a)! --------------------------------------------------
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 454799 ***