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 363261 - Crash when locking sheet during cell edit
Crash when locking sheet during cell edit
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: GUI
git master
Other Linux
: Normal critical
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2006-10-18 22:21 UTC by sum1
Modified: 2006-10-19 18:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description sum1 2006-10-18 22:21:05 UTC
This might not be a bug with Gnumeric (based on the backtrace), but it seemed best to file it here first.

Steps to reproduce:
- Type '1' in A1
- While still editing the cell, right-click on the 'Sheet1' tab
- Select 'Manage Sheets...'
- Click on the lock icon for Sheet2

Backtrace:
Program received signal SIGSEGV, Segmentation fault.

Thread NaN (LWP 4438)

  • #0 gtk_tree_view_get_hadjustment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #1 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #2 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #3 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #4 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #5 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #6 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #7 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
    at main-application.c line 529

Comment 1 Jon Kåre Hellan 2006-10-19 06:09:24 UTC
Verified with HEAD of gtk 2.8 branch, self compiled on Debian sid.
For me, the crashing line is gtktreeview.c:2450
         aft_val = tree_view->priv->vadjustment->value;
relatively late in gtk_tree_view_button_press

tree_view->priv->vadjustment is NULL.

Backtrace:
  • #0 gtk_tree_view_button_press
    at gtktreeview.c line 2450
  • #1 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #2 g_type_class_meta_marshal
    at gclosure.c line 567
  • #3 IA__g_closure_invoke
    at gclosure.c line 490
  • #4 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #5 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #6 IA__g_signal_emit
    at gsignal.c line 2243
  • #7 gtk_widget_event_internal
    at gtkwidget.c line 3751
  • #8 IA__gtk_widget_event
    at gtkwidget.c line 3554
  • #9 IA__gtk_propagate_event
    at gtkmain.c line 2195
  • #10 IA__gtk_main_do_event
    at gtkmain.c line 1409
  • #11 gdk_event_dispatch
    at gdkevents-x11.c line 2291
  • #12 g_main_dispatch
    at gmain.c line 2045
  • #13 IA__g_main_context_dispatch
    at gmain.c line 2596
  • #14 g_main_context_iterate
    at gmain.c line 2677
  • #15 IA__g_main_loop_run
    at gmain.c line 2881
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 main
    at main-application.c line 529

Looks like a gtk bug to me.
Comment 2 Jon Kåre Hellan 2006-10-19 10:43:56 UTC
Taking this back to gnumeric. The tree view button press handler calls gtk_tree_view_real_set_cursor, which invokes cb_selection_changed in dialog-sheet-order.c, which causes the dialog to be destroyed. At the end of
gtk_tree_view_button_press, the dialog no longer exists.
Comment 3 Morten Welinder 2006-10-19 14:00:56 UTC
We need to either exit editing when any of those menu entries are selected,
or else disable them.  By the time we're in the dialog, we are already in
a silly state.
Comment 4 Jon Kåre Hellan 2006-10-19 18:20:49 UTC
Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report.