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 611073 - critical on autofilter removal
critical on autofilter removal
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
1.10.x
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2010-02-25 14:15 UTC by frob
Modified: 2010-03-11 17:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description frob 2010-02-25 14:15:57 UTC 
Versions: 1.9.17 and 1.10

Put 1 to A1, 2 to A2, select A1, 'Data->Filter->Add Auto Filter' then 'Data->Filter->Remove Auto Filter'.

Result:
** CRITICAL **: gnm_filter_remove: assertion `filter->sheet != NULL' failed
aborting...

Program received signal SIGABRT, Aborted.

+ Trace 220718

Thread NaN (LWP 27113)

  • #0 raise
    from /lib/libc.so.6
  • #1 abort
    from /lib/libc.so.6
  • #2 g_logv
    from /lib/libglib-2.0.so.0
  • #3 g_log
    from /lib/libglib-2.0.so.0
  • #4 g_return_if_fail_warning
    from /lib/libglib-2.0.so.0
  • #5 gnm_filter_remove
    from /usr/lib/libspreadsheet-1.10.0.so
  • #6 gdk_display_close
    from /usr/lib/libspreadsheet-1.10.0.so
  • #7 ??
  • #8 ??
  • #9 sv_update
    from /usr/lib/libspreadsheet-1.10.0.so
  • #10 gnm_command_push_undo
    from /usr/lib/libspreadsheet-1.10.0.so
  • #11 cmd_autofilter_add_remove
    from /usr/lib/libspreadsheet-1.10.0.so
  • #12 gdk_display_close
    from /usr/lib/libspreadsheet-1.10.0.so
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 g_value_peek_pointer
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #19 gdk_display_close
    from /usr/lib/libgobject-2.0.so.0 






Comment 1


Morten Welinder





          2010-03-11 17:48:15 UTC
        



This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.