GNOME Bugzilla – Bug 562356
crash in File Browser: I was working with other...
Last modified: 2008-11-26 18:22:42 UTC
Version: 2.20.0 What were you doing when the application crashed? I was working with other application -openoffice 2.4- then I switch to nautilus because I want to check my personal home directory, I did click on the folder and then nautilus hanged out Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Sat Nov 8 19:00:26 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 79740928 vsize: 79740928 resident: 28512256 share: 16814080 rss: 28512256 rss_rlim: 4294967295 CPU usage: start_time: 1227708970 rtime: 2190 utime: 2051 stime: 139 cutime:3 cstime: 3 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1230685904 (LWP 5046)] 0xb7f3e424 in __kernel_vsyscall ()
+ Trace 210245
Thread 1 (Thread -1230685904 (LWP 5046))
----------- .xsession-errors (6 sec old) --------------------- argv[1] showgotobar Talse argv[2] transparentatstart true argv[3] autostart False argv[4] showstatusbar True argv[5] src http://radioitalialive.str.idc.extra.it/radioitalia argv[6] type application/x-mplayer2 argv[7] bbclient 0 argv[8] name MC1 argv[9] height 45 argv[10] width 250 Failed to execute child process "/usr/lib/totem/totem-mozilla-viewer" (No existe el fichero o el directorio) ** Message: stop Die scriptable instance ** ** ERROR:(fm-tree-model.c:1531):fm_tree_model_unref_node: assertion failed: (node->ref_count > 0) --------------------------------------------------
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 356672 ***