GNOME Bugzilla – Bug 459434
crash in Open Folder:
Last modified: 2007-07-24 21:31:08 UTC
Version: 2.18.1 What were you doing when the application 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: 81731584 vsize: 81731584 resident: 22249472 share: 12242944 rss: 22249472 rss_rlim: 4294967295 CPU usage: start_time: 1185169610 rtime: 1168 utime: 1038 stime: 130 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 -1209096480 (LWP 6335)] (no debugging symbols found) 0x003e8402 in __kernel_vsyscall ()
+ Trace 149881
Thread 1 (Thread -1209096480 (LWP 6335))
----------- .xsession-errors --------------------- (nautilus:7923): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:6335): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:6335): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed (nautilus:6335): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:6335): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:6335): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:6335): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:6335): 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 ***