Download it now!
Bug 105690 - FILESAVE: Button dissapears after saving in Calc
Summary: FILESAVE: Button dissapears after saving in Calc
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected)
4.4 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: bibisected, bisected, filter:xls, regression
Depends on:
Reported: 2017-02-02 09:21 UTC by Adam Niedling
Modified: 2020-09-16 11:07 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Test document. (53.00 KB, application/
2017-02-02 09:21 UTC, Adam Niedling
Screenshot of the document in LO 5.1.4 and Word 2013 side by side (123.08 KB, image/png)
2017-02-03 08:15 UTC, Gabor Kelemen

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Niedling 2017-02-02 09:21:02 UTC
Created attachment 130827 [details]
Test document.

Steps to reproduce:

1. Open attached file with Libreoffice Calc.
2. Save it as is.
3. Open it in Excel.

Expected result:
Button is there.

Actual result:
There is no button. It has dissapeared.

This problem doesn't exist in Libre 4.4, only versions after that.
I don't want the script to work in Libreoffice as it was written for Excel.
I just don't want the button to dissapear.
Comment 1 Gabor Kelemen 2017-02-03 08:13:40 UTC
I can reproduce with 5.1.4 - after saving in XLS format and reopening the button is visible in LO but not in Excel 2013.
Comment 2 Gabor Kelemen 2017-02-03 08:15:38 UTC
Created attachment 130872 [details]
Screenshot of the document in LO 5.1.4 and Word 2013 side by side
Comment 3 Xisco Faulí 2017-07-21 09:48:28 UTC
Still reproducible in

- Version:
Build ID: bde72cdae1e7e001d5089c5284672c976b8e43df
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

- Version:
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e

but not in

Version (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Comment 4 raal 2017-07-30 16:02:10 UTC
I'm not sure if bisect is correct - in this commit is file broken in excel, so I marked it like "bad". Likely repaired in follow-up commits, now excel doesn't warn the file is broken. Markus, can this bug be related to your work on VBA export? Thanks

d9f3cb7d5cc72718103f9fc20a6ad07af00140d8 is the first bad commit
commit d9f3cb7d5cc72718103f9fc20a6ad07af00140d8
Author: Norbert Thiebaud <>
Date:   Sat Sep 12 06:56:52 2015 -0700

    source sha:3d492e8f5d5062dd4f52f29e36047ea82f18bce4

	author	Markus Mohrhard <>	2015-08-24 22:14:02 (GMT)
committer	Markus Mohrhard <>	2015-09-10 02:14:48 (GMT)
commit	3d492e8f5d5062dd4f52f29e36047ea82f18bce4 (patch)
tree	6a7faacc1abcc70deecd0fdd4e81bca84699d3a0
parent	8e06037b3f9d13a29a6ffd2f030e4360c7e1a30a (diff)
handle different callers for vba export code
This now integrates it correctly with the XLS code, the XLSX one
requires a bit more work to copy the stream to the OOXML file.
Comment 5 QA Administrators 2018-07-31 02:34:04 UTC Comment hidden (obsolete)
Comment 6 Adam Niedling 2018-10-27 15:08:18 UTC
This is still an issue.

Build az.: 65905a128db06ba48db947242809d14d3f9a93fe
CPU szálak: 8; OS: Windows 10.0; Felületmegjelenítés: alapértelmezett; 
Területi beállítások: hu-HU (hu_HU); Calc: CL
Comment 7 Adam Niedling 2019-02-02 09:36:11 UTC
Get 15 dollars to fix this bug:
Comment 8 Timur 2020-09-16 11:07:15 UTC
Repro Lo 7.1+. Excel gives warning that: File Error: data may have been lost.