GNOME Bugzilla – Bug 604409
crash in File Browser: poxa mandem o patch por ...
Last modified: 2009-12-11 23:34:36 UTC
Version: 2.28.1 What were you doing when the application crashed? poxa mandem o patch por email, nao sei mais o que fazer 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: 138874880 vsize: 138874880 resident: 17485824 share: 491520 rss: 17485824 rss_rlim: 0 CPU usage: start_time: 1260573540 rtime: 19 utime: 138481 stime: 60083 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' 6695: nautilus ----------------- lwp# 1 / thread# 1 -------------------- feef3d65 waitid (0, 1a28, 80467c0, 3) feea3335 waitpid (1a28, 804687c, 0, fe2db60d) + 65 fe2dba14 g_spawn_sync (0, 837b4e8, 0, 4, 0, 0) + 418 fe2dbe28 g_spawn_command_line_sync (837a008, 0, 0, 0, 804699c) + 5c fdde1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (8225f50, 1a27, 0, fdde1ff2) + f3 fdde20d6 __1cMcheck_if_gdb6F_v_ (400, fef81000, 8046a2c, feeee765, b, 0) + 12e fdde1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046ae0, ffbffeff, ffff, fe882a00) + 64 feeee765 __sighndlr (b, 0, 8046ae0, fdde1a30) + 15 feee161f call_user_handler (b) + 2af feee184f sigacthandler (b, 0, 8046ae0) + df --- called from signal handler with signal 11 (SIGSEGV) --- fe2d5efb g_utf8_collate_key (82ab7a8, 8) + 83 fe2d63eb g_utf8_collate_key_for_filename (82ab7a8, ffffffff, 82ab7a8, 81537c2) + 2ff 081538ae nautilus_file_set_display_name (82a7060, 82ab7a8, 82ab7c0, 0) + fa 08156e30 update_info_internal (82a7060, 82ac230, 0, fe38667e, 82a7060, 821f8d8) + 94 08157e1f nautilus_file_update_info (82a7060) + 13 0813c26b query_info_callback (82985a0, 8280938, 82a3ef0, fe3aa4df) + d7 fe3aa521 g_simple_async_result_complete (8280938, 0, 0, fe3aa646) + 99 fe3aa673 complete_in_idle_cb_for_thread (82ab2b0, 0, 14, fe2a7514) + 3b fe2a752a g_idle_dispatch (82ac1b0, fe3aa638, 82ab2b0, 8046f70) + 22 fe2a4eee g_main_context_dispatch (8245ce0, 0, 837dc38, d) + 262 fe2a559f g_main_context_iterate (8245ce0, 1, 1, 8225620) + 483 fe2a5bc9 g_main_loop_run (8379d50, 8379d50, 80be76c, fe57e832) + 1dd fe57e8db gtk_main (80470c0, feeec196, 8047178, 0, 0, 0) + b7 080ce78b main (1, 8047220, 8047228, 80471dc) + 77b 080bca6d _start (1, 804734c, 0, 8047355, 8047386, 80473ba) + 7d ----------------- lwp# 2 / thread# 2 -------------------- feeee6d9 lwp_park (0, fd9dee08, 0) feee7cdd cond_wait_queue (8379e10, 827d148, fd9dee08, feee7f26) + 60 feee8103 cond_wait_common (8379e10, 827d148, fd9dee08, feee8346) + 1eb feee839e __cond_timedwait (8379e10, 827d148, fd9dee88, feee8430) + 66 feee8441 cond_timedwait (8379e10, 827d148, fd9dee88, feee8474) + 27 feee848c pthread_cond_timedwait (8379e10, 827d148, fd9dee88, fe861955) + 24 fe86199f g_cond_timed_wait_posix_impl (8379e10, 827d148, fd9def38, fe27c23b) + 57 fe27c284 g_async_queue_pop_intern_unlocked (827d128, 0, fd9def38, fe27c6b2) + 90 fe27c708 g_async_queue_timed_pop (827d128, fd9def38, 0, fe2ce702) + 64 fe2ce7be g_thread_pool_wait_for_new_pool (fe34d4dc, fe34c460, 4b22d364, e6d02, fe34d4ec, 0) + ca fe2cea10 g_thread_pool_thread_proxy (82ab948, 82ab980, 200, fe2cd1de) + 180 fe2cd303 g_thread_create_proxy (82ab980, fef81000, fd9defe8, feeee39e) + 133 feeee3f3 _thrp_setup (fdfa0a00) + 9b feeee680 _lwp_start (fdfa0a00, 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 ***