Description: When open same MS excel files Calc gives an alert "The data could not be loaded completely because the maximum number of columns per sheet was exceeded." If we click "OK" the file open properly. But if there exist already open calc files and if you try to open that excel file from file manager the calc opens an empty page and hangs. You couldn't see the warning window. If you go to the other open calc documents one by one, in one page you see the warning window, and after clicking "OK", the hang calc document able to open. Steps to Reproduce: 1.Open any calc file 2.Open file manager on linux 3.Open a calc file which has many columns that exceeds maximum number of columns 4. Actual Results: The Calc hangs If you go to the other open calc documents one by one, in one page you see the warning window, and after clicking "OK", the hanged calc document become open. Expected Results: Open a calc document Reproducible: Always User Profile Reset: Yes Additional Info:
Created attachment 145821 [details] ScreenShots that showing the bug
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Created attachment 145824 [details] Sample XLSX document To test the bug: First open other Calc documents Then open this document from file manager
I ve added sample XLSX document. Also I ve added screenshots
(In reply to Pap Alagi from comment #3) > Created attachment 145824 [details] > Sample XLSX document > > To test the bug: > > First open other Calc documents > Then open this document from file manager This file does not exceed the maximum number of columns, so I cannot confirm the problem.
it seems to be fine in Version: 6.3.0.0.alpha0+ Build ID: 31d3369803ce4eceab5ef708f2cd33748b6d10ea CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Pap Alagi, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Pap Alagi, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp