GNOME Bugzilla – Bug 602211
crash in File Browser: system start
Last modified: 2009-11-17 18:17:23 UTC
Version: 2.28.0 What were you doing when the application crashed? system start 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: 84860928 vsize: 84860928 resident: 16228352 share: 540672 rss: 16228352 rss_rlim: 0 CPU usage: start_time: 1258474305 rtime: 34 utime: 253719 stime: 92389 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' 3104: nautilus ----------------- lwp# 1 / thread# 1 -------------------- ff2c7504 waitid (0, c21, ffbfd8d0, 3) ff27b070 waitpid (c21, ffbfd9d8, 0, 0, 0, c21) + 64 fe602688 g_spawn_sync (0, ffbfd9dc, 0, ffbfd9d8, 0, 0) + 4a8 fe602a1c g_spawn_command_line_sync (34b500, 0, 0, 0, ffbfdb44, 2b8e10) + 98 fe0c1d88 __1cNrun_bug_buddy6Fpkclp0_b_ (1ef078, c20, 0, fe0c25a4, 2b8e10, 34b500) + f0 fe0c1fec __1cMcheck_if_gdb6F_v_ (400, 1, 1, fffeffba, c20, 10000) + 118 fe0c19f0 __1cUbugbuddy_segv_handle6Fi_v_ (1, 0, fe0d2754, 46c, 10de4, 400) + 84 ff2c26ac __sighndlr (b, 0, ffbfdde0, fe0c196c, a, ffbfdde0) + c ff2b5eec call_user_handler (b, 0, ffbfdde0, 0, 0, 9fcb8) + 1a4 ff2b638c sigacthandler (b, 0, ffbfdde0, ffffffff, ffbfdeb0, ff356000) + 48 --- called from signal handler with signal 11 (SIGSEGV) --- fe5fc2f4 g_utf8_collate_key (34ca40, b, 0, 0, ffffffff, 3504d8) + a8 fe5fc75c g_utf8_collate_key_for_filename (264840, 264844, 34ca4b, fe5fc448, 34ca4b, 2300) + 2e4 0011962c nautilus_file_set_display_name (272308, 34ca40, 279018, 0, 1, a000000) + 138 0011cc68 update_info_internal (1, 1, 0, 272308, 272318, 23000) + c4 00102048 query_info_callback (27a118, 31e920, 2a5478, 1bd224, 270030, 272308) + 13c fe6db7e4 complete_in_idle_cb_for_thread (1, fe6db768, 4eea8, fe72a62c, 31e920, 27f0f8) + 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, 212050, 1) + 4c4 fe5c84a4 g_main_loop_run (34c7e8, 10, 0, fe66ed0c, 1, 1ee748) + 38c fea00a00 gtk_main (1, 1, 0, 34c7e8, 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 (27f110, 249a88, fdcfbc80, 0, 0, 0) + 4c ff2bcb18 cond_wait_common (27f110, 249a88, fdcfbc80, 1c00, fe280a00, 0) + 2d8 ff2bcd14 __cond_timedwait (27f110, 249a88, fdcfbdb0, 0, ffffffe0, 0) + 80 ff2bcdac cond_timedwait (27f110, 249a88, fdcfbdb0, 4356, 4000, ff35c1ac) + 14 ff2bcdec pthread_cond_timedwait (27f110, 249a88, fdcfbdb0, 3, 27b28960, 4f6512c) + c fef71918 g_cond_timed_wait_posix_impl (27f110, 249a88, fdcfbed8, fef72e78, 11c40, 10400) + 104 fe59b744 g_async_queue_pop_intern_unlocked (249a68, fe6711dc, fdcfbed8, fe6711d8, fe671200, fe66ed0c) + 10c fe59bbc8 g_async_queue_timed_pop (249a68, 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 (278cd8, 0, 0, fe66ed0c, fe6711d8, fe6711f8) + 150 fe5f1c34 g_thread_create_proxy (278d10, 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 ***