Description: Open libreoffice from command line, try to select to create a new writer doc. Writer seems to open but it freezes and crashes (or directly crashes). According to "top" command, soffice.bin is still working (and draining CPU). Also killall soffice.bin command does nothing (to force libreoffice to shutdown I have to kill -9 PID number). Steps to Reproduce: 1.from command line open libreoffice (kf5, in kde-plasma, wayland) 2.select a new writer doc 3. Actual Results: libreoffice freezes and crashes or directly crashes Expected Results: Libreoffice's working Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) Locale: es-ES (es_ES.UTF-8); UI: es-ES 7.2.1-2 Calc: threaded
Created attachment 175592 [details] screencast showing
Can't reproduce with current master on current Debian testing (plasma-desktop 4:5.21.5-2) What's your Linux distro and Plasma version? Can you possibly retest with a current daily build? Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 5041b1491a183366ca44380bd0f5dfb7c0acc5fb CPU threads: 12; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded
(In reply to Michael Weghorn from comment #2) > Can't reproduce with current master on current Debian testing > (plasma-desktop 4:5.21.5-2) > > What's your Linux distro and Plasma version? Can you possibly retest with a > current daily build? > > Version: 7.3.0.0.alpha0+ / LibreOffice Community > Build ID: 5041b1491a183366ca44380bd0f5dfb7c0acc5fb > CPU threads: 12; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) > Locale: en-GB (en_GB.UTF-8); UI: en-US > Calc: threaded Sorry for being back late. I am on arch linux with Kde Plasma 5.23.2, kde frameworks 5.87.0 and QT 5.15.2. And the bug is still there (libreoffice constantly crashes).
(In reply to Michael Weghorn from comment #2) > Can't reproduce with current master on current Debian testing > (plasma-desktop 4:5.21.5-2) > > What's your Linux distro and Plasma version? Can you possibly retest with a > current daily build? > > Version: 7.3.0.0.alpha0+ / LibreOffice Community > Build ID: 5041b1491a183366ca44380bd0f5dfb7c0acc5fb > CPU threads: 12; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) > Locale: en-GB (en_GB.UTF-8); UI: en-US > Calc: threaded Sorry for being back late. The bug is still there. Libreoffice crashes constantly Operating System: Arch Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7500 CPU @ 3.40GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630
[Automated Action] NeedInfo-To-Unconfirmed
Thanks for testing. Today, Plasma 5.23 made it to Debian testing, but I still cannot reproduce after that update. When watching your video once again, I realized output related to SLF4J in the terminal from which you started LibreOffice. It's currently unclear to me how that is related to LibreOffice. Do you have any (Java) extensions installed in LibreOffice? Does the problem also happen with a fresh user profile?
Also, does this also happen when you use an X11 Plasma session instead of a Wayland one, or starting LO with environment variable 'QT_QPA_PLATFORM=xcb' set? (Please double-check that "About" -> "LibreOffice" actually has "VCL: kf5 (cairo+xcb)" instead of "VCL: kf5 (cairo+wayland)" then.)
(In reply to Michael Weghorn from comment #6) > Thanks for testing. > > Today, Plasma 5.23 made it to Debian testing, but I still cannot reproduce > after that update. > > When watching your video once again, I realized output related to SLF4J in > the terminal from which you started LibreOffice. It's currently unclear to > me how that is related to LibreOffice. > > Do you have any (Java) extensions installed in LibreOffice? Does the problem > also happen with a fresh user profile? Thank you. Before starting testing, I just would like to let you know that libreoffice crashing seems to be now more "verbose" in the terminal. So first of all, I post the message that I actually receive: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() This plugin supports grabbing the mouse only for popup windows This plugin supports grabbing the mouse only for popup windows SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. [xcb] Unknown sequence number while processing reply [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. soffice.bin: xcb_io.c:725: _XReply: La declaración `!xcb_xlib_threads_sequence_lost' no se cumple. [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. soffice.bin: xcb_io.c:269: poll_for_event: La declaración `!xcb_xlib_threads_sequence_lost' no se cumple. 45 -- exe=/usr/lib/libreoffice/program/soffice.bin 17 -- platform=wayland 20 -- appname=soffice.bin 37 -- apppath=/usr/lib/libreoffice/program 9 -- signal=6 9 -- pid=2394 12 -- startupid=0 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = soffice.bin path = /usr/lib/libreoffice/program pid = 2394 KCrash: Arguments: /usr/lib/libreoffice/program/soffice.bin --nocrashhandler
(In reply to giors_00 from comment #8) > Thank you. Before starting testing, I just would like to let you know that > libreoffice crashing seems to be now more "verbose" in the terminal. So > first of all, I post the message that I actually receive: > > qt.qpa.wayland: Wayland does not support QWindow::requestActivate() > qt.qpa.wayland: Wayland does not support QWindow::requestActivate() > qt.qpa.wayland: Wayland does not support QWindow::requestActivate() > This plugin supports grabbing the mouse only for popup windows > This plugin supports grabbing the mouse only for popup windows > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further > details. > [xcb] Unknown sequence number while processing reply > [xcb] Most likely this is a multi-threaded client and XInitThreads has not > been called > [xcb] Aborting, sorry about that. > soffice.bin: xcb_io.c:725: _XReply: La declaración > `!xcb_xlib_threads_sequence_lost' no se cumple. > [xcb] Unknown sequence number while processing queue > [xcb] Most likely this is a multi-threaded client and XInitThreads has not > been called > [xcb] Aborting, sorry about that. > soffice.bin: xcb_io.c:269: poll_for_event: La declaración > `!xcb_xlib_threads_sequence_lost' no se cumple. > (...) This looks weird, some X11/xcb library calls mixed with Qt's Wayland QPA. When running LO with the qt5 VCL plugin using the Wayland QPA, no xcb functionality should be used directly, so this very much looks like some other application/extension/... somehow getting into the way here
(In reply to Michael Weghorn from comment #6) > Thanks for testing. > > Today, Plasma 5.23 made it to Debian testing, but I still cannot reproduce > after that update. > > When watching your video once again, I realized output related to SLF4J in > the terminal from which you started LibreOffice. It's currently unclear to > me how that is related to LibreOffice. > > Do you have any (Java) extensions installed in LibreOffice? Does the problem > also happen with a fresh user profile? Java testing: 1.Available Java environments: java-11-openjdk (default) java-17-openjdk java-7-openjdk java-8-openjdk Video is recorded with java-17-openjdk (libreoffice identifies it as N/A 17) selected in libreoffice. Nothing changes with "Oracle Corporation 11.0.12" selected. Libreoffice crashes (not exactly the same, but unusable). The same occurs with "Oracle Corporation 1.8.9_292" selected. With no java environment selected, it seems to work just fine (at least, I am able to open writer): I should test it a little deeper but it seems fine. New profile: tried with all kind of java but it crashes as usual. With no java selected, works fine. So, since the problem seems to be related with java, I tried having uninstalled languagetool (previously installed from aur repos) and I have to tell you that now all seems fine (obviously need to test it deeply) no metter which java version is selected. So apparently, it is a languagetool issue (quite strange though, since with gnome it seems to work just perfectly). By the way, I confirm that problem is not related with profile (going back to my old profile does not change anything: without languagetool, it just works). Just to complete the test, I decided to try reinstalling languagetool but manually (instead of from aur repository from libreoffice-extensions' page). Download speed is quite annoying (never faster than 350kb/sec.). Crashing is back. Finally: sorry for my inexperience (I am just a final user) but IMHO problem seems to be related with languagetool extension's behaviour with kf5 skin. Do you think it can be possible?
(In reply to Michael Weghorn from comment #7) > Also, does this also happen when you use an X11 Plasma session instead of a > Wayland one, or starting LO with environment variable 'QT_QPA_PLATFORM=xcb' > set? (Please double-check that "About" -> "LibreOffice" actually has "VCL: > kf5 (cairo+xcb)" instead of "VCL: kf5 (cairo+wayland)" then.) With "QT_QPA_PLATFORM=xcb" no problem (even with languagetool installed). In X11 session, no problem (even with languagetool installed)
(In reply to giors_00 from comment #10) > So, since the problem seems to be related with java, I tried having > uninstalled languagetool (previously installed from aur repos) and I have to > tell you that now all seems fine (obviously need to test it deeply) no > metter which java version is selected. So apparently, it is a languagetool > issue (quite strange though, since with gnome it seems to work just > perfectly). Since you mention it works in GNOME: Does it also work in a Plasma session when started with environment variable SAL_USE_VCPLUGIN=gtk3 set? (please double-check that gtk3 actually shows up in "Help" -> "About LibreOffice") > Just to complete the test, I decided to try reinstalling languagetool but > manually (instead of from aur repository from libreoffice-extensions' page). > Download speed is quite annoying (never faster than 350kb/sec.). Crashing is > back. I quickly tried with current LO master and languagetool 5.5.1. I ran into an assertion here with my debug build that seems to be unrelated to the problem you're encountering (on both X11 and Wayland, but this only happens after clicking around in the menu a bit, and after silencing the assert, it seems to work OK so far, so that should not have hit you with a release build of LibreOffice). Could you try collecting a backtrace and attach it here, as described at [1]? That might give a clue on why you're running into this (from comment 8): [xcb] Unknown sequence number while processing reply [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. soffice.bin: xcb_io.c:725: _XReply: La declaración `!xcb_xlib_threads_sequence_lost' no se cumple. [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. soffice.bin: xcb_io.c:269: poll_for_event: La declaración `!xcb_xlib_threads_sequence_lost' no se cumple. > Finally: sorry for my inexperience (I am just a final user) but IMHO problem > seems to be related with languagetool extension's behaviour with kf5 skin. > Do you think it can be possible? Yes, that's what it looks like and is definitely possible. Thanks a lot for your investigations, that's exactly what helps to narrow down the issue! :) [1] https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace
Created attachment 176107 [details] gdbtrace Here's the gdbtrace.log file
(In reply to Michael Weghorn from comment #12) > > > Since you mention it works in GNOME: Does it also work in a Plasma session > when started with environment variable SAL_USE_VCPLUGIN=gtk3 set? (please > double-check that gtk3 actually shows up in "Help" -> "About LibreOffice") > Unable to double check (globalmenu and menu not working which should mean I'm using gtk3 skin). Works well. No crash. > Could you try collecting a backtrace and attach it here, as described at [1]? I don't know if I did it correctly. Please find attached the gdbtrace.log file (please confirm if it's ok). > Thanks a lot for your investigations, that's exactly what helps to narrow > down the issue! :) Thanks to you. Now (without languagetool) I can use plasma-wayland and libreoffice.
(In reply to giors_00 from comment #14) > I don't know if I did it correctly. Please find attached the gdbtrace.log > file (please confirm if it's ok). Thanks. It turns out that this scenario needs an extra step to get a more useful backtrace, since the JVM (Java Virtual Machine) uses segfaults by itself that are not relevant to the crash discussed here... Anyway, I have set up a VM running arch, and could reproduce the issue there in a Wayland session. It's not 100% reproducible, sometimes crashes, sometimes hangs, sometimes seems to work fine, sometimes runs into an assertion... It seems to be more reprocuible with a release/non-debug build, I've used the current daily build from here: https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@tb87-TDF/current/LibreOfficeDev_7.3.0.0.alpha1_Linux_x86-64_deb.tar.gz Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: 23214f1c14c4d3981dad90b6e3ba6e4ca2c8c30e CPU threads: 2; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Command used: gdb -ex 'handle SIGSEGV nostop' -ex 'r' --args ./opt/libreofficedev7.3/program/soffice.bin --writer --norestore GDB log: ~/gdb.log ----- Also "sometimes" reproducible with a debug build downloaded from here: https://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@tb87-TDF-dbg/current/LibreOfficeDev_7.3.0.0.alpha1_Linux_x86-64_archive.tar.gz Version: 7.3.0.0.alpha1+ / LibreOffice Community Build ID: 23214f1c14c4d3981dad90b6e3ba6e4ca2c8c30e CPU threads: 2; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded I'll attach the backtrace for the latter.
Created attachment 176121 [details] gdb backtrace for daily debug build as of 23214f1c14c4d3981dad90b6e3ba6e4ca2c8c30e on Arch Linux
(In reply to Michael Weghorn from comment #17) > Created attachment 176121 [details] > gdb backtrace for daily debug build as of > 23214f1c14c4d3981dad90b6e3ba6e4ca2c8c30e on Arch Linux At a quick glance, this looks like 'QEventDispatcherGlib::processEvents' calls into glib and that one does some kind of processing of X11 events, even if Qt uses the Wayland QPA.
Created attachment 176122 [details] gdb backtrace for master debug build as of ab32d1c01814d576b0b82c99e1849a8a71b12188 on Debian testing (In reply to Michael Weghorn from comment #16) > Anyway, I have set up a VM running arch, and could reproduce the issue there > in a Wayland session. It's not 100% reproducible, sometimes crashes, > sometimes hangs, sometimes seems to work fine, sometimes runs into an > assertion... > This is the backtrace of the assertion that I get at times. I can reliably reproduce this one on my Debian testing in an X11 session, not in a Wayland session, though.
(In reply to Michael Weghorn from comment #19) > Created attachment 176122 [details] > gdb backtrace for master debug build as of > ab32d1c01814d576b0b82c99e1849a8a71b12188 on Debian testing > [...] > This is the backtrace of the assertion that I get at times. I can reliably > reproduce this one on my Debian testing in an X11 session, not in a Wayland > session, though. Pending Gerrit change to fix this aspect: https://gerrit.libreoffice.org/c/core/+/124750 The other issues described earlier *might* be unrelated, though, I can't say so far.
Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/324e2a5c3e6355e6b38db0add100465224841364 tdf#144994 QtInstance::CreateMenu needs SolarMutex It will be available in 7.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Commit Notification from comment #21) > Michael Weghorn committed a patch related to this issue. > It has been pushed to "master": > > https://git.libreoffice.org/core/commit/ > 324e2a5c3e6355e6b38db0add100465224841364 > > tdf#144994 QtInstance::CreateMenu needs SolarMutex > > It will be available in 7.3.0. > > The patch should be included in the daily builds available at > https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More > information about daily builds can be found at: > https://wiki.documentfoundation.org/Testing_Daily_Builds > > Affected users are encouraged to test the fix and report feedback. I really would like to contribute by testing: could you please advice me about how to install the alpha-daily release on archlinux (only deb/rpm package are available and debtap+pacman -u maybe is not the best way to proceed for testing)? I used to try appimage versions, but according to https://libreoffice.soluzioniopen.com/daily-version/, they seem to be quite old. Sorry for bothering with such a (probably) silly question.
(In reply to giors_00 from comment #22) > I really would like to contribute by testing: could you please advice me > about how to install the alpha-daily release on archlinux (only deb/rpm > package are available and debtap+pacman -u maybe is not the best way to > proceed for testing)? I used to try appimage versions, but according to > https://libreoffice.soluzioniopen.com/daily-version/, they seem to be quite > old. > > Sorry for bothering with such a (probably) silly question. Thanks a lot for your willingness to test. It's not a silly question at all, I had to think about that myself when using the Arch VM... In the end, you can use + extract the .deb packages just like on Debian or Ubuntu as described here: https://wiki.documentfoundation.org/Installing_in_parallel/Linux (I used the Debian packages and thus the 'dpkg-deb -x' commands mentioned on that page. dpkg can be installed from the arch repo just fine.)
Does it still crash with current development versions?
Bug seems to be back. Version: 7.3.4.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.18; UI render: default; VCL: kf5 (cairo+wayland) Locale: es-ES (es_ES.UTF-8); UI: es-ES 7.3.4-2 Calc: threaded I've tried in Gnome (Wayland), Plasma X11 and Plasma Wayland (5.25) on arch linux. It seems to be working fine except in Plasma Wayland: Writer crashes immediately no matter if you're facing a new empty document or a large one).
(In reply to giors_00 from comment #25) > Bug seems to be back. > > (...) > > I've tried in Gnome (Wayland), Plasma X11 and Plasma Wayland (5.25) on arch > linux. It seems to be working fine except in Plasma Wayland: Writer crashes > immediately no matter if you're facing a new empty document or a large one). Thanks for testing. Unless it worked for you with a version in between, the issue was probably never solved in the first place. As mentioned in comment 20, the issue that I could reproduce and fix on Debian testing might be different from the root cause of the problem you're running into. Setting back to NEW, since I was able to reproduce (hopefully the same problem) in an arch VM earlier (but Writer still starts just fine for me on Debian testing in a Plasma Wayland session with the Languagetool extension installed, so *might* be somewhat related to a difference between Arch and Debian).
(In reply to Michael Weghorn from comment #26) > (In reply to giors_00 from comment #25) > > Bug seems to be back. > > > > (...) > > > > I've tried in Gnome (Wayland), Plasma X11 and Plasma Wayland (5.25) on arch > > linux. It seems to be working fine except in Plasma Wayland: Writer crashes > > immediately no matter if you're facing a new empty document or a large one). > > Thanks for testing. Unless it worked for you with a version in between, the > issue was probably never solved in the first place. As mentioned in comment > 20, the issue that I could reproduce and fix on Debian testing might be > different from the root cause of the problem you're running into. > > Setting back to NEW, since I was able to reproduce (hopefully the same > problem) in an arch VM earlier (but Writer still starts just fine for me on > Debian testing in a Plasma Wayland session with the Languagetool extension > installed, so *might* be somewhat related to a difference between Arch and > Debian). Thanks for answering. For what it's worth, I just can add that I tried: 1. with a new LO profile 2. with different versions of the extension (5.1, 5.6 and 5.7) 3. with manual installation of Languagetool and with AUR installation. Same result: crashes on plasma 5.25 Wayland IMHO, it should have something to do with plasma new (5.25) version: the crash appeared just after the system upgrade. Micheal are you on plasma 5.25 (debian uses to take something more than arch to upgrade)?
(In reply to giors_00 from comment #27) > IMHO, it should have something to do with plasma new (5.25) version: the > crash appeared just after the system upgrade. Micheal are you on plasma 5.25 > (debian uses to take something more than arch to upgrade)? Good to know. I'm currently still on Plasma 5.24.5. Will add a reminder to retest with 5.25.
Hi, thanks for this bug report. I finally can use LO without using QT_QPA_PLATFORM=xcb or setting gtk3_kde5 in /etc/profile.d/libreoffice-fresh.sh I had this issue for a long time (I think before 5.25) but uninstalling libreoffice-extension-languagetool(5.7-1) is a better workaround for now. I did the same test as giors_00 and had the same results, the problem only occurs with kf5 on wayland, if there is something to help debug I would be glad to help, although giors_00 is doing a great job, thank you both. Operating System: Arch Linux KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 Kernel Version: 5.18.7-hardened1-1-hardened (64-bit) Graphics Platform: Wayland Version: 7.3.4.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 6; OS: Linux 5.18; UI render: default; VCL: kf5 (cairo+wayland) Locale: es-ES (es_ES.UTF-8); UI: es-ES 7.3.4-2 Calc: threaded
(In reply to Michael Weghorn from comment #28) > Good to know. I'm currently still on Plasma 5.24.5. Will add a reminder to > retest with 5.25. Still no crash for me on Debian testing now having plasma-desktop 4:5.25.3-1 with LanguageTool 5.7 from the extension website and a current master build of LibreOffice. Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: 4d6243693c228703394c00164276f8326447beb9 CPU threads: 4; OS: Linux 5.18; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded
It's also resolved for me. I just reinstalled libreoffice-extension-languagetool after a few days with the same AUR package and version, and it's now fixed with no problems after 3 weeks.
giors_00, please retest with newer LO and extension, wrt to previous comments.
Dear giors_00, 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 giors_00, 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
Just tried this - Enable languagetool extension. - Open a .doc document. - insert a comment with an orthographical failure. - right click and try to substitute the misspelled word. Under plasma wayland libreoffice carshes 100% times. Under gnome just work fine
(In reply to giors_00 from comment #35) > Just tried this > > - Enable languagetool extension. > - Open a .doc document. > - insert a comment with an orthographical failure. > - right click and try to substitute the misspelled word. > > Under plasma wayland libreoffice carshes 100% times. > Under gnome just work fine Sorry just forgot to add (copy-paste from gnome session) Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 8; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: es-ES (es_ES.UTF-8); UI: es-ES 7.6.4-1 Calc: threaded Languagetool 6.3.1
(In reply to giors_00 from comment #35) > Just tried this > > - Enable languagetool extension. > - Open a .doc document. > - insert a comment with an orthographical failure. > - right click and try to substitute the misspelled word. > > Under plasma wayland libreoffice carshes 100% times. > Under gnome just work fine Could you please attach a sample screencast doing this where it crashes?