Bug 120349 - Text fields return wrong text to input method
Summary: Text fields return wrong text to input method
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Wayland GTK3
  Show dependency treegraph
Reported: 2018-10-05 17:03 UTC by Dorota Czaplejewicz
Modified: 2020-01-02 03:27 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Dorota Czaplejewicz 2018-10-05 17:03:23 UTC
The LO text widgets providw wrong values of the text surrounding the cursor  wrong values under the following circumstances:

using Wayland
gnome-shell master (commit 33ffdd60)
mutter master (commit 33ffdd60)
gtk 3-24 (commit 36656ea13a735377e59376276727edf63b0e035b)
libreoffice 6.1 (libreoffice 6.0 will likely crash)

the issue is that the zwp_text_input_v3 protocol mandates text input *not* to include the preedit text contents, while LibreOffice includes it.

This is an issue uncovered in the Gtk bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/585

Is this a problem in the LO implementation of the text field?
Comment 1 Xisco Faulí 2018-12-03 15:50:20 UTC
@Caolán, I thought you might be interested in this issue...
Comment 2 Caolán McNamara 2018-12-04 09:39:40 UTC
how do I test this exactly ? Under F29 enabling "Chinese (Intelligent Pinyin)" input engine under GNOME and typing some random letters I don't seem to trigger our signalIMRetrieveSurrounding method which is the one that calls gtk_im_context_set_surrounding.

Clearly migrating to native gtk3 widgets will have solved this for the specific cases where the native widgets are used, but that's not all of them yet and there'll presumably always be some places where they won't be.
Comment 3 Dorota Czaplejewicz 2018-12-04 10:39:35 UTC
I have tested the issue using wlroots' reference compositor (rootston), together with the virtboard virtual keyboard, which can be found here:


I found the issue by analyzing logs produced with the WL_DEBUG=1 env variable.
Comment 4 Xisco Faulí 2019-06-04 14:07:23 UTC
Hello Dorota,
A new major release of LibreOffice is available since this bug was reported.
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.
Comment 5 QA Administrators 2019-12-02 03:39:27 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2020-01-02 03:27:14 UTC
Dear Dorota Czaplejewicz,

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