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

Fcitx 5 does not function normally #11752

Closed
1 of 2 tasks
xuangeyouneihan opened this issue Jul 5, 2024 · 7 comments
Closed
1 of 2 tasks

Fcitx 5 does not function normally #11752

xuangeyouneihan opened this issue Jul 5, 2024 · 7 comments

Comments

@xuangeyouneihan
Copy link

xuangeyouneihan commented Jul 5, 2024

Windows Version

10.0.22631.3810

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

6.6.36.3 (Self-compiled from microsoft/WSL2-Linux-Kernel, and version 5.15.153.1 also has the same problem)

Distro Version

Arch and Ubuntu 22.04

Other Software

No response

Repro Steps

Just update all the packages to the latest versions using the package manager, and make sure fcitx5 and fcitx5-configtool (or fcitx-config-qt) are installed, then run fcitx5 --disable=wayland and fcitx5-configtool

Expected Behavior

Fcitx 5 functions normally, at least it should be configured by fcitx5-configtool

Actual Behavior

"Cannot connect to Fcitx by DBus, is Fcitx running?" In addition, Fcitx 5 cannot be used in other apps like Firefox either
image

Diagnostic Logs

Fcitx log, got in Arch with v5.15.153.1 kernel: debug_log.txt

Copy link

github-actions bot commented Jul 5, 2024

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

@xuangeyouneihan
Copy link
Author

@xuangeyouneihan
Copy link
Author

Related to yuk7/ArchWSL#370

Copy link

github-actions bot commented Jul 5, 2024

Diagnostic information
Detected appx version: 2.2.4.0

@OneBlue
Copy link
Collaborator

OneBlue commented Jul 9, 2024

I don't have deep knowledge of what fcitx5 is, but based on the error message it looks like it might need systemd support, which you can enable via:

#/etc/wsl.conf

[boot]
systemd=true

If that doesn't solve the issue, this probably needs to be investigated on the fcitx5 side, to see what the exact problem is.

@OneBlue OneBlue closed this as completed Jul 9, 2024
@xuangeyouneihan
Copy link
Author

I've already enabled Systemd. systemctl status shows that Systemd is running. I'll submit an issue on the Fcitx 5 side

@xuangeyouneihan
Copy link
Author

Solved, but every user needs to be configured separately: #10205 (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

2 participants