| Summary: | text-input-v1 not working with fcitx5 on chromium | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Yiyang Wu <xgreenlandforwyy> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | nicolas.fella, qydwhotmail, wengxt |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.2 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
logs running chromium with `WAYLAND_DEBUG=1`
(weston) logs running chromium with `WAYLAND_DEBUG=1` |
||
|
Description
Yiyang Wu
2023-03-04 06:25:54 UTC
Created attachment 156986 [details]
(weston) logs running chromium with `WAYLAND_DEBUG=1`
Have you selected fcitx5 in virtual keyboard KCM? Also `export $(dbus-launch); startplasma-wayland` on tty is not a supported way to use fcitx5 on Wayland because an Arch user also reported the same bug. (In reply to Fushan Wen from comment #2) > Have you selected fcitx5 in virtual keyboard KCM? No. And after I enabled it this issue is resolved. Thanks! > Also `export $(dbus-launch); startplasma-wayland` on tty is not a supported way to use > fcitx5 on Wayland because an Arch user also reported the same bug. For me it seems not having any impact using `export $(dbus-launch); startplasma-wayland` |