GNOME Bugzilla – Bug 601310
crash in File Manager: Nothing at all just logg...
Last modified: 2009-11-09 22:23:46 UTC
Version: 2.28.0 What were you doing when the application crashed? Nothing at all just logged in for the first time Distribution: Solaris Express Community Edition snv_126 SPARC Gnome Release: 2.28.0 2009-10-12 (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: 86597632 vsize: 86597632 resident: 15335424 share: 0 rss: 15335424 rss_rlim: 0 CPU usage: start_time: 1257802087 rtime: 28 utime: 215976 stime: 65815 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' 2303: nautilus ----------------- lwp# 1 / thread# 1 -------------------- ff2c7504 waitid (0, 927, ffbfe250, 3) ff27b070 waitpid (927, ffbfe358, 0, 0, 0, 927) + 64 fe602688 g_spawn_sync (0, ffbfe35c, 0, ffbfe358, 0, 0) + 4a8 fe602a1c g_spawn_command_line_sync (319660, 0, 0, 0, ffbfe4c4, 27de60) + 98 fe011d88 __1cNrun_bug_buddy6Fpkclp0_b_ (1ef050, 8ff, 0, fe0125a4, 27de60, 319660) + f0 fe011fec __1cMcheck_if_gdb6F_v_ (400, 1, 1, fffeffba, 8ff, 10000) + 118 fe0119f0 __1cUbugbuddy_segv_handle6Fi_v_ (1, 0, fe022754, 46c, 10de4, 400) + 84 ff2c26ac __sighndlr (b, 0, ffbfe760, fe01196c, a, ffbfe760) + c ff2b5eec call_user_handler (b, 0, ffbfe760, 0, 0, 9fcb8) + 1a4 ff2b638c sigacthandler (b, 0, ffbfe760, ffffffff, ffbfe830, ff356000) + 48 --- called from signal handler with signal 11 (SIGSEGV) --- fe5fc2f4 g_utf8_collate_key (3492e8, b, 0, 0, ffffffff, 27e0b8) + a8 fe5fc75c g_utf8_collate_key_for_filename (2b2aa0, 2b2aa4, 3492f3, fe5fc448, 3492f3, 0) + 2e4 0011963c nautilus_file_set_display_name (274140, 3492e8, 3493d8, 0, 1, a000000) + 138 0011cc78 update_info_internal (1, 1, 0, 274140, 274150, 23000) + c4 00102058 query_info_callback (27b730, 317a08, 2a0600, 1bd22c, 272038, 274140) + 13c fe6db7e4 complete_in_idle_cb_for_thread (1, fe6db768, 4eea8, fe72a62c, 317a08, 342728) + 7c fe5c6038 g_main_dispatch (2110c0, 2110c8, fe670ffc, 0, fe66ed0c, fe5ca364) + 1e4 fe5c7704 g_main_context_dispatch (fe6711d8, 2110c8, 20, fe6711d4, 2110c8, 2110c0) + cc fe5c7c54 g_main_context_iterate (2110c0, 1, 1, fe6711e0, 1, 1) + 4c4 fe5c84a4 g_main_loop_run (342608, 10, 0, fe66ed0c, 1, 1ee750) + 38c fea009a0 gtk_main (1, 1, 0, 342608, fec747d4, ce9c) + d8 00092798 main (1, 0, 249b40, 0, 0, 1) + 4d4 000804e0 _start (0, 0, 0, 0, 0, 0) + 108 ----------------- lwp# 2 / thread# 2 -------------------- ff2c2630 lwp_park (0, fdbfbc80, 0) ff2bc600 cond_wait_queue (3412e8, 248190, fdbfbc80, 0, 0, 0) + 4c ff2bcb18 cond_wait_common (3412e8, 248190, fdbfbc80, 1c00, fe1b0a00, 0) + 2d8 ff2bcd14 __cond_timedwait (3412e8, 248190, fdbfbdb0, 0, 0, 0) + 80 ff2bcdac cond_timedwait (3412e8, 248190, fdbfbdb0, 0, 0, 0) + 14 ff2bcdec pthread_cond_timedwait (3412e8, 248190, fdbfbdb0, 0, f821ba8, 1f04375) + c fefc1918 g_cond_timed_wait_posix_impl (3412e8, 248190, fdbfbed8, fefc2e78, 11c40, 10400) + 104 fe59b744 g_async_queue_pop_intern_unlocked (248170, fe6711dc, fdbfbed8, fe6711d8, fe671200, fe66ed0c) + 10c fe59bbc8 g_async_queue_timed_pop (248170, 0, fe6711e8, fe620624, 4e400, fe66ed0c) + cc fe5f3484 g_thread_pool_wait_for_new_pool (0, fdbfbed8, fe67127c, fe5f384c, fe66ed0c, 0) + c0 fe5f3744 g_thread_pool_thread_proxy (278578, 0, 0, fe66ed0c, fe6711d8, fe6711f8) + 150 fe5f1c34 g_thread_create_proxy (2785b0, 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 ***