Description of problem: After typing in gnome-terminal with ibus input methods, cursor can becomes invisible which is very inconvenient. Version-Release number of selected component (if applicable): Fedora 28 workstation x86_64 ibus-1.5.18-5.fc28.x86_64 ibus-libpinyin-1.10.0-1.fc28.x86_64 (or other Chinese input methods like ibus-rime) How reproducible: 100% Steps to Reproduce: 1. Add Chinese (Intelligent Pinyin) as an input sources in Settings -> Region & Language. 2. Open gnome-terminal 3. Switch to pinyin input (by press "Super" + "Space") 4. Typing, like "ceshi" to get the candidate words, Note: don't press "space" to input a word, just stop at the list candidate words. 5. Press "Super" + "Press" to switch to another input method. 6. Now, in gnome-terminal, the cursor is disappeared. This is one of the reproduce methods, switching to other windows while typing, deleting all inputted letters while typing, may also trigger this. And this is not limited to ibus-libpinyin only, other input methods like ibus-rime can trigger this too. Actual results: Cursor in terminal disappears. Expected results: Cursor won't disappear. Additional info: From the same gnome-terminal tab, switch to Chinese input method, typing and input a Chinese word can get the cursor back.
This also happens with other input sources like Japanese (e.g.: ibus-kkc).
Same issue here. Fedora 28 workstation gnome-terminal-3.28.2-2.fc28.x86_64 ibus-1.5.18-5.fc28.x86_64 ibus-mozc-2.23.2815.102-1.fc28.x86_64 "reset" or "clear" command didn't work.
Could you help to fix this? It's really inconvenient for using ibus input methods.
I thought it's not so critical issue. But now I agree it's not inconvenient especially in the text mode likes vi and investigated this bug yesterday. This is a Wayland specific bug which is caused by mutter.
(In reply to fujiwara from comment #4) > But now I agree it's not inconvenient especially in the text mode likes vi and investigated this bug yesterday. But now I agree it's inconvenient.
Thanks very much for the fix, I rebuilt mutter with the patch and installed it, so far it works well.
Hello, Thanks for the fix, I would appreciate very much if there's a temporary workaround for the issue. (Would be also helpful to give a instruction to build the rpm with the patch)
Gan Huang: I created https://copr.fedorainfracloud.org/coprs/fujiwara/mutter/
Unfortunately I hit the issue :\ [root@fedora tmp]# rpm -ivh ./mutter-3.28.3-3.1.fc28.src.rpm Updating / installing... 1:mutter-3.28.3-3.1.fc28 warning: user tfujiwar does not exist - using root warning: group tfujiwar does not exist - using root warning: user tfujiwar does not exist - using root warning: group tfujiwar does not exist - using root warning: user tfujiwar does not exist - using root warning: group tfujiwar does not exist - using root warning: user tfujiwar does not exist - using root warning: group tfujiwar does not exist - using root ################################# [100%] warning: user tfujiwar does not exist - using root warning: group tfujiwar does not exist - using root warning: user tfujiwar does not exist - using root warning: group tfujiwar does not exist - using root warning: user tfujiwar does not exist - using root warning: group tfujiwar does not exist - using root warning: user tfujiwar does not exist - using root warning: group tfujiwar does not exist - using root Not sure if i missed something, thanks a lot anyway.
(In reply to Gan Huang from comment #9) > [root@fedora tmp]# rpm -ivh ./mutter-3.28.3-3.1.fc28.src.rpm You don't have to install source rpm. # dnf copr enable fujiwara/mutter # dnf update ibus
(In reply to fujiwara from comment #10) > (In reply to Gan Huang from comment #9) > > [root@fedora tmp]# rpm -ivh ./mutter-3.28.3-3.1.fc28.src.rpm > > You don't have to install source rpm. > > # dnf copr enable fujiwara/mutter > # dnf update ibus typo? I believe you were meat to say: # dnf update mutter
Cool, the following commands works for me (Seems a restart needed) :) # dnf copr enable fujiwara/mutter # dnf update mutter Thanks a bunch.
(In reply to vt from comment #11) > typo? I believe you were meat to say: Thanks for fixing my typo :).
Seems this issue was fixed in VTE3 since Fedora 29.
Tested in Fedora 30 , this issue is not reproducible anymore.