Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 12; OS: Linux 6.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTf-8); UI: en-US 7.5.3-1 Calc: threaded LibreOffice Writer crashes when I open two windows side-by-side with one document that I wrote and sent to myself via email and a second document on the right side in which I write. Both documents use MS Office Fonts (Arial and Times New Roman). A sentence or so into the new document, the document freezes and then crashes to desktop forcing me to recover documents. Unfortunately nothing is saved and I am greeted with a blank document. I am able to reproduce it every time with the same documents. Resetting profile does not help. There is no corresponding error message. Please help!
Could not reproduce in: Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded I tried using those MS fonts, and I also tested the KF5 VCL. Can you maybe share example documents? Or can you also reproduce from two brand new documents?
(In reply to Stéphane Guillou (stragu) from comment #1) > Could not reproduce in: > > Version: 7.5.3.2 (X86_64) / LibreOffice Community > Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 > CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 > Locale: en-AU (en_AU.UTF-8); UI: en-US > Calc: threaded > > I tried using those MS fonts, and I also tested the KF5 VCL. > > Can you maybe share example documents? Or can you also reproduce from two > brand new documents? I cannot share those documents as they have sensitive information but it happens even with two documents put side by side on same desktop.
Does the crash occur when you send the document via email? If so, do you use File > Send > Email document, or something else? Which email client? Is one of the documents in read-only mode because opened from the email client? Would be good to have more precise steps for us to test, keeping them as minimal as possible (for example: is writing with MS fonts actually necessary to reproduce the crash?).
(In reply to Stéphane Guillou (stragu) from comment #3) > Does the crash occur when you send the document via email? > If so, do you use File > Send > Email document, or something else? Which > email client? Is one of the documents in read-only mode because opened from > the email client? > > Would be good to have more precise steps for us to test, keeping them as > minimal as possible (for example: is writing with MS fonts actually > necessary to reproduce the crash?). The crash occurs when I either open two documents side by side (one is from email and the other is a new document) or when I start typing on a entirely new single document. I am not sure if the document is in read-only mode. But it allows me to type on it. The Email client i use is Mailspring. I use only MS fonts but also LanguageTool and Zotero extension. Maybe those are the culprits?
(In reply to agapp11 from comment #4) > I use only MS fonts but also LanguageTool and Zotero extension. Maybe those > are the culprits? If you've tested with a new profile (Help > Restart in Safe mode > Reset to factory setting (with both options ticked) > Apply changes and restart) and could still reproduce the issue, it should be unrelated to the extensions. Do you see a crash reporter window when you restart LO? If so, please report the crash and share the link that the dialog gives you. And do you still experience bug 154978 with LO 7.5.3?
(In reply to Stéphane Guillou (stragu) from comment #5) > (In reply to agapp11 from comment #4) > > I use only MS fonts but also LanguageTool and Zotero extension. Maybe those > > are the culprits? > > If you've tested with a new profile (Help > Restart in Safe mode > Reset to > factory setting (with both options ticked) > Apply changes and restart) and > could still reproduce the issue, it should be unrelated to the extensions. > > Do you see a crash reporter window when you restart LO? If so, please report > the crash and share the link that the dialog gives you. > > And do you still experience bug 154978 with LO 7.5.3? I tried testing with a new profile and I was able to complete testing a document with no freezes or crashes. However, all the extensions were turned off.
[Automated Action] NeedInfo-To-Unconfirmed
Created attachment 187283 [details] MY LO Writer document
(In reply to Stéphane Guillou (stragu) from comment #5) > (In reply to agapp11 from comment #4) > > I use only MS fonts but also LanguageTool and Zotero extension. Maybe those > > are the culprits? > > If you've tested with a new profile (Help > Restart in Safe mode > Reset to > factory setting (with both options ticked) > Apply changes and restart) and > could still reproduce the issue, it should be unrelated to the extensions. > > Do you see a crash reporter window when you restart LO? If so, please report > the crash and share the link that the dialog gives you. > > And do you still experience bug 154978 with LO 7.5.3? It seems the crash has returned. I reset my profile and reinstalled the extensions. I was trying to write "Plants have developed many chemical methods to deter heterotrophes from eat..." when writer freezes and then I get the following dialog: https://i.imgur.com/LgL4b7p.png The document is attached.
(In reply to agapp11 from comment #9) > It seems the crash has returned. I reset my profile and reinstalled the > extensions. I was trying to write "Plants have developed many chemical > methods to deter heterotrophes from eat..." when writer freezes [...] It sounds like the issue is related to the languageTool extension. Can you please: - test the new version of the extension, just released on the 14th of May and see if it still crashes: https://extensions.libreoffice.org/en/extensions/show/languagetool - if it still crashes, uninstall the extension, and use the integrated languageTool feature instead, as described on https://languagetool.org/insights/post/product-libreoffice/#how-to-enable-languagetool-on-libreoffice There are issues reported about the extensions for KDE + LibreOffice users, for example: https://github.com/languagetool-org/languagetool/issues/7827 and https://github.com/languagetool-org/languagetool/issues/6288 , I think you might be having the same problem. Please report if the extension update or the integrated languageTool option solve the issue.
Dear agapp11, 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
It seems that this issue has mostly disappeared with the new LibreOffice versions with the updated extension. However, it still appears sometimes but I haven't been able to consistently reproduce it.
Actually, testing it again I get a crash every time I enable "check spelling as you type" option. If i disable that, the crashes disappear. It seems to be related to this feature.
I tested with the following: - LO 7.6.2.1 with kf5 (cairo+xcb) VCL plugin - LT extension 6.3 - "Tools > Automatic Spell Checking" on - "Tools > Language settings > Writing aids > Check grammar as you type" on - Editing two documents in Arial at the same time (or including the sample document in comment 8) - Typed the sentence in comment 9 ... but still could not make it crash. (I did however get a "java.lang.NullPointerException" once when trying the run the LT check.) Would be great if you could collect a backtrace, if at all possible: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU/Linux:_How_to_get_a_backtrace