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

electron-12.x.y branch, IME don't work when on Wayland #120084

Closed
karuboniru opened this issue Mar 29, 2021 · 11 comments
Closed

electron-12.x.y branch, IME don't work when on Wayland #120084

karuboniru opened this issue Mar 29, 2021 · 11 comments
Assignees
Labels
chromium Issues and items related to Chromium info-needed Issue requires more information from poster upstream Issue identified as 'upstream' component related (exists outside of VS Code) wayland Issue related to wayland display server

Comments

@karuboniru
Copy link

  • VS Code Version: commit hash: 6a7aba1
  • OS Version: Fedora 34 (Workstation Edition Prerelease)

Steps to Reproduce:

  1. Compile code-oss from source, package as rpm, install it.
  2. code-oss --enable-features=UseOzonePlatform --ozone-platform=wayland
  3. Input method don't work, here specifically fcitx5

Does this issue occur when all extensions are disabled?: Yes


additional information:
Seems that IM module (like /usr/lib64/gtk-3.0/3.0.0/immodules/im-fcitx5.so or /usr/lib64/gtk-3.0/3.0.0/immodules/im-ibus.so) isn't loaded at all, when using Wayland.

@karuboniru
Copy link
Author

Still present in #120034 (comment)
Maybe waiting a newer electron 12.x release?

@12101111
Copy link

It may get support in electron 14 ( chromium 93 ) or later. electron 12 ( chromium 89 ) or electron 13 ( chromium 91 ) don't support it.

@stalkerg
Copy link

ibus not working at all under wayland because not support the latest version of the protocol.

@ghost
Copy link

ghost commented May 6, 2021

ibus not working at all under wayland because not support the latest version of the protocol.

Does Electron or Chromium currently supports text_input_unstable_v3 or text_input_unstable_v1 protocol?

@12101111
Copy link

12101111 commented May 7, 2021

Does Electron or Chromium currently supports text_input_unstable_v3 or text_input_unstable_v1 protocol?

It support text_input_unstable_v1: https://github.com/chromium/chromium/blob/master/ui/ozone/platform/wayland/host/zwp_text_input_wrapper_v1.h

@stalkerg
Copy link

stalkerg commented May 8, 2021

Basically, current Wayland protocols not enough for normal IME but developers working on it - https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/39

@deepak1556 deepak1556 added electron-12-update Issues and items related to electron 12 update wayland Issue related to wayland display server chromium Issues and items related to Chromium upstream Issue identified as 'upstream' component related (exists outside of VS Code) confirmation-pending labels May 9, 2021
@microcai
Copy link

using gtk-4 will solve it. but how to use gtk-4 ? chrome has command flag for it.

@deepak1556
Copy link
Collaborator

gtk-4 is not supported in electron yet, so the command line flag cannot be used.

Is this issue present with latest insiders https://code.visualstudio.com/insiders which comes with newer runtime version ?

@deepak1556 deepak1556 added info-needed Issue requires more information from poster and removed electron-12-update Issues and items related to electron 12 update labels Apr 11, 2022
@karuboniru
Copy link
Author

This problem still exist with code-1.67.1-1651841920 and code-insiders-1.68.0-1652420254 version. Chromium's input method support can be enabled by --gtk-version=4, while this is not possible since follow error will be generated when running code --enable-features=UseOzonePlatform --ozone-platform=wayland --gtk-version=4 --verbose

Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'ozone-platform' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'gtk-version' is not in the list of known options, but still passed to Electron/Chromium.
[15673:0514/001526.813128:WARNING:wayland_object.cc(94)] Binding to gtk_shell1 version 4 but version 5 is available.
[15673:0514/001526.813180:WARNING:wayland_object.cc(94)] Binding to zwp_pointer_gestures_v1 version 1 but version 3 is available.
[15673:0514/001526.813208:WARNING:wayland_object.cc(94)] Binding to zwp_linux_dmabuf_v1 version 3 but version 4 is available.
[15673:0514/001526.813499:WARNING:wayland_drm.cc(96)] Failed to get drm magic
(process:15673): Gtk-ERROR **: 00:15:26.816: GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported
[0514/001526.837255:ERROR:directory_reader_posix.cc(42)] opendir /home/yan/.config/Code/Crashpad/attachments/797ac066-0ea9-4880-b687-1ea6d3156a9a: No such file or directory (2)

@github-actions github-actions bot locked and limited conversation to collaborators Jun 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
chromium Issues and items related to Chromium info-needed Issue requires more information from poster upstream Issue identified as 'upstream' component related (exists outside of VS Code) wayland Issue related to wayland display server
Projects
None yet
Development

No branches or pull requests

7 participants
@microcai @deepak1556 @stalkerg @karuboniru @12101111 @tinywrkb and others