Description of problem: When I keep preediting on apps and the screen is locked by idle, IBus stop working after unlocking. Version-Release number of selected component (if applicable): ibus-1.5.25-13.fc36.x86_64 How reproducible: always Steps to Reproduce: 1.Install Workstation from Live 2.Setup with ja 3.Open LibreOffice Writer 4.Type something on preedit and wait for locking the screen 5.Unlock the screen Actual results: Unable to input through IBus on apps Expected results: Able to input through IBus Additional info: IBus get back after changing the focus for example.
I cannot reproduce this issue while I set the idling time is 1 minute.
I can reproduce this now, thank you for the report.
I seem able to reproduce this, even without any pre-edit (nor even the IME turned on), using gnome-terminal for example. As reported, switching application focus brings back the Input Source indicator and input. I used Fedora-Workstation-Live-x86_64-36_Beta-1.1.iso to test.
The IMEs also disappear from the Input Source menu.
Discussed during the 2022-04-11 blocker review meeting: [1] The decision to classify this bug as an AcceptedFreezeException was made: "It is a noticeable issue that cannot be fixed with an update." [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2022-04-11/f36-blocker-review.2022-04-11-16.00.log.txt
It looks to me that somehow the disabling of IM state on the lockscreen password is persisting back into the user session or something?
I opened https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5346
I can still reproduce this issue on f37.
This should be fixed now for gtk4 (as of 4.8.1 at least): ie in current F37 GA. However gtk3 is pending on a new release I believe: should get fixed in 3.24.35.
After updating SB37, that looks good to me: $ rpm-ostree db diff ostree diff commit from: rollback deployment (ed12035ef6daf01958c96ee407d61ec0d875bd7bbf813cf3b8d8e7e1462 584ee) ostree diff commit to: booted deployment (9d1cee1285c831b165403b83b21b944df3c74c7a759dfdd0b3145dda82ffe 310) ...<snip>...
*** Bug 2124007 has been marked as a duplicate of this bug. ***