https://bugs.kde.org/show_bug.cgi?id=506095
--- Comment #24 from [email protected] --- I see. It may be becoming possible to organize the information more clearly. First, the primary point is that for XWayland windows, KWin + Fcitx5 may fail to input text when using XIM. Next, however, for applications that support other input methods, such as Electron, input works correctly. Moreover, it seems that under certain conditions, such as window switching, input may fail. >From these three points, what can be confirmed is that there is an inconsistency in determining which input method to use to start the input protocol for the target window. In other words, there is a clear inconsistency in the algorithm that actually selects the input method in practice. Considering this, the first thing that comes to mind is that logically, some kind of incorrect use of variables, unnecessary variables, or a coding mistake in the process is occurring. This is because, logically, processing involves manipulating variables or modifying memory states, so it is certain that this issue is related to variables. Furthermore, since the behavior appears to be consistent rather than probabilistic, it indicates that this occurs because some specific processing is clearly happening. In other words, I infer that it should be possible to further identify the exact conditions under which this behavior occurs. As an additional note: even if the process description itself is correct, if the content of the variables is not compatible with the process, the process may produce unexpected behavior. In other words, it will likely be necessary to also consider investigating how the variables are obtained and the consistency of their values. -- You are receiving this mail because: You are watching all bug changes.
