GNOME Bugzilla – Bug 511366
crash in File Browser: Buscando archivos
Last modified: 2008-01-23 10:31:42 UTC
Version: 2.18.3 What were you doing when the application crashed? Buscando archivos Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 101957632 vsize: 101957632 resident: 38486016 share: 21426176 rss: 38486016 rss_rlim: 4294967295 CPU usage: start_time: 1201028218 rtime: 4291 utime: 3801 stime: 490 cutime:12 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 -1208629536 (LWP 3167)] [New Thread -1274782832 (LWP 6496)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 186398
Thread 2 (Thread -1274782832 (LWP 6496))
----------- .xsession-errors (6 sec old) --------------------- gstplaybasebin.c(2203): prepare_output (): /play ** Message: Error: Internal data flow error. gstbasesrc.c(1811): gst_base_src_loop (): /play/source: streaming task paused, reason not-linked (-1) totem-video-thumbnailer couln't open file 'file:///mnt/var/spool/squirrelmail/attach/uLZVJNMjFm4lNGr6fBDYn35z6L72eGmd' Reason: You do not have a decoder installed to handle this file. You might need to install the necessary plugins.. --- Hash table keys for warning below: --> file:///root (nautilus:6482): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:3167): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed --------------------------------------------------
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 ***