First letter flies to front of line in pinyin

[jidanni]

If I try to type 正常 here in a Github issue, I end up with n至常.
欲打如本行，必先於 bash shell command line 打，再複製到 GitHub.
Else when I try to type 欲 the first letter flies out in front.
By the way, to type fuzhi, well, even in the bash shell, I need fuzhzhzhiii4
before finally seeing the precious two letters, "複製"!

[kanru]

What is the browser? I can't reproduce this with Firefox 127.0.2

正常

firefox 127.0.2
ibus-chewing 2.0.0
libchewing 0.8.4

[jidanni]

Linux Desktop https://www.google.com/chrome/beta/

• https://stackoverflow.com/questions/75194926/cursor-jumps-in-the-beginning-of-the-input-line-after-each-letter-in-1-milliseco
• https://www.reddit.com/r/chrome/comments/yqpksk/cursor_jumps_to_beginning_of_line_in_text_boxes/

[kanru]

Testing from Chrome installed from flatpak

正常正常正常正常正常

It seems it's not reproducible from my laptop. Perhaps it's fixed in newer ibus (1.5.30)?

ibus 1.5.30-rc1 has has this line in the release note:

• Fix preedit issue with X applications ibus/ibus@719792d

[jidanni]

OK I'll wait until that reaches Debian sid.

[kanru]

OK I'll wait until that reaches Debian sid.

ibus 1.5.30 is in Debian sid. Does it improve anything?

[jidanni]

• nzheg ... still garbled.

Sorry. Not fixed. After reboot using

Package: ibus-chewing
Version: 2.0.0-1+b1
ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4+b2
ii ibus 1.5.30-1
ii libadwaita-1-0 1.5.2-1
ii libc6 2.38-14
ii libchewing3 0.8.4-2
ii libglib2.0-0t64 2.80.3-1
ii libgtk-4-1 4.12.5+ds-6+b1
ii libibus-1.0-5 1.5.30-1

Note: this is when intending to type "zheng..." into a GitHub comment in chrome beta on desktop.

注意 the problem only happens in Chrome when typing into a GitHub comment, not in emacs or shell.

[kanru]

Please share the whole config by running this in shell:

gsettings list-recursively org.freedesktop.IBus.Chewing

Also your beta chrome version. What desktop environment are you using?

[jidanni]

Today still on my slower computer: "n證chag". But on my faster computer I didn't see the problem. So maybe it's a CPU speed issue.

$ gsettings list-recursively org.freedesktop.IBus.Chewing
org.freedesktop.IBus.Chewing add-phrase-direction true
org.freedesktop.IBus.Chewing auto-shift-cur true
org.freedesktop.IBus.Chewing cand-per-page uint32 10
org.freedesktop.IBus.Chewing chi-eng-mode-toggle 'caps_lock'
org.freedesktop.IBus.Chewing clean-buffer-focus-out false
org.freedesktop.IBus.Chewing default-english-case 'lowercase'
org.freedesktop.IBus.Chewing easy-symbol-input true
org.freedesktop.IBus.Chewing esc-clean-all-buf false
org.freedesktop.IBus.Chewing kb-type 'hanyu'
org.freedesktop.IBus.Chewing max-chi-symbol-len 20
org.freedesktop.IBus.Chewing phrase-choice-from-last true
org.freedesktop.IBus.Chewing plain-zhuyin false
org.freedesktop.IBus.Chewing sel-keys '1234567890'
org.freedesktop.IBus.Chewing show-page-number false
org.freedesktop.IBus.Chewing show-systray true
org.freedesktop.IBus.Chewing space-as-selection false
org.freedesktop.IBus.Chewing sync-caps-lock 'disable'
org.freedesktop.IBus.Chewing vertical-lookup-table false

Package: google-chrome-beta
Version: 127.0.6533.26-1

$ pstree
systemd-+-acpi_fakekeyd
        |-acpid
        |-agetty
        |-at-spi-bus-laun-+-dbus-daemon
        |                 `-4*[{at-spi-bus-laun}]
        |-at-spi2-registr---3*[{at-spi2-registr}]
        |-atd
        |-chrome_crashpad---2*[{chrome_crashpad}]
        |-chrome_crashpad---{chrome_crashpad}
        |-copy_mail---sleep
        |-cron
        |-2*[dbus-daemon]
        |-dbus-launch
        |-dconf-service---3*[{dconf-service}]
        |-dictd
        |-emacs---5*[{emacs}]
        |-exim4
        |-ibus-daemon-+-ibus-engine-che---7*[{ibus-engine-che}]
        |             |-ibus-engine-sim---3*[{ibus-engine-sim}]
        |             |-ibus-extension----5*[{ibus-extension-}]
        |             |-ibus-memconf---3*[{ibus-memconf}]
        |             |-ibus-ui-gtk3---6*[{ibus-ui-gtk3}]
        |             `-3*[{ibus-daemon}]
        |-ibus-portal---3*[{ibus-portal}]
        |-ibus-x11---4*[{ibus-x11}]
        |-lightdm-+-Xorg---4*[{Xorg}]
        |         |-lightdm-+-bash-+-i3-+-i3bar-+-sh---i3status
        |         |         |      |    |       `-{i3bar}
        |         |         |      |    |-sh---alttab
        |         |         |      |    `-{i3}
        |         |         |      `-ssh-agent
        |         |         `-3*[{lightdm}]
        |         `-3*[{lightdm}]
        |-pppd
        |-rsyslogd---3*[{rsyslogd}]
        |-systemd---(sd-pam)
        |-systemd-journal
        |-systemd-logind
        |-systemd-timesyn---{systemd-timesyn}
        |-systemd-udevd
        |-xclip
        |-xterm---bash-+-mybrowser---chrome-+-2*[cat]
        |              |                    |-chrome---chrome---12*[{chrome}]
        |              |                    |-chrome---chrome-+-chrome---6*[{chrome}]
        |              |                    |                 |-2*[chrome---12*[{chrome}]]
        |              |                    |                 |-5*[chrome---10*[{chrome}]]
        |              |                    |                 `-chrome---9*[{chrome}]
        |              |                    |-chrome---8*[{chrome}]
        |              |                    `-35*[{chrome}]
        |              |-pstree
        |              `-xclip
        `-xterm---su---bash

[kanru]

Typing as fast as I can in Chrome that is running in GNOME Xorg on QEMU, and intentionally throttled the CPU. It is still not very slow but there is visible lag.

I still can't reproduce this issue so it might be tricky to fix it.