GNOME Bugzilla – Bug 593122
crash in Open Folder: logging in
Last modified: 2010-01-06 04:33:02 UTC
Version: 2.26.2 What were you doing when the application crashed? logging in Distribution: Solaris Express Community Edition snv_116 X86 Gnome Release: 2.26.1 2009-05-04 (Sun Microsystems, Inc.) BugBuddy Version: 2.26.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10601901 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 166117376 vsize: 166117376 resident: 41975808 share: 491520 rss: 41975808 rss_rlim: 0 CPU usage: start_time: 1251271342 rtime: 379 utime: 2921594 stime: 877644 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' 2861: nautilus ----------------- lwp# 1 / thread# 1 -------------------- d0b02825 waitid (0, b70, 8046470, 3) d0ab2ef5 waitpid (b70, 804652c, 0, d0089389) + 65 d0089790 g_spawn_sync (0, 92f87f0, 0, 4, 0, 0) + 418 d0089b90 g_spawn_command_line_sync (838b850, 0, 0, 0, 804664c) + 5c cc1d1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (82257d0, b2d, 0, cc1d1fde) + f3 cc1d20c2 __1cMcheck_if_gdb6F_v_ (d0ad8275, d0b80000, 80466cc, d0afd1df, b, 0) + 12e cc1d1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046780) + 64 d0afd1df __sighndlr (b, 0, 8046780, cc1d1a30) + f d0af025f call_user_handler (b) + 2af d0af048f sigacthandler (b, 0, 8046780) + df --- called from signal handler with signal 11 (SIGSEGV) --- 080ff104 directory_belongs_in_scripts_menu (0, 81f01a4, 83a3118, 83a3114) + 34 080ff236 update_scripts_menu (83aa478, 0, 0, 8103809) + fe 08103d38 real_update_menus (83aa478) + edc 0810c651 fm_icon_view_update_menus (83aa478, 82a46f0, 8046b18, 80f67e1) + 4d 080f67fe real_update_menus (83aa478, 82a46f0, 8046b38, 81061e1) + 96 081061f8 fm_directory_view_update_menus (83aa478, 50) + 70 080fb684 update_menus_timeout_callback (83aa478, d00fa278, 0, d0054b19) + 4c d0054b2f g_timeout_dispatch (83cc4e8, 80fb638, 83aa478, 8046bf0) + 23 d0052d5a g_main_context_dispatch (8242d20, 0, 83a2aa0, f) + 262 d00533fd g_main_context_iterate (8242d20, 1, 1, 8224ed0) + 475 d0053a71 g_main_loop_run (8330a40, 8330a40, 80be378, d032286e) + 1dd d0322917 gtk_main (8046d40, d0afac5b, 8046df8, 0, 0, 0) + b7 080cdfbf main (1, 8046e9c, 8046ea4, d0bfc804) + 73b 080bc69d _start (1, 804700c, 0, 8047015, 804704d, 8047086) + 7d ----------------- lwp# 2 / thread# 2 -------------------- d0afd159 lwp_park (0, cbcbee0c, 0) d0af684d cond_wait_queue (82e0c68, 8284f70, cbcbee0c, d0af6a36) + 60 d0af6c13 cond_wait_common (82e0c68, 8284f70, cbcbee0c, d0af6e56) + 1eb d0af6eae __cond_timedwait (82e0c68, 8284f70, cbcbee8c, d0af6f40) + 66 d0af6f51 cond_timedwait (82e0c68, 8284f70, cbcbee8c, d0af6f84) + 27 d0af6f9c pthread_cond_timedwait (82e0c68, 8284f70, cbcbee8c, cfe21955) + 24 cfe2199f g_cond_timed_wait_posix_impl (82e0c68, 8284f70, cbcbef3c, d002b422) + 57 d002b4a4 g_async_queue_pop_intern_unlocked (8284f50, 0, cbcbef3c, d002b8d2) + 90 d002b928 g_async_queue_timed_pop (8284f50, cbcbef3c, 0, d007c942) + 64 d007c9fe g_thread_pool_wait_for_new_pool (d00fb28c, d00fa278, 4a94e2b9, db351, d00fb29c, 0) + ca d007cc50 g_thread_pool_thread_proxy (82c0838, 82c0870, 200, d007b41e) + 180 d007b543 g_thread_create_proxy (82c0870, d0b80000, cbcbefec, d0afce3e) + 133 d0afce76 _thrp_setup (ceb10a00) + 7e d0afd100 _lwp_start (ceb10a00, 0, 0, d0afce3e, 0, 0) ---- Critical and fatal warnings logged during execution ---- ** Eel **: file eel-preferences.c: line 330: assertion `preferences_is_initialized ()' failed ** Eel **: file eel-preferences.c: line 1170: assertion `preferences_is_initialized ()' failed ** nautilus **: file nautilus-directory.c: line 1937: assertion `NAUTILUS_IS_DIRECTORY (directory)' failed ** GLib-GObject **: file gobject.c: line 2916: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** GLib-GObject **: file gobject.c: line 2916: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** nautilus **: file nautilus-directory.c: line 558: assertion `NAUTILUS_IS_DIRECTORY (directory)' 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 571611 ***