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 603016 - crash when deleting series
crash when deleting series
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Charting
git master
Other Linux
: Normal critical
: ---
Assigned To: Jean Bréfort
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2009-11-26 08:17 UTC by Andreas J. Guelzow
Modified: 2009-11-26 10:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Andreas J. Guelzow 2009-11-26 08:17:35 UTC 
new gnumeric
set A1:A3 to 1,2,3
select A1:A3
insert chart
select Statistic->probability plot
forward
click on "Series 1"
click on the delete button
boom!

Program received signal SIGSEGV, Segmentation fault.
0xb5a307ba in gog_probability_plot_update (obj=0x85a4178)
    at gog-probability-plot.c:74
74		GogProbabilityPlotSeries *series = GOG_PROBABILITY_PLOT_SERIES (
(gdb) bt

+ Trace 219297

  • #0 gog_probability_plot_update
    at gog-probability-plot.c line 74
  • #1 gog_object_update
    at gog-object.c line 1354
  • #2 gog_object_update
    at gog-object.c line 1347
  • #3 gog_object_update
    at gog-object.c line 1347
  • #4 gog_graph_force_update
    at gog-graph.c line 718
  • #5 gog_object_get_editor
    at gog-object.c line 1297
  • #6 cb_attr_tree_selection_change
    at gog-guru.c line 608
  • #7 IA__g_cclosure_marshal_VOID__VOID
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gmarshal.c line 77
  • #8 IA__g_closure_invoke
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gclosure.c line 767
  • #9 signal_emit_unlocked_R
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/gobject/gsignal.c line 3247
  • #10 IA__g_signal_emit_valist 






Comment 1


Jean Bréfort





          2009-11-26 10:42:17 UTC
        



This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.