-
Notifications
You must be signed in to change notification settings - Fork 28.2k
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
unable to input chinese character #96041
Comments
(Experimental duplicate detection) |
This bug is still present on the |
can confirm this on snap |
try to address microsoft#96041
Note that this is a duplicate of #77382. I can test if the patch works. |
@Lin-Buo-Ren Thanks! Please do let me know if it works in today's Insiders, should come out soon. |
@joaomoreno I've installed the insiders snap( |
Test under Ubuntu 22.04 / ibus:
|
same issue
the solution is same as what @scaomath said, use fcitx5 and vscode.deb version instead of snap version |
same here: simplescreenrecorder-2022-12-23_19.27.42.mp4Ubuntu 22.04 LTS |
bug has been fixed in 1.74.2,but the snap version of vscode is still 1.74.1 |
@scaomath , thanks very much |
这是来自QQ邮箱的假期自动回复邮件。你好,我最近正在休假中,无法亲自回复你的邮件。我将在假期结束后,尽快给你回复。
|
No, it haven't been fixed
|
Still haven't been fixed.
|
still haven't been fixed for the snap version
but it works well for the .deb version. |
So, now the solution is to use deb or flatpak version instead of snap version right? |
alternatively if you are on Ubuntu you can use Ubuntu Make to install vscode |
Installing with .deb works well😀 |
Is there some flag that needs to be set to enable fcitx for the snap build? I use fcitx fine with other snaps, but for some reason my fcitx input does not work with VS code. |
@braindevices Was there a reason why this is/was not implemented? fcitx does not work for me, though it works fine in other snaps, presumably because of this. Did you test adding desktop-legacy manually to the snap and repacking it? @rzhao271 Sorry, my comment was intended to be addressed to braindevices, I was wondering if he had tested this on his local build. Quote reply didn't auto-append the tag >_<;; I did notice that there are no plugs that seem to connect by default, so is that part of the design choice for security purposes or some other reason? I have not yet locally tested adding the desktop-legacy plug to verify that it allows for fcitx to work. From the official Snapcraft documentation: https://snapcraft.io/docs/desktop-legacy-interface
|
@brlin-tw Does this mean this issue is a |
The snap version does not work.
|
@leimao It probably should be marked as |
Same problem using the deb version:
|
a quick fix is to use ibus instead of fcitx. |
Issue Type: Bug
open it
and switch to chinese input
VS Code version: Code 1.44.2 (ff91584, 2020-04-16T17:50:03.709Z)
OS version: Linux x64 5.3.0-46-generic snap
System Info
flash_3d: disabled_software
flash_stage3d: disabled_software
flash_stage3d_baseline: disabled_software
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: disabled_off
rasterization: disabled_software
skia_renderer: disabled_off_ok
video_decode: disabled_software
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: unavailable_software
webgl2: unavailable_software
Extensions (21)
(1 theme extensions excluded)
The text was updated successfully, but these errors were encountered: