https://bugs.documentfoundation.org/show_bug.cgi?id=154978
--- Comment #12 from [email protected] --- Created attachment 186947 --> https://bugs.documentfoundation.org/attachment.cgi?id=186947&action=edit Test LO document (In reply to Julien Nabet from comment #11) > (In reply to agapp11 from comment #10) > > ... > > I wasn't aware I needed to launch LO from terminal. I exported the variable > > again (copy/pasted to terminal) and then launched LO from terminal. > Again what I described is a workaround, if there wasn't the bug, you > wouldn't need to do this. The goal was to test if it was KDE rendering on LO > related pb and a workaround so you're not stuck but of course, the bug isn't > fixed. > > > > > When launching the program again and opening the Test Document, it seems to > > cause no issues (but I am not sure if LanguageTool is working correctly) > > > > I also get the following responses in Terminal after closing LibreOffice: > > (soffice.bin:299655): Gtk-WARNING **: 07:57:27.898: Theme parsing error: > > gtk.css:1649:16: '-gtk-icon-size' is not a valid property name > > > > (soffice.bin:299655): Gtk-WARNING **: 07:57:27.898: Theme parsing error: > > gtk.css:1652:16: '-gtk-icon-size' is not a valid property name > > > > (soffice.bin:299655): Gtk-WARNING **: 07:57:28.131: Theme parsing error: > > gtk.css:1649:16: '-gtk-icon-size' is not a valid property name > > > > (soffice.bin:299655): Gtk-WARNING **: 07:57:28.131: Theme parsing error: > > gtk.css:1652:16: '-gtk-icon-size' is not a valid property name > That's something else but ok. > > BTW, I installed LanguageTool-20230425-snapshot.oxt by following these steps: > - select menu Tools/Extensions > - click button "Add" > - choose "for me only" > I also enabled LanguageTool Server by checking "Enable LanguageTool" and let > the by default url https://api.languagetool.org/v2 > > Then I did: > - open a term/console > - export SAL_USE_VCLPLUGIN=kf5 (this one is to force LO to use KDE libs for > the rendering since by default I use gtk rendering) > - launch Writer > - type some text with error > - close > => no crash. > > Do you reproduce the crash with an empty doc or just with a specific > document? > If just a specific document, would it be possible you attach the file? > (after having sanitized it if needed, see > https://wiki.documentfoundation.org/QA/Bugzilla/ > Sanitizing_Files_Before_Submission) > That's something else but ok. Apologies. I am new to submitting bug reports. > BTW, I installed LanguageTool-20230425-snapshot.oxt by following these steps: > - select menu Tools/Extensions > - click button "Add" > - choose "for me only" > I also enabled LanguageTool Server by checking "Enable LanguageTool" and let > the by default url https://api.languagetool.org/v2 > > Then I did: > - open a term/console > - export SAL_USE_VCLPLUGIN=kf5 (this one is to force LO to use KDE libs for > the rendering since by default I use gtk rendering) > - launch Writer > - type some text with error > - close > => no crash. I installed the extension by downloading from the website and then double clicking on it in the ~./Downloads folder. An "Extension" popup appears that then prompts me to install the addon and requires a restart of LO. I also followed the steps of enabling the server that you listed. > Do you reproduce the crash with an empty doc or just with a specific > document? > If just a specific document, would it be possible you attach the file? > (after having sanitized it if needed, see > https://wiki.documentfoundation.org/QA/Bugzilla/ > Sanitizing_Files_Before_Submission) This happens to any file with text. If there is no text, closing the app does not result in a crash. Here is the file I generally use for testing. The same issue occurs with .odt file format as well. -- You are receiving this mail because: You are the assignee for the bug.
