Description: ver. 7.0 calc crashes on start, in 6.4.6 everything OK. Steps to Reproduce: 1. Start Calc with new document 2. Error opening the document Untitled 3. Actual Results: On start the document Untitled cannot be opened. Expected Results: Error message that document Untitled cannot be opened Reproducible: Always User Profile Reset: No Additional Info: Renewing the document Untitled did not help.
On which env are you? (Windows, MacOs, Linux) Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps?
I am on Linux Ubuntu 16.04.07 LTS In previous versions of LO calc OK.
Sorry I have two OS installed Ubuntu 16.04. and Zorin (Ubuntu 18.) so the bug is on Zorin not Ubuntu 16.04 as I mentioned above.
Well I have just switched to my Ubuntu 16.04, installed the version 6.4.6 and found out that base is not working. Again the error with opening the initial file. Calc and other apps are working.
You shouldn't mix bugs. Also, you've got different OS: - Ubuntu 16.04 - Ubuntu 18.04 - Zorin I think you should give a try on Ubuntu LTS 20.04, then test Calc with initial version. If ok, you can give a try with 7.0 About Base, it might be a completely different problem. About Zorin, you can give a try but if it's ok with Ubuntu, it means the bug is related to Zorin packaging.
I also have far more crashes in 7.0.3 then in 6.4 series. I don't really think its related to the one from the original reporter. I just wanted to ask if there is a bug that collects different crashes or shall we open a new bug report for every crash we encounter? I have WinDBG Output as a textfile that maybe is useful for a developer or QA-Specialist. I just don't know where to send it.
Thank you for reporting the bug. To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
(In reply to bugzilla2 from comment #6) > I also have far more crashes in 7.0.3 then in 6.4 series. I don't really > think its related to the one from the original reporter. I just wanted to > ask if there is a bug that collects different crashes or shall we open a new > bug report for every crash we encounter? I have WinDBG Output as a textfile > that maybe is useful for a developer or QA-Specialist. I just don't know > where to send it. Please submit a new bugtracker for the first crash you got. Then if you got other crashes, a priori, you don't need to open new ones if it's the same bt.
Dear jpopelka, 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 jpopelka, 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