Description: It is not possible to export a selected area as png Steps to Reproduce: 1. Selet an area 2. File -> Export... Filetype -> PNG 3. Save Actual Results: Crash. The export is not done. Expected Results: The selected area exported as png Reproducible: Always User Profile Reset: No Additional Info: Version: 6.3.2.2 Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU threads: 4; OS: Mac OS X 10.15.1; UI render: default; VCL: osx; Locale: nl-NL (nl_NL.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 155464 [details] This popup is shown a few seconds after pressing 'Save'
Does not apply to Version: 6.3.2.2 (x64) under win 7.
I can confirm it in Version: 6.4.0.0.alpha1+ Build ID: 80109586e6cb6d3e2e0a53a9079c3125ec9b8368 CPU threads: 4; OS: Mac OS X 10.15.1; UI render: default; VCL: osx; Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US Calc: threaded but LO crashed not every time when I tried export to PNG
I tried like 10 times, I could only reproduce it once Version: 6.4.0.0.alpha1+ Build ID: a0ebc6f898992dbc0da9f252911da867dfdfd741 CPU threads: 8; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; Locale: en-US (en_ES.UTF-8); UI-Language: en-US Calc: threaded
(In reply to Xisco Faulí from comment #4) > I tried like 10 times, I could only reproduce it once > > Version: 6.4.0.0.alpha1+ > Build ID: a0ebc6f898992dbc0da9f252911da867dfdfd741 > CPU threads: 8; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; > Locale: en-US (en_ES.UTF-8); UI-Language: en-US > Calc: threaded This is a different Mac OS X. On 10.15.1 is crashes all the time. The application is not usable. Please increase the Severity / Priority back again. Thanks.
Do you still have this issue? Are you using a standard or admin user account? Have you installed a language pack? Does the issue go away if you grant LO full disk access in system preferences (security & privacy)?
Dear Arjan, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This is many years old now, do you still see the issue on latest 7.5?
Dear Arjan, 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 Arjan, 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