GNOME Bugzilla – Bug 604384
crash in Computer: help me error desktop
Last modified: 2009-12-11 20:48:46 UTC
Version: 2.28.1 What were you doing when the application crashed? help me error desktop 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: 138903552 vsize: 138903552 resident: 17346560 share: 442368 rss: 17346560 rss_rlim: 0 CPU usage: start_time: 1260556062 rtime: 19 utime: 134643 stime: 59820 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' 4188: nautilus ----------------- lwp# 1 / thread# 1 -------------------- feef3d65 waitid (0, 105d, 80467d0, 3) feea3335 waitpid (105d, 804688c, 0, fe2db60d) + 65 fe2dba14 g_spawn_sync (0, 837e5d8, 0, 4, 0, 0) + 418 fe2dbe28 g_spawn_command_line_sync (83493e0, 0, 0, 0, 80469ac) + 5c fde01e4f __1cNrun_bug_buddy6Fpkclp0_b_ (8225f50, 105c, 0, fde01ff2) + f3 fde020d6 __1cMcheck_if_gdb6F_v_ (400, fef81000, 8046a3c, feeee765, b, 0) + 12e fde01a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046af0, ffbffeff, ffff, febd2a00) + 64 feeee765 __sighndlr (b, 0, 8046af0, fde01a30) + 15 feee161f call_user_handler (b) + 2af feee184f sigacthandler (b, 0, 8046af0) + df --- called from signal handler with signal 11 (SIGSEGV) --- fe2d5efb g_utf8_collate_key (82b0960, 7) + 83 fe2d63eb g_utf8_collate_key_for_filename (82b0960, ffffffff, 82b0960, 81537c2) + 2ff 081538ae nautilus_file_set_display_name (82a7230, 82b0960, 82b0980, 0) + fa 08156e30 update_info_internal (82a7230, 82ad6c8, 0, fe38667e, 82a7230, 821f8d8) + 94 08157e1f nautilus_file_update_info (82a7230) + 13 0813c26b query_info_callback (8297dc0, 8280b70, 82b0a60, fe3aa4df) + d7 fe3aa521 g_simple_async_result_complete (8280b70, 0, 0, fe3aa646) + 99 fe3aa673 complete_in_idle_cb_for_thread (82af4f8, 0, 14, fe2a7514) + 3b fe2a752a g_idle_dispatch (82b2d78, fe3aa638, 82af4f8, 8046f80) + 22 fe2a4eee g_main_context_dispatch (8245d08, 0, 8380748, d) + 262 fe2a559f g_main_context_iterate (8245d08, 1, 1, 8225620) + 483 fe2a5bc9 g_main_loop_run (837a780, 837a780, 80be76c, fe57e832) + 1dd fe57e8db gtk_main (80470d0, feeec196, 8047188, 0, 0, 0) + b7 080ce78b main (1, 8047224, 804722c, 80bca0f) + 77b 080bca6d _start (1, 8047350, 0, 8047359, 804738a, 80473be) + 7d ----------------- lwp# 2 / thread# 2 -------------------- feeee6d9 lwp_park (0, fd9eee08, 0) feee7cdd cond_wait_queue (8381480, 827b7d0, fd9eee08, feee7f26) + 60 feee8103 cond_wait_common (8381480, 827b7d0, fd9eee08, feee8346) + 1eb feee839e __cond_timedwait (8381480, 827b7d0, fd9eee88, feee8430) + 66 feee8441 cond_timedwait (8381480, 827b7d0, fd9eee88, feee8474) + 27 feee848c pthread_cond_timedwait (8381480, 827b7d0, fd9eee88, febb1955) + 24 febb199f g_cond_timed_wait_posix_impl (8381480, 827b7d0, fd9eef38, fe27c23b) + 57 fe27c284 g_async_queue_pop_intern_unlocked (827b7b0, 0, fd9eef38, fe27c6b2) + 90 fe27c708 g_async_queue_timed_pop (827b7b0, fd9eef38, 0, fe2ce702) + 64 fe2ce7be g_thread_pool_wait_for_new_pool (fe34d4dc, fe34c460, 4b228f1f, 1faed, fe34d4ec, 0) + ca fe2cea10 g_thread_pool_thread_proxy (82ac7b8, 82ac7f0, 200, fe2cd1de) + 180 fe2cd303 g_thread_create_proxy (82ac7f0, fef81000, fd9eefe8, feeee39e) + 133 feeee3f3 _thrp_setup (fdfc0a00) + 9b feeee680 _lwp_start (fdfc0a00, 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
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 ***
*** Bug 604392 has been marked as a duplicate of this bug. ***