cannot switch to japanese input method

[smeetide]

When inputting to an annotation note, it does not switch to Japanese input using a Japanese keyboard. Please respond.

[johnfactotum]

Works fine for me. Which desktop environment and input method are you using?

[smeetide]

Thank you, your kindness. I use: echo $XDG_CURRENT_DESKTOP X-Cinnamon ls /usr/bin/*-session /usr/bin/cinnamon-session /usr/bin/dbus-run-session Japanese input method: fcitx-mozc System Locale: LANG=ja_JP.UTF-8 LANGUAGE=ja_JP:ja VC Keymap: n/a X11 Layout: jp X11 Model: pc105

…

On Sat, Mar 23, 2024 at 1:20 PM John Factotum ***@***.***> wrote: Works fine for me. Which desktop environment and input method are you using? — Reply to this email directly, view it on GitHub <#1277 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYNJFHCZQ3OEPNR7BDV2RZ3YZT7KRAVCNFSM6AAAAABFEFM7MSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJWGM2DCMRTGM> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

-- --- Sidekick Browserで送信

[smeetide]

p.s. trigger keys: Henkan and Muhenkan

…

On Sat, Mar 23, 2024 at 5:12 PM smeet ide ***@***.***> wrote: Thank you, your kindness. I use: echo $XDG_CURRENT_DESKTOP X-Cinnamon ls /usr/bin/*-session /usr/bin/cinnamon-session /usr/bin/dbus-run-session Japanese input method: fcitx-mozc System Locale: LANG=ja_JP.UTF-8 LANGUAGE=ja_JP:ja VC Keymap: n/a X11 Layout: jp X11 Model: pc105 On Sat, Mar 23, 2024 at 1:20 PM John Factotum ***@***.***> wrote: > Works fine for me. Which desktop environment and input method are you > using? > > — > Reply to this email directly, view it on GitHub > <#1277 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AYNJFHCZQ3OEPNR7BDV2RZ3YZT7KRAVCNFSM6AAAAABFEFM7MSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJWGM2DCMRTGM> > . > You are receiving this because you modified the open/close state.Message > ID: ***@***.***> > -- --- Sidekick Browserで送信

-- --- Sidekick Browserで送信

[johnfactotum]

Presumably this would be a problem with how fcitx is configured. Does this only happen with popovers? And does it work in other GTK 4 apps?

[smeetide]

thank you. this only happen with popover in foliate annotation. in other GTK4 apps goes on well.

…

On Mon, Mar 25, 2024 at 1:42 PM John Factotum ***@***.***> wrote: Presumably this would be a problem with how fcitx is configured. Does this only happen with popovers? And does it work in other GTK 4 apps? — Reply to this email directly, view it on GitHub <#1277 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYNJFHF7MWMPXTXYLYHAYV3YZ6TLVAVCNFSM6AAAAABFEFM7MSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJXGE4TSMBRHE> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

-- --- Sidekick Browserで送信

[johnfactotum]

Well, I must admit that I don't really know how input methods work in GTK, but I can think of two possibilities.

One is that Foliate might have set something, e.g. a shortcut, that interferes with input. This seems unlikely, though, unless the problem happens also for the search entry on the sidebar.

The second possibility is that there could be a problem with Fcitx for GtkPopover, GtkTextView, or the specific combination of GtkPopover + GtkTextView.