Description: Writer crashes when I try to set all text to English. I have a file (originally DOCX, saved as ODT) with 4-5 pages of text (Spanish mixed with English). I want to set the language of the entire document to English. I can set 'selected text' and 'paragraph' to English, but when I try with "all text", Writer hangs (and I have to kill it). I tried debugging with GDB: weirdly, I can open the file and work otherwise 'normally', but when I try to open it using backtrace ('lowriter --backtrace') Writer never really opens (although I see the border of a window with the title of the file during a second before it crashes and disappears again). This may mean I will need also guidance with debugging. I attach the gdbtrace.log file. Steps to Reproduce: This happens when I try to set Enlish as language for All text via Tools > Language > For all text > English. - it happens only for this file (it works well with a brand-new ODT) - it happens only for "all text" option. The "selected text" and "paragraph" works fine. Actual Results: Also, when I try to debug (lowriter --backtrace) I can not reproduce the problem because in this case Writer does not even start! BUT, there is no problem if I start Writer in the 'normal' ways (eg lowriter from console or Writer in my applications menu) Expected Results: Maybe I am doing something wrong with the debugging as well? What else can I do to diagnose this? Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 4:7.5.4~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded
Created attachment 188480 [details] debugging info This is the log file, generated by gdb
Thank you J22Gim. This is most likely bug 155939, which is fixed in 7.5.5. Please feel free to confirm that it does work in that new version (at the bottom of the page): https://www.libreoffice.org/download/download-libreoffice/ *** This bug has been marked as a duplicate of bug 155939 ***
Yes it works now!!! Thanks so much everyone for all your work!