Description of problem: The search box at Activities can shows first character only on the preedit and committed strings but not updating preedit during typing. Version-Release number of selected component (if applicable): gnome-shell-42~rc-1.fc36.x86_64 How reproducible: always Steps to Reproduce: 1.Add Japanese(Anthy) Input source 2.Activate it through Super+space 3.type edhita at the search box for example Actual results: only "え" is renderred Expected results: "えでぃた" should be renderred Additional info: Once typing enter, "えでぃた" appears at the search box. so they are capable to input something through ibus. but the rendering isn't correct.
Yeah, I can confirm this - openQA has been hitting it for weeks, I just hadn't got around to reporting it yet. In the openQA test we hit the keys y, a, m, a - which should enter やま and then let us complete it to 山 - but we only see 'y' appear in the search box: https://openqa.fedoraproject.org/tests/1176159#step/_graphical_input/11
Sadly I can't tell from openQA exactly when this started, because some other bugs that happened *earlier* showed up and confused the record. But the last time the test passed was on Fedora-Rawhide-20220214.n.0 , and I managed to get the other bugs fixed and reach this bug for the first time with Fedora-Rawhide-20220305.n.0 , so it broke somewhere in that gap.
Oddly, I just tested this on my own laptop (where I have US English keyboard layout and Anthy input method configured) and can't reproduce it. But openQA hits it every time. Not sure what the difference is.
+4 Beta FE in https://pagure.io/fedora-qa/blocker-review/issue/676 , marking accepted.
(In reply to Adam Williamson from comment #3) > Oddly, I just tested this on my own laptop (where I have US English keyboard > layout and Anthy input method configured) and can't reproduce it. But openQA > hits it every time. Not sure what the difference is. It seems not 100% reproducible - though I think I can hit it about 90% of the time or more in my VM.
+3 in https://pagure.io/fedora-qa/blocker-review/issue/676 , marking accepted Final blocker.
Moving to mutter to align with the current upstream issue: https://gitlab.gnome.org/GNOME/mutter/-/issues/2188
FEDORA-2022-566779da43 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-566779da43
I confirmed the fix here myself.
FEDORA-2022-566779da43 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-566779da43` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-566779da43 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Yes, works for me too. thanks for the update.
FEDORA-2022-566779da43 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.