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 77681 - Nautilus is crashing when you do Back and Forward Multiple times.
Nautilus is crashing when you do Back and Forward Multiple times.
Status: VERIFIED FIXED
Product: nautilus
Classification: Core
Component: Navigation
0.x.x [obsolete]
Other Solaris
: High critical
: 1.1.x
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-04-05 04:20 UTC by Sekhar Reddy Pulukunta
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch to fix it. (Well, to quietly ignore the problem rather than abort.) (994 bytes, patch)
2002-05-08 17:46 UTC, Damon Chaplin
none Details | Review

Description Sekhar Reddy Pulukunta 2002-04-05 04:20:44 UTC
Build :Solaris 9 64 Bit with the Build 3rd march 2002

Procedure :

1)Start Nautilus.
2)Select and Double click on a folder .
3)Select and Double click on the folder to open another fodler
4) Now do Back and forward multiple times by using "CTRL+[" and "CTRL+]".
5) Natilus is crashing .

This is always repeatable .

Debugging Information .


  • #0 _waitid
    from /usr/lib/libc.so.1
  • #1 _waitpid
    from /usr/lib/libc.so.1
  • #2 waitpid
    from /usr/lib/libthread.so.1
  • #3 libgnomeui_segv_handle
    from /opt/gnome-2.0/lib/libgnomeui-2.so.0
  • #4 __sighndlr
    from /usr/lib/libthread.so.1
  • #5 call_user_handler
    from /usr/lib/libthread.so.1
  • #6 <signal handler called>
  • #7 _lwp_kill
    from /usr/lib/libc.so.1
  • #8 raise
    from /usr/lib/libc.so.1
  • #9 abort
    from /usr/lib/libc.so.1
  • #10 g_logv
    from /opt/gnome-2.0/lib/libglib-2.0.so.0
  • #11 g_log
    from /opt/gnome-2.0/lib/libglib-2.0.so.0
  • #12 nautilus_window_back_or_forward
  • #13 nautilus_window_go_forward
  • #14 go_menu_forward_callback
  • #15 marshal_VOID__USER_DATA_STRING
    from /opt/gnome-2.0/lib/libbonoboui-2.so.0
  • #16 g_closure_invoke
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #17 bonobo_closure_invoke_va_list
    from /opt/gnome-2.0/lib/libbonobo-2.so.0
  • #18 bonobo_closure_invoke
    from /opt/gnome-2.0/lib/libbonobo-2.so.0
  • #19 impl_Bonobo_UIComponent_execVerb
    from /opt/gnome-2.0/lib/libbonoboui-2.so.0
  • #20 Bonobo_UIComponent_execVerb
    from /opt/gnome-2.0/lib/libbonobo-2.so.0
  • #21 real_exec_verb
    from /opt/gnome-2.0/lib/libbonoboui-
  • #22 impl_emit_verb_on
    from /opt/gnome-2.0/lib/libbonoboui-2.so.0
  • #23 g_cclosure_marshal_VOID__POINTER
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #24 g_type_class_meta_marshal
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #25 g_closure_invoke
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #26 signal_emit_unlocked_R
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /opt/gnome-2.0/lib/libgobject-
  • #29 bonobo_ui_engine_emit_verb_on_w
    from /opt/gnome-2.0/lib/libbonoboui-2.so.0
  • #30 exec_verb_cb
    from /opt/gnome-2.0/lib/libbonoboui-
  • #31 g_cclosure_marshal_VOID__VOID
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #32 g_closure_invoke
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #33 signal_emit_unlocked_R
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #34 g_signal_emit_valist
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #35 g_signal_emit
    from /opt/gnome-2.0/lib/libgobject-
  • #36 closure_accel_activate
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #37 g_closure_invoke
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #38 signal_emit_unlocked_R
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #39 g_signal_emit_valist
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #40 g_signal_emit
    from /opt/gnome-2.0/lib/libgobject-
  • #41 _gtk_accel_group_activate
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #42 gtk_accel_groups_activate
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #43 _gtk_window_activate_key
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #44 gtk_window_key_press_event
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #45 bonobo_window_key_press_event
    from /opt/gnome-2.0/lib/libbonoboui-2.so.0
  • #46 _gtk_marshal_BOOLEAN__BOXED
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #47 g_type_class_meta_marshal
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #48 g_closure_invoke
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #49 signal_emit_unlocked_R
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #50 g_signal_emit_valist
    from /opt/gnome-2.0/lib/libgobject-2.0.so.0
  • #51 gtk_signal_emit
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #52 gtk_widget_event_internal
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #53 gtk_widget_event
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #54 gtk_propagate_event
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #55 gtk_main_do_event
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #56 gdk_event_dispatch
    from /opt/gnome-2.0/lib/libgdk-x11-2.0.so.0
  • #57 g_main_dispatch
    from /opt/gnome-2.0/lib/libglib-
  • #58 g_main_context_dispatch
    from /opt/gnome-2.0/lib/libglib-2.0.so.0
  • #59 g_main_context_iterate
    from /opt/gnome-2.0/lib/libglib-2.0.so.0
  • #60 g_main_loop_run
    from /opt/gnome-2.0/lib/libglib-
  • #61 gtk_main
    from /opt/gnome-2.0/lib/libgtk-x11-2.0.so.0
  • #62 main

Comment 1 Sekhar Reddy Pulukunta 2002-04-05 09:29:29 UTC
Sorry the Build is Gnome2.0 1st April 2002 .
Comment 2 Luis Villa 2002-04-09 22:19:06 UTC
Still would be nice to see symbols from Wipro.
Comment 3 Damon Chaplin 2002-04-23 19:41:55 UTC
Here's a trace with more detail.

I can reproduce it very easily, just by pressing the keys a few times
quickly.

The quick fix is to just ignore forward/backward keys when they are
not appropriate.

The correct thing may be to find out why we are getting Bonobo exev
verb calls when the buttons should be insensitive. It seems there is
some kind of race condition happening.


  • #0 g_logv
  • #1 g_log
  • #2 nautilus_window_back_or_forward
    at nautilus-window-manage-views.c line 2053
  • #3 nautilus_window_go_back
    at nautilus-window.c line 1426
  • #4 go_menu_back_callback
    at nautilus-window-menus.c line 286
  • #5 marshal_VOID__USER_DATA_STRING
    at bonobo-ui-component.c line 217
  • #6 g_closure_invoke
    at gclosure.c line 437
  • #7 bonobo_closure_invoke_va_list
    at bonobo-types.c line 415
  • #8 bonobo_closure_invoke
    at bonobo-types.c line 474
  • #9 impl_Bonobo_UIComponent_execVerb
    at bonobo-ui-component.c line 155
  • #10 Bonobo_UIComponent_execVerb
    at Bonobo-stubs.c line 1733
  • #11 real_exec_verb
    at bonobo-ui-engine.c line 1479
  • #12 impl_emit_verb_on
    at bonobo-ui-engine.c line 1528
  • #13 g_cclosure_marshal_VOID__POINTER
    at gmarshal.c line 601
  • #14 g_type_class_meta_marshal
    at gclosure.c line 514
  • #15 g_closure_invoke
    at gclosure.c line 437
  • #16 signal_emit_unlocked_R
    at gsignal.c line 2379
  • #17 g_signal_emit_valist
    at gsignal.c line 2100
  • #18 g_signal_emit
    at gsignal.c line 2144
  • #19 bonobo_ui_engine_emit_verb_on_w
    at bonobo-ui-engine.c line 2945
  • #20 exec_verb_cb
    at bonobo-ui-sync-menu.c line 463
  • #21 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #22 g_closure_invoke
    at gclosure.c line 437
  • #23 signal_emit_unlocked_R
    at gsignal.c line 2341
  • #24 g_signal_emit_valist
    at gsignal.c line 2100
  • #25 g_signal_emit
    at gsignal.c line 2144
  • #26 closure_accel_activate
    at gtkwidget.c line 2560
  • #27 g_closure_invoke
    at gclosure.c line 437
  • #28 signal_emit_unlocked_R
    at gsignal.c line 2341
  • #29 g_signal_emit_valist
    at gsignal.c line 2110
  • #30 g_signal_emit
    at gsignal.c line 2144
  • #31 _gtk_accel_group_activate
    at gtkaccelgroup.c line 747
  • #32 gtk_accel_groups_activate
    at gtkaccelgroup.c line 785
  • #33 _gtk_window_activate_key
    at gtkwindow.c line 5929
  • #34 gtk_window_key_press_event
    at gtkwindow.c line 3581
  • #35 bonobo_window_key_press_event
    at bonobo-window.c line 302
  • #36 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #37 g_type_class_meta_marshal
    at gclosure.c line 514
  • #38 g_closure_invoke
    at gclosure.c line 437
  • #39 signal_emit_unlocked_R
  • #40 g_signal_emit_valist
    at gsignal.c line 2110
  • #41 gtk_signal_emit
    at gtksignal.c line 355
  • #42 gtk_widget_event_internal
    at gtkwidget.c line 3085
  • #43 gtk_widget_event
    at gtkwidget.c line 2946
  • #44 gtk_propagate_event
    at gtkmain.c line 2070
  • #45 gtk_main_do_event
    at gtkmain.c line 1337
  • #46 gdk_event_dispatch
    at gdkevents-x11.c line 1752
  • #47 g_main_dispatch
    at gmain.c line 1617
  • #48 g_main_context_dispatch
    at gmain.c line 2161
  • #49 g_main_context_iterate
    at gmain.c line 2242
  • #50 g_main_loop_run
    at gmain.c line 2462
  • #51 gtk_main
    at gtkmain.c line 936
  • #52 main
    at nautilus-main.c line 263
  • #53 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129

Comment 4 Luis Villa 2002-05-01 11:16:23 UTC
cc'ing michael and adding the GNOME2.0.0 keyword; it shouldn't be this
easy to crash nautilus if we can at all avoid it. [Puntable if we
can't fix, of course.] Damon: is this solaris specific?
Comment 5 Damon Chaplin 2002-05-06 18:01:12 UTC
No, it isn't Solaris-specific. And it is very easy to reproduce.

It would be simple to just ignore keypresses when we are at the ends
of the history lists. I think we should just do that.
Comment 6 Damon Chaplin 2002-05-08 17:46:26 UTC
Created attachment 8294 [details] [review]
Patch to fix it. (Well, to quietly ignore the problem rather than abort.)
Comment 7 Damon Chaplin 2002-05-08 17:47:15 UTC
Added PATCH, sun_patches keywords.

OK to commit? (I can't crash it any more.)
Comment 8 Darin Adler 2002-05-08 19:58:09 UTC
Sure. Fine to commit this change.
Comment 9 Damon Chaplin 2002-05-08 20:21:20 UTC
thanks. committed.
Comment 10 Muktha 2002-09-18 13:20:20 UTC
Couldn't simulate the problem with the latest sources from CVS head. I
guess the bug can be closed.
Comment 11 Anand 2002-09-23 04:56:18 UTC
Thanks for verifying. Marking bug as Closed.