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 367870 - Strangeness when attempting to edit locked cell
Strangeness when attempting to edit locked cell
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: GUI Expression Entry Widget
git master
Other Linux
: Normal normal
: ---
Assigned To: Jon Kåre Hellan
Jody Goldberg
: 372711 382640 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-30 19:40 UTC by sum1
Modified: 2007-01-08 01:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description sum1 2006-10-30 19:40:37 UTC 
Steps to reproduce:
- Leave the caret in A1, and select Insert > Function
- Select dimcirc and press Insert
- Check 'Enter as array function' and press OK
- Edit > Sheet > Manage Sheets
- Lock Sheet1 and press OK
- View > New View
- Press OK
- In the expression widget, click between the "[0]"s
- Press enter to close the message box
- Click again between the "[0]"s

Backtrace:

Program received signal SIGSEGV, Segmentation fault.

+ Trace 80617

Thread NaN (LWP 15983)

  • #1 cb_workbook_uri
    at application.c line 436
  • #0 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #1 cb_workbook_uri
    at application.c line 436
  • #2 gnm_app_workbook_foreach
    at application.c line 464
  • #3 gnm_app_workbook_get_by_uri
    at application.c line 449
  • #4 gnm_app_workbook_get_by_name
    at application.c line 414
  • #5 wbref_parse
    at parse-util.c line 834
  • #6 rangeref_parse
    at parse-util.c line 996
  • #7 gnm_expr_expr_find_range
    at gnumeric-expr-entry.c line 804
  • #8 cb_gee_button_press_event
    at gnumeric-expr-entry.c line 505
  • #9 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #21 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #22 main
    at main-application.c line 529 






Comment 1


Morten Welinder





          2006-10-30 20:28:50 UTC
        



I cannot reproduce this.







Comment 2


Jon Kåre Hellan





          2006-10-31 08:51:49 UTC
        



Me neither. There is sufficient info in the backtrace to avoid this particular crash, though. Expr entry passes a non-rangeref ('[0][0]') to rangeref_parse, and things go downhill from there. expr-entry made a mistake, but underlying layers shouldn't crash because of that.

Other strangeness I've seen while trying to reproduce:

A drag of part of the text in the entry would start, resulting in
 CRITICAL **: cb_pane_drag_leave: assertion `IS_GNM_CANVAS (source_widget)' failed.

I did not press the mouse to start the drag. Part of the text in the entry had become selected, and I
- clicked in the selection
- got a 'sheet locked' message box which I dismissed.
- moved the mouse over the text to the left of the selection.
May be a button release event never reached the depths of gtk responsible for tracking button state.

If I clicked in the grid to end the drag, I got
WARNING **: Unknown target type 'UTF8_STRING'!






Comment 3


Jon Kåre Hellan





          2006-10-31 09:19:04 UTC
        



Added a number of checks for NULL, fixing the crash. Downgrading/retitling. Will upgrade severity if you get a crash in another place instead.






Comment 4


Jon Kåre Hellan





          2006-10-31 10:09:47 UTC
        



Removed the criticals and warnings. You can get them in perfectly normal circumstances.

The remaining problem is that drag is initiated when it shouldn't, and that text is selected when it shouldn't.






Comment 5


Morten Welinder





          2006-10-31 20:43:29 UTC
        



Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report.







Comment 6


Morten Welinder





          2006-11-09 01:21:49 UTC
        



*** Bug 372711 has been marked as a duplicate of this bug. ***






Comment 7


Morten Welinder





          2007-01-08 01:41:46 UTC
        



*** Bug 382640 has been marked as a duplicate of this bug. ***