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?
The limit of rows for xls is 65536, verify you haven't data neither format beyond that.
(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.
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?
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.
(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?
But don't attach the xls, the needed file is ods that when saved shows the issue.
(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
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.
Then there is nothing to reproduce and verify.
(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?
Created attachment 116681 [details]
I managed to find a way to reproduce repeatedly the error.
The attached file named "SAVE_AS_test.xls" is the sample base.
- 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.
Following steps in comment#10 I can't reproduce the issue.
Please try resetting user profile, sometimes solves strange issues.
(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.
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
Created attachment 116690 [details]
zipped user profile
reproducible as in comment 10 under Win8.1 x64 using LibO 22.214.171.124
please tell which is the O/S you tested.
status NEW. edited summary notes.
(In reply to tommy27 from comment #14)
> @gmarco @m.a.riosv
> reproducible as in comment 10 under Win8.1 x64 using LibO 126.96.36.199
> please tell which is the O/S you tested.
> status NEW. edited summary notes.
I too am working under Win8.1 x64 using LibO 188.8.131.52
warning is not present in LibO 184.108.40.206 and is present in 220.127.116.11 hence a 4.3.x regression that needs bibisecting
issue also persists in today's 18.104.22.168 daily build
(In reply to tommy27 from comment #16)
> warning is not present in LibO 22.214.171.124 and is present in 126.96.36.199 hence a
> 4.3.x regression that needs bibisecting
> issue also persists in today's 188.8.131.52 daily build
Tommy, fine work, thanks.
But a curiosity: which neologism is bibisecting?
the verb does not exist, what does it mean?
(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
Migrating Whiteboard tags to Keywords: (bibisectRequest)
Definitely Windows only. Can't repro:
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
This regression was introduced before branch 4.4, thus it can't be bibisected with the current bibisect repositories. Changing keyword 'notBibisectable' to 'preBibisect'
Still in LO 184.108.40.206 Win10.
Tha same warning as in the past, both saving as .xls and .ods
Why this bug is assigned to myself?
Because you do it, take a look to the history, top-right.
(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.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
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".
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.
Created attachment 140119 [details]
Created attachment 140120 [details]
Further information: same warning also in LODev Version: 220.127.116.11.alpha0 + (x64)
Putting back to NEW...
Warning is already present in 18.104.22.168alpha1 (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
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
Built on 13 April 2019