Bug 92164 - FILESAVE XLS Excessive number of rows warning (see comment 10)
Summary: FILESAVE XLS Excessive number of rows warning (see comment 10)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:xls
Depends on:
Blocks: XLS
  Show dependency treegraph
 
Reported: 2015-06-18 20:17 UTC by gmarco
Modified: 2019-04-14 19:13 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
screen shot of the warning (34.86 KB, image/jpeg)
2015-06-18 20:17 UTC, gmarco
Details
xls spreadsheet (193.50 KB, application/xls)
2015-06-20 14:46 UTC, gmarco
Details
zipped user profile (233.02 KB, application/x-zip-compressed)
2015-06-20 21:31 UTC, gmarco
Details
screenshot (58.43 KB, image/jpeg)
2018-02-24 18:56 UTC, gmarco
Details
screenshot (54.06 KB, image/jpeg)
2018-02-24 18:58 UTC, gmarco
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gmarco 2015-06-18 20:17:27 UTC
Created attachment 116636 [details]
screen shot of the warning

I opened a .xls file already previously open/saved in LOCALC, updating it.
Saving again the file I got the attached warning (translation: Warning saving the doc xxx: the document contains a number of rows above the limit supported in the selected format. The rows in excess were not saved).
I have files bigger than this and no warning appears.
A 1st question: which is the supported limit? I've looked for but did not find any info.
Then other observations:
- I tried to save the same still opened file as .xlsx and .ods getting no warning.
- the warning appeared after saving, so I reopened the file but I couldn't note any missing row, even making a comparison with other formats (xlsx and ods).
A 2nd question: I noticed that the size of the files on the disk is significantly different: KB 187 for xls, 61 for xlsx, 64 for ods.

Is it a possible bug?
Could you give me an explanation to questions 1 and 2?
Thanks.
Comment 1 m.a.riosv 2015-06-19 00:36:50 UTC
The limit of rows for xls is 65536, verify you haven't data neither format beyond that.
Comment 2 gmarco 2015-06-19 08:35:29 UTC
(In reply to m.a.riosv from comment #1)
> The limit of rows for xls is 65536, verify you haven't data neither format
> beyond that.

Impossible!
The file contains 3 sheets,  respectively of 24, 215, 291 rows.
I have xls files much stronger without that problem.
I think 65536 is the limit for MSExcel too, but never I had that problem.

What about the substantial difference between xls size and the others?
Comment 3 m.a.riosv 2015-06-19 13:38:02 UTC
The different size I think is in relation with the matter that ods+xlsx are compressed files while xls not.

Sorry @ gmarco, but without access to the file, doesn't seem too easy verify the issue. 

Can you attach the file after clear any information that can't be public.
Comment 4 gmarco 2015-06-19 16:07:28 UTC
(In reply to m.a.riosv from comment #3)
> Can you attach the file after clear any information that can't be public.

Sorry, but unfortunately opening/closing that file the problem no longer occurs.
That file is the same for which I received the warning after the previous save, and apparently is intact, no missing rows.
The fact remaining certain, documented, is that the warning had appeared: why remain a mystery?
Comment 5 m.a.riosv 2015-06-19 16:09:26 UTC
But don't attach the xls, the needed file is ods that when saved shows the issue.
Comment 6 gmarco 2015-06-19 17:02:00 UTC
(In reply to m.a.riosv from comment #5)
> But don't attach the xls, the needed file is ods that when saved shows the
> issue.

I think unusefull to attach anything, the file was xls, had already been modified and resaved from Calc as xls, on the last occasion, after further changes, after saving again as xls, Calc displayed the warning in question.
Now, reopening and resaving that file, the probem do not recurs any more.
Nevertheless, the file is apparently intact without missing rows.
Comment 7 m.a.riosv 2015-06-19 20:28:11 UTC
Then there is nothing to reproduce and verify.
Comment 8 gmarco 2015-06-19 21:32:11 UTC
(In reply to m.a.riosv from comment #7)
> Then there is nothing to reproduce and verify.

Hi, just tonight, changing again the xls file, the problem still occurred.
I wish to point that:
- the message appears after having completed the save (Save As)
- if I do not exit the file and try to save it again with a different name, the warning is repeated
- but if I exit the file, reopen it and resave it (Save As) the warning does no more displays.

Now I ask you: the problem exists, it is regrettably recurring but unfortunately intermittent: do you want the file anyway?
Comment 9 gmarco 2015-06-20 14:46:42 UTC
Created attachment 116681 [details]
xls spreadsheet
Comment 10 gmarco 2015-06-20 15:03:57 UTC
GOAL !!!
I managed to find a way to reproduce repeatedly the error.
The attached file named "SAVE_AS_test.xls" is the sample base.
Instructions:
- open the file (is quite complex but you should not have the need to investigate the contents or on the formulas)
- in the sheet named "scalare" select rows 1:10
- from Menu select "Insert->Rows"
- now you can also Undo, so the file is again alike when just opened
- from File select "Save As" saving with a new name (eg "SAVE_AS_testXXX.xls")
- after the saving end you should get displayed the warning (doing the above I get it repetitively)

Let me know.
Comment 11 m.a.riosv 2015-06-20 16:38:58 UTC
Following steps in comment#10 I can't reproduce the issue.

Please try resetting user profile, sometimes solves strange issues.

https://wiki.documentfoundation.org/UserProfile
Comment 12 gmarco 2015-06-20 21:29:29 UTC
(In reply to m.a.riosv from comment #11)
> Following steps in comment#10 I can't reproduce the issue.
> 
> Please try resetting user profile, sometimes solves strange issues.
> 
> https://wiki.documentfoundation.org/UserProfile

Sorry, I've resetted my user profile but nothing changed.
I attach here the zipped user folder (just resetted without any change) for your investigation.
Remember that the problem happens only if the Save As is .xls, and this also creating the file as .ods, opening it and reSaving As .xls
Comment 13 gmarco 2015-06-20 21:31:00 UTC
Created attachment 116690 [details]
zipped user profile
Comment 14 tommy27 2015-06-25 20:23:35 UTC
@gmarco @m.a.riosv
reproducible as in comment 10 under Win8.1 x64 using LibO 4.4.3.2
please tell which is the O/S you tested.

status NEW. edited summary notes.
Comment 15 gmarco 2015-06-25 21:33:48 UTC
(In reply to tommy27 from comment #14)
> @gmarco @m.a.riosv
> reproducible as in comment 10 under Win8.1 x64 using LibO 4.4.3.2
> please tell which is the O/S you tested.
> 
> status NEW. edited summary notes.

HI,
I too am working under Win8.1 x64 using LibO 4.4.3.2
Comment 16 tommy27 2015-06-25 21:53:25 UTC
warning is not present in LibO 4.2.7.2 and is present in 4.3.0.4 hence a 4.3.x regression that needs bibisecting

issue also persists in today's 5.1.0.0 daily build
Comment 17 gmarco 2015-06-26 10:51:43 UTC
(In reply to tommy27 from comment #16)
> warning is not present in LibO 4.2.7.2 and is present in 4.3.0.4 hence a
> 4.3.x regression that needs bibisecting
> 
> issue also persists in today's 5.1.0.0 daily build

Tommy, fine work, thanks.
But a curiosity: which neologism is bibisecting?
the verb does not exist, what does it mean?
Comment 18 tommy27 2015-06-26 11:10:40 UTC
(In reply to gmarco from comment #17)
> 
> But a curiosity: which neologism is bibisecting?
> the verb does not exist, what does it mean?

it's a method to identify the committ which caused a regression.
more infos here: https://wiki.documentfoundation.org/QA/Bibisect
Comment 19 Robinson Tryon (qubit) 2015-12-14 05:32:35 UTC Comment hidden (obsolete)
Comment 20 Joel Madero 2015-12-20 17:26:47 UTC
Definitely Windows only. Can't repro:

Bodhi Moksha
Version: 5.2.0.0.alpha0+
Build ID: 5df326438fd3a5613a52b4de1935426911ff1301

I don't think that this is bibisectable as the Windows bibisect package doesn't go back this far. See https://wiki.documentfoundation.org/QA/Bibisect/Windows
Comment 21 Xisco Faulí 2016-09-13 10:53:02 UTC
This regression was introduced before branch 4.4, thus it can't be bibisected with the current bibisect repositories. Changing keyword 'notBibisectable' to 'preBibisect'
Comment 22 gmarco 2017-01-07 22:40:36 UTC
Still in LO 5.2.3.3 Win10.
Tha same warning as in the past, both saving as .xls and .ods
Comment 23 gmarco 2017-02-23 21:51:44 UTC
Why this bug is assigned to myself?
Comment 24 m.a.riosv 2017-02-23 22:12:13 UTC
Because you do it, take a look to the history, top-right.
Comment 25 gmarco 2017-02-23 22:22:02 UTC
(In reply to m.a.riosv from comment #24)
> Because you do it, take a look to the history, top-right.

OK, thanks, but I do not know how and why this happened.
I can not fix the bug, so I think corrected unassign myself.
Comment 26 QA Administrators 2018-02-24 03:34:22 UTC Comment hidden (obsolete)
Comment 27 gmarco 2018-02-24 11:50:46 UTC
Sorry but the post is 3 years old and since then I do not use that file anymore, downloading the one attached in 2015 does not reflect the problem anymore.
But many conditions have changed: libo was v.4.3 and Win 8.1, now I have v.5.4 and Win 10, then a "guilty" was, now it will remain "mysterious and unpunished" and so "worksforme".
Greetings.
Comment 28 gmarco 2018-02-24 18:53:38 UTC
Unfortunately I said all that too soon, the problem is still such (I had forgotten to save by Save As).
Following the steps as per comment 10 the warning occurs both in LO5442 and in LO 5451 (see the new screenshots), the only difference is the text, a mix EN-IT, and it occurs also opening/saving an ods file as said per comment 12.
Comment 29 gmarco 2018-02-24 18:56:18 UTC
Created attachment 140119 [details]
screenshot
Comment 30 gmarco 2018-02-24 18:58:18 UTC
Created attachment 140120 [details]
screenshot
Comment 31 gmarco 2018-02-24 21:18:06 UTC
Further information: same warning also in LODev Version: 6.1.0.0.alpha0 + (x64)
Comment 32 Xisco Faulí 2018-02-26 10:44:12 UTC
Putting back to NEW...
Comment 33 Buovjaga 2019-04-14 19:13:13 UTC
Warning is already present in 4.2.0.0alpha1 (first commit of win32-4.3 bibisect repo)

What's more, the warning is present already in 3.5.0 and 3.3.0!

What's EVEN more is that the warning is also present on Linux!!@@

Arch Linux 64-bit
Version: 6.3.0.0.alpha0+
Build ID: 9030ffb1a1b282eb2c6d1773930b0de0d42df447
CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3; 
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Calc: threaded
Built on 13 April 2019