GNOME Bugzilla – Bug 602475
crash in File Manager: rien
Last modified: 2009-11-20 12:18:12 UTC
Version: 2.28.1 What were you doing when the application crashed? rien Distribution: Solaris Express Community Edition snv_127 SPARC Gnome Release: 2.28.0 2009-10-26 (Sun Microsystems, Inc.) BugBuddy Version: 2.28.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 6620 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 86704128 vsize: 86704128 resident: 16269312 share: 0 rss: 16269312 rss_rlim: 0 CPU usage: start_time: 1258705866 rtime: 37 utime: 289590 stime: 81550 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' 2098: nautilus ----------------- lwp# 1 / thread# 1 -------------------- ff2c7524 waitid (0, 833, ffbfe358, 3) ff27b090 waitpid (833, ffbfe460, 0, 0, 0, 833) + 64 fe702688 g_spawn_sync (0, ffbfe464, 0, ffbfe460, 0, 0) + 4a8 fe702a1c g_spawn_command_line_sync (30f7a8, 0, 0, 0, ffbfe5cc, 2b1fa0) + 98 fe021d88 __1cNrun_bug_buddy6Fpkclp0_b_ (1ef398, 832, 0, fe0225a4, 2b1fa0, 30f7a8) + f0 fe021fec __1cMcheck_if_gdb6F_v_ (400, 1, 1, fffeffba, 832, 10000) + 118 fe0219f0 __1cUbugbuddy_segv_handle6Fi_v_ (1, 0, fe032754, 46c, 10de4, 400) + 84 ff2c26cc __sighndlr (b, 0, ffbfe868, fe02196c, a, ffbfe868) + c ff2b5f0c call_user_handler (b, 0, ffbfe868, 0, 0, 9fc98) + 1a4 ff2b63ac sigacthandler (b, 0, ffbfe868, ffffffff, ffbfe948, ff356000) + 48 --- called from signal handler with signal 11 (SIGSEGV) --- fe6fc2f4 g_utf8_collate_key (2909a0, 7, 0, 0, ffffffff, 3253b8) + a8 fe6fc75c g_utf8_collate_key_for_filename (2b1fc0, 2b1fc4, 2909a7, fe6fc448, 2909a7, 0) + 2e4 001198ec nautilus_file_set_display_name (270220, 2909a0, 2909d0, 0, 1, a000000) + 138 0011cf28 update_info_internal (1, 1, 0, 270220, 270230, 23000) + c4 00102304 query_info_callback (294378, 2554c8, 2709f8, 1bd550, 26e160, 270220) + 13c ff05b860 complete_in_idle_cb_for_thread (1, ff05b7e4, 4f20c, ff0aaa0c, 2554c8, 2734e8) + 7c fe6c6038 g_main_dispatch (20e4e8, 20e4f0, fe770ffc, 0, fe76ed0c, fe6ca364) + 1e4 fe6c7704 g_main_context_dispatch (fe7711d8, 20e4f0, 20, fe7711d4, 20e4f0, 20e4e8) + cc fe6c7c54 g_main_context_iterate (20e4e8, 1, 1, fe7711e0, 1, 1) + 4c4 fe6c84a4 g_main_loop_run (3442b0, 10, 0, fe76ed0c, 1, 1eea98) + 38c fea00a5c gtk_main (1, 1, 0, 3442b0, fec74c2c, cebc) + d8 00092848 main (1, 0, 245740, 0, 0, 1) + 4d4 00080568 _start (0, 0, 0, 0, 0, 0) + 108 ----------------- lwp# 3 / thread# 3 -------------------- ff2c2650 lwp_park (0, fda7bc80, 0) ff2bc620 cond_wait_queue (2949f0, 246f60, fda7bc80, ff000000, 0, 0) + 4c ff2bcb38 cond_wait_common (2949f0, 246f60, fda7bc80, 1c00, fe1e1200, 0) + 2d8 ff2bcd34 __cond_timedwait (2949f0, 246f60, fda7bdb0, 0, ffffffe0, 0) + 80 ff2bcdcc cond_timedwait (2949f0, 246f60, fda7bdb0, 4356, 4000, ff35c1ec) + 14 ff2bce0c pthread_cond_timedwait (2949f0, 246f60, fda7bdb0, 3, 4747120, 8e8e24) + c feca1918 g_cond_timed_wait_posix_impl (2949f0, 246f60, fda7bed8, feca2e78, 11c40, 10400) + 104 fe69b744 g_async_queue_pop_intern_unlocked (246f40, fe7711dc, fda7bed8, fe7711d8, fe771200, fe76ed0c) + 10c fe69bbc8 g_async_queue_timed_pop (246f40, 0, fe7711e8, fe720624, 4e400, fe76ed0c) + cc fe6f3484 g_thread_pool_wait_for_new_pool (0, fda7bed8, fe77127c, fe6f384c, fe76ed0c, 0) + c0 fe6f3744 g_thread_pool_thread_proxy (273a78, 0, 0, fe76ed0c, fe7711d8, fe7711f8) + 150 fe6f1c34 g_thread_create_proxy (272350, fe771250, 252c, fe7711d4, fe771210, fe771250) + 160 ff2c25cc _lwp_start (0, 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 ***