Description: In latest openSUSE Tumbleweed(2023/04/24 or maybe some earlier snapshots), I use plasma desktop on X11. I installed libreoffice 7.5.22 with qt5 frontend(vcl kf5), and fcitx5 with qt5 frontend support. But When I type chinese characters in libreoffice programs, the candidate list(a popup expected to move as the cursor moves and stay very close to the cursor) does not show in the right position. It follows the cursor, but not close enought to the cursor. In other softwares like firefox (with gtk3 interface) and other softwares with qt5 interface(like konsole, kate), the popup is shown in the right position. I also tried remove libreoffice-qt5 and install libreoffice-gtk3, then the popup position is also right. Steps to Reproduce: 1. Install libreoffice on a recent release of rolling distribution of linux( openSUSE Tumbleweed or arch linux for example); 2. Install libreoffice qt5 interface; 3. Install fcitx5 with qt5 support and install some chinese input method(so as to show the popup while typing); 4. Use plasmashell on X11(maybe this is not necessary to be plasma or X11); 5. open a new libreoffice writer(other components can also reproduce) and type in chinese. Actual Results: popup show in a position that follow the cursor and but not right below the cursor, but roughly a line under the cursor.u Expected Results: popup show in a position that follow the cursor and right below the cursor. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: zh-CN (zh_CN.UTF-8); UI: zh-CN Calc: threaded
Created attachment 186996 [details] libreoffice-qt5 wrong popup position
Created attachment 186997 [details] libreoffice-gtk3 popup right position
Created attachment 186998 [details] firefox popup right position
Created attachment 186999 [details] kate popup right position
Created attachment 187000 [details] konsole popup right position
Thanks for the report, iclementine! Please don't set your own reports to "new" as others have to confirm they also see the issue. Did this issue start with LibreOffice 7.5, or was it present before? Could you please test running LibreOffice with the qt5 VCL, with the following commande: SAL_USE_VCLPLUGIN=qt5 libreoffice Does the issue remain?
Is this still an issue with kf6? What about a Wayland session?
Dear iclementine, 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 iclementine, 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