Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keymap change for DirectInput mode and IMEOn command requires fcitx5 restart #62

Open
jubame opened this issue Jul 16, 2024 · 0 comments

Comments

@jubame
Copy link

jubame commented Jul 16, 2024

Description

Keymap change for DirectInput mode and IMEOn command requires a fcitx5 restart. However, non DirectInput modes keymap changes do not require a restart.

Steps to reproduce

Steps to reproduce the behavior:

  1. Go to Mozc -> Configure -> Configuration Tool -> Configure -> Keymap section -> Keymap style MS-IME -> Customize...
  2. Go to this default row: DirectInput mode - Hankaku/Zenkaku key - IMEOn command
  3. Change key from default Hankaku/Zenkaku to something else.
  4. This message is shown: "Changes of keymaps for direct input mode will apply only to applications that are launched after making your modifications." -> Click OK

Expected behavior

Either of these:

  • No restart required
  • Automatic restart
  • Manual restart: in this case, ask the user to restart fcitx5 manually in the dialog box at point 4 above, instead of restarting the application.

Actual behavior

Pressing the keymap does nothing, staying in DirectInput mode, even after restarting my editor. Have to restart fcitx5 manually for it to take effect.

Version or commit-id

Mozc-2.30.5490.102+24.11.oss

Environment

  • OS: Arch Linux, Wayland (Sway)
  • IMF: fcitx5
  • Related Applications: I have tried Firefox and Mousepad

Installed packages

% sudo pacman -Qs fcitx                                                                                   [0]
[sudo] password for j: 
local/fcitx5 5.1.10-1 (fcitx5-im)
    Next generation of fcitx
local/fcitx5-configtool 5.1.6-1 (fcitx5-im)
    Configuration Tool for Fcitx5
local/fcitx5-gtk 5.1.3-1 (fcitx5-im)
    Fcitx5 gtk im module and glib based dbus client library
local/fcitx5-mozc-ut 2.30.5490.102-2
    Mozc module for Fcitx5
local/fcitx5-mozc-ut-debug 2.30.5490.102-2
    Detached debugging symbols for fcitx5-mozc-ut
local/fcitx5-qt 5.1.6-3 (fcitx5-im)
    Fcitx5 Qt Library (Qt5 & Qt6 integrations)
% sudo pacman -Qs mozc                                                                                    [0]
local/fcitx5-mozc-ut 2.30.5490.102-2
    Mozc module for Fcitx5
local/fcitx5-mozc-ut-debug 2.30.5490.102-2
    Detached debugging symbols for fcitx5-mozc-ut
local/mozc 2.30.5490.102-1
    The Open Source edition of Google Japanese Input
local/mozc-debug 2.30.5490.102-1
    Detached debugging symbols for mozc

Investigations

  • Whether this issue happens on both Ibus and other IMF (e.g. Fcitx, uim).
    • N/A, only tried fcitx5
  • Whether this issue happens on other IMEs (e.g. Anthy, SKK).
    • N/A, only applies to Mozc
  • What applications this issue happens on (e.g. Chromium, gedit).
    • I have tried Firefox and Mousepad
  • What applications this issue does not happen on (e.g. Chromium, gedit).
    • not-found
  • (optional) What versions or commit-ids this issue did not happen on
    no-investigation, this is the latest package for my distro.

Additional context

It seems I am not the first one to encounter this issue. See:
google#395 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant