https://bugs.kde.org/show_bug.cgi?id=489057
--- Comment #7 from elgoogno...@gmail.com ---
(In reply to elgoognojks from comment #6)
> I found one possible culprit!
>
> Traditionally in order to use fcitx input method (e.g. mcbopomofo for
> Traditional Chinese in Taiwan) in Wayland + KDE Plasma, w
https://bugs.kde.org/show_bug.cgi?id=489057
elgoogno...@gmail.com changed:
What|Removed |Added
Keywords||wayland
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=489057
--- Comment #6 from elgoogno...@gmail.com ---
I found one possible culprit!
Traditionally in order to use fcitx input method (e.g. mcbopomofo for
Traditional Chinese in Taiwan) in Wayland + KDE Plasma, we need to go to Plasma
setting/Keyboard/Virtual ke
https://bugs.kde.org/show_bug.cgi?id=489057
elgoogno...@gmail.com changed:
What|Removed |Added
Version|6.1.0 |6.1.1
--- Comment #5 from elgoogno...@gm
https://bugs.kde.org/show_bug.cgi?id=489057
--- Comment #4 from Nate Graham ---
Ah, the binding loop issue. I think this should be fixed in Plasma 6.1.1; can
you test again with that version?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=489057
--- Comment #3 from elgoogno...@gmail.com ---
Also, I found a difference.
In the original user account where "Enter edit mode" is malfunction, after
trying entering edit mode the journal log in the KSystemLog emerged 2 new
entries:
```
plasmashell
file:
https://bugs.kde.org/show_bug.cgi?id=489057
--- Comment #2 from elgoogno...@gmail.com ---
(In reply to Nate Graham from comment #1)
> Cannot reproduce the issue by following the steps in the video. Does it
> happen in a new clean user account on the same machine? This could rule out
> any local co
https://bugs.kde.org/show_bug.cgi?id=489057
Nate Graham changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
