Created attachment 151736 [details] Screenshot Tool 4.5.1 Java SE 8u2121
Could you please paste the info from Help - about LibreOffice ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the information has been provided
Sorry i have no onfo from Help. I started LO by using quickstart. Than a new page is started. The text to see in the screenshot arrieves and disapiere behind the new page. I can write as usually
(In reply to Dr. Haug from comment #2) > Sorry i have no onfo from Help. > I started LO by using quickstart. Than a new page is started. The text to > see in the screenshot arrieves and disapiere behind the new page. I can > write as usually Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
*** This bug has been marked as a duplicate of bug 75051 ***
I am working with Version: 6.2.4.2 (x64)
Could you provide the same screenshot with error popup window moved at right so we can see all the details of the last stacktrace?
On pc Debian x86-64 with master sources updated today, I downloaded Languagetool 4.5.1 from https://languagetool.org/fr/#libreoffice and installed it. I also changed locale to German/Switzerland and language to German. Then I restarted and tried the different entries of Languagetool, no error message.
(In reply to Julien Nabet from comment #6) > Could you provide the same screenshot with error popup window moved at right > so we can see all the details of the last stacktrace? Setting to NEEDINFO until the screenshot is provided...
Thanks for informations. The problem seems disappeared because: Version: 6.2.5.2 (x64) Build-ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 CPU-Threads: 6; BS: Windows 10.0; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: CL Sincerly Haug
Thanks for retesting with the latest version. Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.
Created attachment 152644 [details] Again
Sorry see attatment. The problem is back.