Description: I'm using Libreoffice Writer on Arch Linux, on KDE plasma 5.23.1. I have an Intel i7-6500U processor and a nvidia Geforce 920MX dedicated graphics card. I noticed a strange behaviour in the program. At first, when I select a paragraph style, a font or a font size from the toolbar, I can type normally in Libreoffice Writer. But if I change a second time the paragraph style, the font or the font size, the menu bar changes color and I cannot type anymore. This strange behaviour seems to stop when I right click or minimize the windows to remaximize it afterwards. I've tried using Libreoffice on GNOME 40.5 and everything seems to behave normally there, so I think that the problem regards the KDE Plasma desktop environment. I tried reinstalling Arch Linux many times in a VM and on physical hardware and the problem continues to appear. I've tried running Libreoffice Writer in safe mode, but it still shows this problem. Steps to Reproduce: 1.Change the paragraph style, the font or the font size from the toolbar a first time; 2.Try to change it a second time using the toolbar; 3.Libreoffice starts behaving strangely. Actual Results: The menu bar changes color and I can't type anymore. Only if I right click or I minimize the window, the problem seems to disappear. Expected Results: Libreoffice Writer should let me type even if I change the paragraph style, the font or the font size from the toolbar. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.2.2.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+xcb) Locale: it-IT (it_IT.UTF-8); UI: it-IT 7.2.2-1 Calc: threaded
I tried using Libreoffice Still, version 7.1.7.2, and it works flawlessly, without any bug that I mentioned. For this reason, I think the bug appears after version 7.2.2.2, the version in which I noticed the bug when I did this bug report. Even after all the updates of KDE plasma, the bug still persists, even in the newer versions of LibreOffice Fresh, so in the 7.2.3.x versions. I hope I'm not the only one experiencing this bug and that it can still be reproduced.
Created attachment 176702 [details] This is a video showing how to reproduce the bug. I will send now a video showing how to reproduce this bug.
I can reproduce with Version: 7.2.4.1 / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded but not with a daily build of the current development version: Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 2934472ab888ebfe64a153984af2902fac63a7a0 CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded This *might* be related to recent changes in the popup handling for the qt5 VCL plugin.
Interesting... So Libreoffice won't behave strangely starting from version 7.4.x?
I bibisected this. The problem starts appearing at commit commit cf5cc42785eae15dc19f06f391d614832b16be20 Author: Jan-Marek Glogowski <glogow@fbihome.de> Date: Thu Apr 15 00:37:55 2021 +0200 Qt5 correctly focus the navigator window and it works OK again after commit 63f92f185b78db5a575da58efac3f94a8cb5a5f6 Author: Jan-Marek Glogowski <glogow@fbihome.de> Date: Mon Jul 19 22:13:21 2021 +0200 Qt5 fix Qt::Popup window handling On the libreoffice-7-2 branch, that has been reverted with commit a928bab9fb68ff8fe45aca212b3c794799db31f6 Author: Jan-Marek Glogowski <glogow@fbihome.de> Date: Mon Sep 20 13:56:00 2021 +0200 tdf#144585 Qt5 restore old VCL popup handling because there are otherwise issues on Wayland, s. tdf#144585. (In reply to Gabriele Avi from comment #4) > Interesting... So Libreoffice won't behave strangely starting from version > 7.4.x? As is, this specific issue should not be present with upcoming LO versions 7.3 and 7.4. (Note however that a "proper" fix for tdf#144585 is still needed for those versions.)
I will wait for version 7.3.x then. Let's hope that tdf#144585 will be fixed soon. I thank you for your kind and quick response. What should we do about this issue? We can mark it as closed?
(In reply to Gabriele Avi from comment #6) > What should we do about this > issue? We can mark it as closed? Let's do so, since it's fixed in newer versions by the commit mentioned in comment 5.