[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on KDE with LanguageTool extension
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||8164 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on KDE with LanguageTool extension
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #14 from Buovjaga --- I installed the latest snapshot from https://internal1.languagetool.org/snapshots/ I get a Java index out of bounds error, when opening the example DOCX, but I don't get a crash when closing. Arch Linux 64-bit, X11 Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e5e324a3420fc74fc147601bb125421e87060d93 CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 6 July 2023 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on KDE with LanguageTool extension
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5224 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on KDE with LanguageTool extension
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|Crash when closing a|Crash when closing a |document in Writer/Impress |document in Writer/Impress |with the message "Soffice |with the message "Soffice |closed unexpectedly" on kde |closed unexpectedly" on KDE ||with LanguageTool extension Version|unspecified |7.5.2.2 release Component|Writer |LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Blocks||102495, 133092 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102495 [Bug 102495] [META] KDE VCL backend bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=133092 [Bug 133092] [META] Crash bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 Julien Nabet changed: What|Removed |Added CC|serval2...@yahoo.fr | --- Comment #13 from Julien Nabet --- I gave a try on pc Debian x86-64 with master sources updated today but got hangings so couldn't retrieve any backtrace. It seems Java in LO isn't the best idea, above all when trying to debug with gdb. Since I can't do anything here=>uncc myself. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 --- Comment #12 from agap...@hotmail.com --- Created attachment 186947 --> https://bugs.documentfoundation.org/attachment.cgi?id=186947=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.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 --- Comment #11 from Julien Nabet --- (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) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978
--- Comment #10 from agap...@hotmail.com ---
(In reply to Julien Nabet from comment #9)
> (In reply to agapp11 from comment #8)
> > ...
> > I copy/pasted the above command, hit enter and nothing happened in the
> > terminal. Opened LibreOffice and opened the Test Document I always used
> > (that previously elicited a crash). The Crash is gone when closing the
> > document. I am not sure what changed.
>
> "export SAL_USE_VCLPLUGIN=gen" tells to Linux to create a environment
> variable in memory named SAL_USE_VCLPLUGIN with the value "gen".
> When you launch LO from the terminal, LO will find this environment variable
> and instead of using KDE for the UI rendering, it will use something generic
> ("gen").
> This environment variable will be available until you close the term/console
> or unset it manually with a Linux command.
>
> So if you have no more crash with this, it seems specific to KDE and at
> least you've got a workaround.
> For gdbtrace, badfully, I didn't see something obvious but I'm not an expert
> so perhaps someone may help here.
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.
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
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978
--- Comment #9 from Julien Nabet ---
(In reply to agapp11 from comment #8)
> ...
> I copy/pasted the above command, hit enter and nothing happened in the
> terminal. Opened LibreOffice and opened the Test Document I always used
> (that previously elicited a crash). The Crash is gone when closing the
> document. I am not sure what changed.
"export SAL_USE_VCLPLUGIN=gen" tells to Linux to create a environment variable
in memory named SAL_USE_VCLPLUGIN with the value "gen".
When you launch LO from the terminal, LO will find this environment variable
and instead of using KDE for the UI rendering, it will use something generic
("gen").
This environment variable will be available until you close the term/console or
unset it manually with a Linux command.
So if you have no more crash with this, it seems specific to KDE and at least
you've got a workaround.
For gdbtrace, badfully, I didn't see something obvious but I'm not an expert so
perhaps someone may help here.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 --- Comment #8 from agap...@hotmail.com --- (In reply to Julien Nabet from comment #6) > Could you attach gdbtrace.log generated by using this link ? > https://bugs.documentfoundation.org/attachment.cgi?bugid=154978=enter > Indeed, we see not much in the backtrace but perhaps there's more in > gdbtrace.log > > Also, just to be sure it's not specific to KDE, could you try this > - open a term/console > - export SAL_USE_VCLPLUGIN=gen > - launch LO and test LanguageTool > ? I added the gdbtrace.log file. > - export SAL_USE_VCLPLUGIN=gen > - launch LO and test LanguageTool > ? I copy/pasted the above command, hit enter and nothing happened in the terminal. Opened LibreOffice and opened the Test Document I always used (that previously elicited a crash). The Crash is gone when closing the document. I am not sure what changed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 --- Comment #7 from agap...@hotmail.com --- Created attachment 186935 --> https://bugs.documentfoundation.org/attachment.cgi?id=186935=edit gdbtrace.log -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 --- Comment #6 from Julien Nabet --- Could you attach gdbtrace.log generated by using this link ? https://bugs.documentfoundation.org/attachment.cgi?bugid=154978=enter Indeed, we see not much in the backtrace but perhaps there's more in gdbtrace.log Also, just to be sure it's not specific to KDE, could you try this - open a term/console - export SAL_USE_VCLPLUGIN=gen - launch LO and test LanguageTool ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 --- Comment #4 from agap...@hotmail.com --- (In reply to Julien Nabet from comment #2) > What's your LO version? > Could you check you use recent LO version, 7.4.6 or even brand new 7.5.2? > Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps to > exclude things like corrupted LO profile. > > Then how do you use Languagetool? I mean, until recently Languagetool was an > extension to install on LO, now it's an api to call from > Tools/Options/Language Settings/LanguageTool Server > and here you must check "Enable LanguageTool" option then put the Base URL. > By default the free one (because there's also premium one), it's > https://api.languagetool.org/v2. > > Finally, would it be possible you attach a backtrace by following > https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU/Linux: > _How_to_get_a_backtrace ? >LO version: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTf-8); UI: en-US 7.5.2-1 Calc: threaded > Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps to > exclude things like corrupted LO profile. I have tried deleting the profile in /home//.config/libreoffice/4/user/ The moment I reinstall LanguageTool the issue appears again. >Then how do you use Languagetool? I mean, until recently Languagetool was an > extension to install on LO, now it's an api to call from I use it as an extension from the official site. I have also tried the latest SNAPSHOT versions as well from https://internal1.languagetool.org/snapshots/ >> extension to install on LO, now it's an api to call from > Tools/Options/Language Settings/LanguageTool Server > and here you must check "Enable LanguageTool" option then put the Base URL. > By default the free one (because there's also premium one), it's > https://api.languagetool.org/v2. I have the Server also enabled and the issue persists >Finally, would it be possible you attach a backtrace by following Here is the backtrace warning: Currently logging to gdbtrace.log. Turn the logging off and on to make the new setting effective. Downloading separate debug info for /lib64/ld-linux-x86-64.so.2... Downloading separate debug info for system-supplied DSO at 0x77fc8000... Downloading separate debug info for /usr/lib/libreoffice/program/libuno_sal.so.3... Downloading separate debug info for /usr/lib/libreoffice/program/libsofficeapp.so... Downloading separate debug info for /usr/lib/libc.so.6... [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Downloading separate debug info for /usr/lib/libz.so.1... Downloading separate debug info for /usr/lib/libm.so.6... Downloading separate debug info for /usr/lib/libdbus-1.so.3... Downloading separate debug info for /usr/lib/libicuuc.so.72... Downloading separate debug info for /usr/lib/libreoffice/program/libclewlo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libcomphelper.so... Downloading separate debug info for /usr/lib/libreoffice/program/libuno_cppu.so.3... Downloading separate debug info for /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3... Downloading separate debug info for /usr/lib/libreoffice/program/libdeploymentmisclo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libeditenglo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libfwklo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libi18nlangtag.so... Downloading separate debug info for /usr/lib/libreoffice/program/libopencllo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libuno_salhelpergcc3.so.3... Downloading separate debug info for /usr/lib/libreoffice/program/libsblo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libsfxlo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libsvllo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libsvxlo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libsvxcorelo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libsvtlo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libtklo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libtllo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libucbhelper.so... Downloading separate debug info for /usr/lib/libreoffice/program/libutllo.so... Downloading separate debug info for /usr/lib/libreoffice/program/libvcllo.so... Downloading separate debug info for /usr/lib/libsystemd.so.0... Downloading separate debug info for /usr/lib/libicudata.so.72... Downloading separate debug info for /usr/lib/libgpgmepp.so.6... Downloading separate debug info for /usr/lib/libnss3.so... Downloading separate
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 --- Comment #3 from agap...@hotmail.com --- (In reply to Robert Großkopf from comment #1) > Do you close the whole LO or is there anything opened of LO and crashes? > > I'm also using KDE (OpenSuSE 15.4). For some apps it will report every time > a crash when closing this apps through the special closing cross of the > window. But I have only closed the app … In the github thread I linked in the OP, there is a screen capture posted of what happens when closing LO Writer. But yes, I usually get a crash when clicking on the X "close window" button in the titlebar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 Julien Nabet changed: What|Removed |Added Keywords||wantBacktrace CC||serval2...@yahoo.fr --- Comment #2 from Julien Nabet --- What's your LO version? Could you check you use recent LO version, 7.4.6 or even brand new 7.5.2? Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps to exclude things like corrupted LO profile. Then how do you use Languagetool? I mean, until recently Languagetool was an extension to install on LO, now it's an api to call from Tools/Options/Language Settings/LanguageTool Server and here you must check "Enable LanguageTool" option then put the Base URL. By default the free one (because there's also premium one), it's https://api.languagetool.org/v2. Finally, would it be possible you attach a backtrace by following https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU/Linux:_How_to_get_a_backtrace ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 Robert Großkopf changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154978] Crash when closing a document in Writer/Impress with the message "Soffice closed unexpectedly" on kde
https://bugs.documentfoundation.org/show_bug.cgi?id=154978 Robert Großkopf changed: What|Removed |Added CC||rob...@familiegrosskopf.de --- Comment #1 from Robert Großkopf --- Do you close the whole LO or is there anything opened of LO and crashes? I'm also using KDE (OpenSuSE 15.4). For some apps it will report every time a crash when closing this apps through the special closing cross of the window. But I have only closed the app … -- You are receiving this mail because: You are the assignee for the bug.
