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 569862 - unhandled excel object and gnm_pane_set_left_col critical
unhandled excel object and gnm_pane_set_left_col critical
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export MS Excel (tm)
git master
Other All
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2009-01-30 17:58 UTC by sum1
Modified: 2011-05-20 20:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description sum1 2009-01-30 17:58:55 UTC
Version: r17115
OS: Ubuntu Intrepid

Steps to reproduce:
- Download Attachment 5893 [details] (.xls file from Bug 62843)
- ssconvert attachment.xls /tmp/foo.xlsx

Console output:

gnumeric:read-WARNING **: EXCEL: unhandled excel object of type Dialog (0xf) id = 1.
gnumeric:read-WARNING **: EXCEL: unhandled excel object of type Group (0x13) id = 6.
gnumeric:read-WARNING **: EXCEL: unhandled excel object of type Group (0x13) id = 12.
gnumeric:read-WARNING **: EXCEL: unhandled excel object of type Dialog (0xf) id = 1.
gnumeric:read-WARNING **: EXCEL: unhandled excel object of type Group (0x13) id = 5.
gnumeric:read-WARNING **: EXCEL: unhandled excel object of type Group (0x13) id = 11.
CRITICAL **: sheet_col_get: assertion `pos < gnm_sheet_get_max_cols (sheet)' failed
CRITICAL **: sheet_col_get: assertion `pos < gnm_sheet_get_max_cols (sheet)' failed


Backtrace:
  • #0 IA__g_return_if_fail_warning
  • #1 sheet_col_get
    at sheet.c line 2860
  • #2 xlsx_write_cols
    at xlsx-write.c line 708
  • #3 xlsx_write_sheet
    at xlsx-write.c line 1305
  • #4 xlsx_write_workbook
    at xlsx-write.c line 1372
  • #5 xlsx_file_save
    at xlsx-write.c line 1454
  • #6 go_plugin_loader_module_func_file_save
    at go-plugin-loader-module.c line 323
  • #7 go_plugin_file_saver_save
    at go-plugin-service.c line 749
  • #8 go_file_saver_save
    at file.c line 705
  • #9 wbv_save_to_output
    at workbook-view.c line 850
  • #10 wbv_save_to_uri
    at workbook-view.c line 887
  • #11 wb_view_save_as
    at workbook-view.c line 923
  • #12 convert
    at ssconvert.c line 336
  • #13 main
    at ssconvert.c line 401

Comment 1 Andreas J. Guelzow 2009-05-11 04:34:07 UTC
Note that the first warnings:

gnumeric:read-WARNING **: EXCEL: unhandled excel object of type Dialog (0xf) id
= 1.
gnumeric:read-WARNING **: EXCEL: unhandled excel object of type Group (0x13) id
= 6.
gnumeric:read-WARNING **: EXCEL: unhandled excel object of type Group (0x13) id
= 12.
gnumeric:read-WARNING **: EXCEL: unhandled excel object of type Dialog (0xf) id
= 1.
gnumeric:read-WARNING **: EXCEL: unhandled excel object of type Group (0x13) id
= 5.
gnumeric:read-WARNING **: EXCEL: unhandled excel object of type Group (0x13) id
= 11.

are related to reading the initial reading of the file. When opeining the file into Gnumeric we also get:

** (gnumeric:27646): CRITICAL **: gnm_pane_set_left_col: assertion `0 <= new_first_col && new_first_col < gnm_sheet_get_max_cols (sheet)' failed
Comment 2 Andreas J. Guelzow 2009-05-11 04:56:39 UTC
I have fixed the xlsx part of the problem. 

THe critical when opening the original (or the xlsx translation) about the gnm_pane still exists and of course the "unhandled excel object". 
Comment 3 Morten Welinder 2011-05-20 20:12:57 UTC
Right now I get a memory allocation failure.

  • #1 abort
    from /lib64/libc.so.6
  • #2 g_logv
    from /lib64/libglib-2.0.so.0
  • #3 g_log
    from /lib64/libglib-2.0.so.0
  • #4 g_malloc
    from /lib64/libglib-2.0.so.0
  • #5 g_strndup
    from /lib64/libglib-2.0.so.0
  • #6 xlsx_write_rich_text
    at xlsx-write.c line 985
  • #7 xlsx_write_comments
    at xlsx-write.c line 1047

985			buf = g_strndup (text + start, end - start);
(gdb) p end - start
$1 = -2147483339
(gdb) p end
$2 = 308
(gdb) p start
$3 = 2147483647
Comment 4 Morten Welinder 2011-05-20 20:16:19 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.