GNOME Bugzilla – Bug 626398
crash in File Browser: Deleting some files.
Last modified: 2010-08-09 03:58:03 UTC
Version: 2.30.1 What were you doing when the application crashed? Deleting some files. Distribution: Debian squeeze/sid Gnome Release: 2.30.2 2010-07-17 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.35-ou20 #1 SMP PREEMPT Mon Aug 2 23:10:09 PDT 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: NOX Icon Theme: gnome-noble GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 325099520 vsize: 325099520 resident: 193019904 share: 24420352 rss: 193019904 rss_rlim: 18446744073709551615 CPU usage: start_time: 1281132758 rtime: 6532 utime: 5982 stime: 550 cutime:52 cstime: 24 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xa6dffb70 (LWP 31941)] 0xb784b424 in __kernel_vsyscall ()
+ Trace 223169
Thread 1 (Thread 0xb6753760 (LWP 3699))
Inferior 1 [process 3699] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (30 sec old) --------------------- (Pidgin:3715): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed (Pidgin:3715): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed (Pidgin:3715): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed (Pidgin:3715): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed (Pidgin:3715): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed (Pidgin:3715): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed (Pidgin:3715): Json-CRITICAL **: json_node_get_int: assertion `node != NULL' failed sys:1: Warning: g_utf8_collate: assertion `str1 != NULL' failed --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 602500 ***