After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 600611 - crash in Computer: nothing nothing nothing ...
crash in Computer: nothing nothing nothing ...
Status: RESOLVED DUPLICATE of bug 599178
Product: nautilus
Classification: Core
Component: general
2.28.x
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-03 21:48 UTC by sascha.winkler
Modified: 2009-11-04 04:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description sascha.winkler 2009-11-03 21:48:35 UTC
Version: 2.28.0

What were you doing when the application crashed?
nothing nothing
nothing nothing


Distribution:                   Solaris Express Community Edition snv_125 X86
Gnome Release: 2.28.0 2009-09-28 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 160858112 vsize: 160858112 resident: 38522880 share: 0 rss: 38522880 rss_rlim: 0
CPU usage: start_time: 1257284897 rtime: 50 utime: 317944 stime: 189745 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/nautilus'

7375:	nautilus
-----------------  lwp# 1 / thread# 1  --------------------
 feee3377 waitid   (0, 1cd0, 8045c70, 3)
 fee932f5 waitpid  (1cd0, 8045d2c, 0, fe38b60d) + 65
 fe38ba14 g_spawn_sync (0, 83e22b8, 0, 4, 0, 0) + 418
 fe38be28 g_spawn_command_line_sync (83b7700, 0, 0, 0, 8045e4c) + 5c
 fddb1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (8225c68, 1ccf, 0, fddb1ff2) + f3
 fddb20d6 __1cMcheck_if_gdb6F_v_ (400, fef71000, 8045edc, feede805, b, 0) + 12e
 fddb1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8045f90, ffbffeff, ffff, fe162a00) + 64
 feede805 __sighndlr (b, 0, 8045f90, fddb1a30) + 15
 feed15df call_user_handler (b) + 2af
 feed180f sigacthandler (b, 0, 8045f90) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fe385efb g_utf8_collate_key (82f8788, b) + 83
 fe3863eb g_utf8_collate_key_for_filename (82f8788, ffffffff, 8046258, 8153572) + 2ff
 0815365e nautilus_file_set_display_name (82a9320, 82f8788, 83e3090, 0) + fa
 08156be0 update_info_internal (82a9320, 82e3148, 0, fe8365de, 82a9320, 821f5ec) + 94
 08157bcf nautilus_file_update_info (82a9320) + 13
 0813c027 query_info_callback (83df740, 83b0d00, 82fb050, fe85a42d) + d7
 fe85a46f g_simple_async_result_complete (83b0d00, 0, 4, fe85a596) + 87
 fe85a5c3 complete_in_idle_cb_for_thread (82de838, 0, 4af0a521, fe357514) + 3b
 fe35752a g_idle_dispatch (82a7260, fe85a588, 82de838, 8046420) + 22
 fe354eee g_main_context_dispatch (82479d0, 0, 8399168, f) + 262
 fe35559f g_main_context_iterate (82479d0, 1, 1, 8225338) + 483
 fe355bc9 g_main_loop_run (82de610, 82de610, 80be6dc, fe57e73a) + 1dd
 fe57e7e3 gtk_main (8046570, feedc246, 8046628, 0, 0, 0) + b7
 080ce6cf main     (1, 80466c4, 80466cc, 80bc97f) + 77b
 080bc9dd _start   (1, 80468a8, 0, 80468b1, 80468e5, 8046922) + 7d
-----------------  lwp# 5 / thread# 5  --------------------
 feede76b lwp_park (0, f96ffe08, 0)
 feed7d8d cond_wait_queue (83e2fa0, 827fee0, f96ffe08, feed7fd6) + 60
 feed81b3 cond_wait_common (83e2fa0, 827fee0, f96ffe08, feed83f6) + 1eb
 feed844e __cond_timedwait (83e2fa0, 827fee0, f96ffe88, feed84e0) + 66
 feed84f1 cond_timedwait (83e2fa0, 827fee0, f96ffe88, feed8524) + 27
 feed853c pthread_cond_timedwait (83e2fa0, 827fee0, f96ffe88, fe141955) + 24
 fe14199f g_cond_timed_wait_posix_impl (83e2fa0, 827fee0, f96fff38, fe32c23b) + 57
 fe32c284 g_async_queue_pop_intern_unlocked (827fec0, 0, f96fff38, fe32c6b2) + 90
 fe32c708 g_async_queue_timed_pop (827fec0, f96fff38, 0, fe37e702) + 64
 fe37e7be g_thread_pool_wait_for_new_pool (fe3fd4dc, fe3fc460, 4af0a522, 218f5, fe3fd4ec, 0) + ca
 fe37ea10 g_thread_pool_thread_proxy (82ca9c8, 836af70, 200, fe37d1de) + 180
 fe37d303 g_thread_create_proxy (836af70, fef71000, f96fffe8, feede44e) + 133
 feede4a3 _thrp_setup (fdf82200) + 9b
 feede730 _lwp_start (fdf82200, 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 
** 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 gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed 
** Gtk **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed 
** Gtk **: file gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed 
** Gtk **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' 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 
** 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 
** Gtk **: file gtkimagemenuitem.c: line 825: assertion `GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed
Comment 1 Akhil Laddha 2009-11-04 04:20:02 UTC
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 ***