[kwin] [Bug 466810] text-input-v1 not working with fcitx5 on chromium

2023-03-04 Thread Yiyang Wu
https://bugs.kde.org/show_bug.cgi?id=466810 Yiyang Wu changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO

[kwin] [Bug 466810] text-input-v1 not working with fcitx5 on chromium

2023-03-04 Thread Yiyang Wu
https://bugs.kde.org/show_bug.cgi?id=466810 --- Comment #3 from Yiyang Wu --- (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

[kwin] [Bug 466810] text-input-v1 not working with fcitx5 on chromium

2023-03-04 Thread Fushan Wen
https://bugs.kde.org/show_bug.cgi?id=466810 Fushan Wen changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED

[kwin] [Bug 466810] text-input-v1 not working with fcitx5 on chromium

2023-03-04 Thread Nicolas Fella
https://bugs.kde.org/show_bug.cgi?id=466810 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de, |

[kwin] [Bug 466810] text-input-v1 not working with fcitx5 on chromium

2023-03-03 Thread Yiyang Wu
https://bugs.kde.org/show_bug.cgi?id=466810 --- Comment #1 from Yiyang Wu --- Created attachment 156986 --> https://bugs.kde.org/attachment.cgi?id=156986=edit (weston) logs running chromium with `WAYLAND_DEBUG=1` -- You are receiving this mail because: You are watching all bug changes.