GNOME Bugzilla – Bug 602143
crash in File Manager:
Last modified: 2009-11-17 04:01:40 UTC
Version: 2.28.1 What were you doing when the application crashed? Distribution: Solaris Express Community Edition snv_127 X86 Gnome Release: 2.28.0 2009-10-26 (Sun Microsystems, Inc.) BugBuddy Version: 2.28.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 182902784 vsize: 182902784 resident: 73981952 share: 3944448 rss: 73981952 rss_rlim: 0 CPU usage: start_time: 1258402068 rtime: 954 utime: 8182986 stime: 1357758 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' 1184: nautilus ----------------- lwp# 1 / thread# 1 -------------------- feee3d65 waitid (0, d7e, 8046420, 3) fee93335 waitpid (d7e, 80464dc, 0, fe2db60d) + 65 fe2dba14 g_spawn_sync (0, 86e4548, 0, 4, 0, 0) + 418 fe2dbe28 g_spawn_command_line_sync (86880b8, 0, 0, 0, 80465fc) + 5c fde11e4f __1cNrun_bug_buddy6Fpkclp0_b_ (8225f50, 4a0, 0, fde11ff2) + f3 fde120d6 __1cMcheck_if_gdb6F_v_ (400, fef71000, 804668c, feede765, b, 0) + 12e fde11a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046740, ffbffeff, ffff, febd2a00) + 64 feede765 __sighndlr (b, 0, 8046740, fde11a30) + 15 feed161f call_user_handler (b) + 2af feed184f sigacthandler (b, 0, 8046740) + df --- called from signal handler with signal 11 (SIGSEGV) --- fe2d5efb g_utf8_collate_key (889dfa8, 1e, 868d7e4, fe2d60fa) + 83 fe2d639b g_utf8_collate_key_for_filename (889dfa8, ffffffff, 0, 81537c2) + 2af 081538ae nautilus_file_set_display_name (898e8f0, 889dfa8, 8905728, 0) + fa 08156e30 update_info_internal (898e8f0, 897e408, 1, 813f81d, 898e8f0, 821f8d8) + 94 08157e07 update_info_and_name (898e8f0, 897e408, 8046ac8, 81545f8) + 13 08154626 nautilus_file_new_from_info (868aa00, 897e408) + e2 08138881 dequeue_pending_idle_callback (868aa00) + 191 08138d00 directory_load_done (868aa00) + 98 0813a226 more_files_callback (8984670, 8986838, 86e45a8, fe38f7fc) + 132 fe38f823 next_async_callback_wrapper (8984670, 8986838, 86e45a8, fe3aa4df) + 33 fe3aa521 g_simple_async_result_complete (8986838, 0, 0, fe3aa646) + 99 fe3aa673 complete_in_idle_cb_for_thread (88ddc08, 0, 8046c28, fe2a7514) + 3b fe2a752a g_idle_dispatch (86e7230, fe3aa638, 88ddc08, 8046c80) + 22 fe2a4eee g_main_context_dispatch (8246f50, 0, 838d118, f) + 262 fe2a559f g_main_context_iterate (8246f50, 1, 1, 8225620) + 483 fe2a5bc9 g_main_loop_run (8388828, 8388828, 80be76c, fe57e832) + 1dd fe57e8db gtk_main (8046dd0, feedc196, 8046e88, 0, 0, 0) + b7 080ce78b main (1, 8046f28, 8046f30, 8046f1c) + 77b 080bca6d _start (1, 804706c, 0, 8047075, 80470a6, 80470da) + 7d ----------------- lwp# 58 / thread# 58 -------------------- feede6d9 lwp_park (0, f5466e08, 0) feed7cdd cond_wait_queue (82dbb28, 8280d20, f5466e08, feed7f26) + 60 feed8103 cond_wait_common (82dbb28, 8280d20, f5466e08, feed8346) + 1eb feed839e __cond_timedwait (82dbb28, 8280d20, f5466e88, feed8430) + 66 feed8441 cond_timedwait (82dbb28, 8280d20, f5466e88, feed8474) + 27 feed848c pthread_cond_timedwait (82dbb28, 8280d20, f5466e88, feba1955) + 24 feba199f g_cond_timed_wait_posix_impl (82dbb28, 8280d20, f5466f38, fe27c202) + 57 fe27c284 g_async_queue_pop_intern_unlocked (8280d00, 0, f5466f38, fe27c6b2) + 90 fe27c708 g_async_queue_timed_pop (8280d00, f5466f38, 0, fe2ce702) + 64 fe2ce7be g_thread_pool_wait_for_new_pool (fe34d4dc, fe34c460, 4b01d253, f0370, fe34d4ec, 0) + ca fe2cea10 g_thread_pool_thread_proxy (82b3278, 89882f0, 200, fe2cd1de) + 180 fe2cd303 g_thread_create_proxy (89882f0, fef71000, f5466fe8, feede39e) + 133 feede3f3 _thrp_setup (fdfc3a00) + 9b feede680 _lwp_start (fdfc3a00, 0, 0, 0, 0, 0) ---- Critical and fatal warnings logged during execution ---- ** Gtk **: file gtkimagemenuitem.c: line 825: assertion `GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed ** Gtk **: file gtkimagemenuitem.c: line 825: assertion `GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed ** Gtk **: file gtkimagemenuitem.c: line 825: assertion `GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed ** Gtk **: file gtkimagemenuitem.c: line 825: assertion `GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed ** GLib **: file ghash.c: line 782: assertion `hash_table != NULL' failed ** GLib **: file ghash.c: line 782: assertion `hash_table != NULL' failed ** libgnomevfs **: file gnome-vfs-uri.c: line 1346: assertion `uri != NULL' failed ** libgnomevfs **: file gnome-vfs-uri.c: line 1018: assertion `uri != NULL' failed ** Gtk **: file gtkimagemenuitem.c: line 825: assertion `GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed ** Gtk **: file gtkimagemenuitem.c: line 825: assertion `GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed ** Gtk **: file gtkimagemenuitem.c: line 825: assertion `GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed ** GLib **: file ghash.c: line 782: assertion `hash_table != NULL' failed ** GLib **: file ghash.c: line 782: assertion `hash_table != NULL' failed ** libgnomevfs **: file gnome-vfs-uri.c: line 1346: assertion `uri != NULL' failed ** libgnomevfs **: file gnome-vfs-uri.c: line 1018: assertion `uri != NULL' failed ----------- .xsession-errors (649206 sec old) --------------------- (nautilus:850): Gtk-WARNING **: About JDS: missing action About JDS (nautilus:850): Gtk-WARNING **: Go to Burn CD: missing action Go to Burn CD (nautilus:850): Gtk-CRITICAL **: file gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed (nautilus:850): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed (nautilus:850): Gtk-WARNING **: About JDS: missing action About JDS ** (gnome-power-manager:851): WARNING **: ERROR: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the r Client shut down the connection owned by im_id(1). Client shut down the connection owned by im_id(1). Client shut down the connection owned by im_id(1). --------------------------------------------------
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 599178 ***