Description: Crash in SwXTextDocument::~SwXTextDocument() Steps to Reproduce: 1. Open Writer 2. Enable Logo toolbar 2. Go to Options -> Language Settings -> Language 3. Set user interface to a non-default language 4. Restart 5. Go to Options -> Language Settings -> Language 6. Change locale to some non-default language 7. Click logo toolbar 8. Type: ZZZ and hit enter 9. Close the warning-dialog box 10. Close LibreOffice 11. Launch LibO Actual Results: Crash report is generated: crashreport.libreoffice.org/stats/crash_details/66a8c034-3846-43b6-b5b5-e845dfa3473b Expected Results: No crash report Reproducible: Always User Profile Reset: No Additional Info: Versie: 5.3.3.1 Build ID: 46360c72c4823cefeaa85af537fba22bd568da7e CPU Threads: 4; Versie besturingssysteem:Windows 6.2; UI Render: standaard; Layout-Engine: nieuw; Locale: hil-PH (nl_NL); Calc: CL User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Not reproduced with: Version: 5.3.2.2 (x64) Build ID: 6cd4f1ef626f15116896b1d8e1398b56da0d0ee1 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; Layout Engine: new; Locale: bvx-CG (fi_FI); Calc: group Or: Version: 5.3.3.1 (x64) Build-ID: 46360c72c4823cefeaa85af537fba22bd568da7e CPU-Threads: 4; BS-Version: Windows 6.19; UI-Render: Standard; Layout-Engine: neu; Gebietsschema: sdj-CG (fi_FI); Calc: group For the second test I first changed everything back to how they were.
Reproduced using 5.3.3.2 / Windows 7. Two crash reports: http://crashreport.libreoffice.org/stats/crash_details/2a54db9d-8296-40e3-8e56-1c5dcd1eb142 http://crashreport.libreoffice.org/stats/crash_details/ed598c79-5701-46e2-981b-d3bd1fb0e1e3 Seems like the crash is related to changing locale, and not restarting before invoking Logo. Fortunately there are very few crash reports, as it's a rare situation.
** 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! Warm Regards, QA Team MassPing-UntouchedBug
Any update with 6.0.5?
Dear Telesto, 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! Warm Regards, QA Team MassPing-UntouchedBug
Needinfo for retest and simpler steps.
Telesto: I do not reproduce with the recent supported version (6.4.7) on Win7 and Fedora 32, under zh-CN locale. Could you please retest? If it works on recent versions, then please mark this as RESOLVED WORKSFORME.
No repro Version: 7.1.0.0.alpha1+ (x64) Build ID: eeed9103350d886f5913aed9b525d863a421dffa CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: el-GR Calc: CL