GNOME Bugzilla – Bug 457201
crash in Open Folder: searching to see if I ha...
Last modified: 2007-07-16 15:58:23 UTC
Version: 2.18.1 What were you doing when the application crashed? searching to see if I had ndiswrapper and it just told me it crashed Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 123764736 vsize: 123764736 resident: 59609088 share: 12292096 rss: 59609088 rss_rlim: 4294967295 CPU usage: start_time: 1184532077 rtime: 628 utime: 561 stime: 67 cutime:0 cstime: 0 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 -1208867104 (LWP 2808)] (no debugging symbols found) 0x005d7402 in __kernel_vsyscall ()
+ Trace 148231
Thread 1 (Thread -1208867104 (LWP 2808))
----------- .xsession-errors --------------------- (nautilus:3041): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2808): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:2808): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed (nautilus:2808): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:2808): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:2808): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:2808): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:2808): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 445429 ***