GNOME Bugzilla – Bug 601369
crash in File Browser: Working!!!!
Last modified: 2009-11-10 12:35:06 UTC
Version: 2.28.0 What were you doing when the application crashed? Working!!!! Distribution: Solaris Express Community Edition snv_125 SPARC Gnome Release: 2.28.0 2009-09-28 (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: 84844544 vsize: 84844544 resident: 15802368 share: 499712 rss: 15802368 rss_rlim: 0 CPU usage: start_time: 1257844448 rtime: 36 utime: 259774 stime: 103515 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' 8387: nautilus ----------------- lwp# 1 / thread# 1 -------------------- ff2c7504 waitid (0, 20c8, ffbfd8e8, 3) ff27b070 waitpid (20c8, ffbfd9f0, 0, 0, 0, 20c8) + 64 fe602688 g_spawn_sync (0, ffbfd9f4, 0, ffbfd9f0, 0, 0) + 4a8 fe602a1c g_spawn_command_line_sync (274280, 0, 0, 0, ffbfdb5c, 2b8ca0) + 98 fe0c1d88 __1cNrun_bug_buddy6Fpkclp0_b_ (1ef078, 20c3, 0, fe0c25a4, 2b8ca0, 274280) + f0 fe0c1fec __1cMcheck_if_gdb6F_v_ (400, 1, 1, fffeffba, 20c3, 10000) + 118 fe0c19f0 __1cUbugbuddy_segv_handle6Fi_v_ (1, 0, fe0d2754, 46c, 10de4, 400) + 84 ff2c26ac __sighndlr (b, 0, ffbfddf8, fe0c196c, a, ffbfddf8) + c ff2b5eec call_user_handler (b, 0, ffbfddf8, 0, 0, 9fcb8) + 1a4 ff2b638c sigacthandler (b, 0, ffbfddf8, ffffffff, ffbfdec8, ff356000) + 48 --- called from signal handler with signal 11 (SIGSEGV) --- fe5fc2f4 g_utf8_collate_key (350508, b, 0, 0, ffffffff, 349650) + a8 fe5fc75c g_utf8_collate_key_for_filename (2b8d40, 2b8d44, 350513, fe5fc448, 350513, 2300) + 2e4 0011962c nautilus_file_set_display_name (273350, 350508, 3504c0, 0, 1, a000000) + 138 0011cc68 update_info_internal (1, 1, 0, 273350, 273360, 23000) + c4 00102048 query_info_callback (27f630, 258890, 2a5728, 1bd224, 272000, 273350) + 13c fe6db7e4 complete_in_idle_cb_for_thread (1, fe6db768, 4eea8, fe72a62c, 258890, 350490) + 7c fe5c6038 g_main_dispatch (212048, 212050, fe670ffc, 0, fe66ed0c, fe5ca364) + 1e4 fe5c7704 g_main_context_dispatch (fe6711d8, 212050, 20, fe6711d4, 212050, 212048) + cc fe5c7c54 g_main_context_iterate (212048, 1, 1, fe6711e0, 1, 1) + 4c4 fe5c84a4 g_main_loop_run (34a120, 10, 0, fe66ed0c, 1, 1ee748) + 38c fea00a00 gtk_main (1, 1, 0, 34a120, fec746a0, ce90) + d8 00092798 main (1, 0, 247b40, 0, 0, 1) + 4d4 000804e0 _start (0, 0, 0, 0, 0, 0) + 108 ----------------- lwp# 2 / thread# 2 -------------------- ff2c2630 lwp_park (0, fdcfbc80, 0) ff2bc600 cond_wait_queue (2cae00, 2492e0, fdcfbc80, 0, 0, 0) + 4c ff2bcb18 cond_wait_common (2cae00, 2492e0, fdcfbc80, 1c00, fe280a00, 0) + 2d8 ff2bcd14 __cond_timedwait (2cae00, 2492e0, fdcfbdb0, 0, 0, 0) + 80 ff2bcdac cond_timedwait (2cae00, 2492e0, fdcfbdb0, 0, 0, 0) + 14 ff2bcdec pthread_cond_timedwait (2cae00, 2492e0, fdcfbdb0, 0, 2a6a5278, 54d4a4f) + c fef71918 g_cond_timed_wait_posix_impl (2cae00, 2492e0, fdcfbed8, fef72e78, 11c40, 10400) + 104 fe59b744 g_async_queue_pop_intern_unlocked (2492c0, fe6711dc, fdcfbed8, fe6711d8, fe671200, fe66ed0c) + 10c fe59bbc8 g_async_queue_timed_pop (2492c0, 0, fe6711e8, fe620624, 4e400, fe66ed0c) + cc fe5f3484 g_thread_pool_wait_for_new_pool (0, fdcfbed8, fe67127c, fe5f384c, fe66ed0c, 0) + c0 fe5f3744 g_thread_pool_thread_proxy (2743e0, 0, 0, fe66ed0c, fe6711d8, fe6711f8) + 150 fe5f1c34 g_thread_create_proxy (274418, fe671250, 252c, fe6711d4, fe671210, fe671250) + 160 ff2c25ac _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 ***