https://bugs.kde.org/show_bug.cgi?id=522236
--- Comment #2 from [email protected] --- Hello, I was busy yesterday I'm sorry Two questions: 1. Is this a regression from Plasma 6.6? A- Afaik yes! 2. Does the same issue happen in a new clean user account with no changes made except for turning on IBus or Plasma Keyboard? A- I just tried and yes! On Fri, Jun 26, 2026, 3:19 PM Nate Graham <[email protected]> wrote: > https://bugs.kde.org/show_bug.cgi?id=522236 > > Nate Graham <[email protected]> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Component|general |input > Version First|unspecified |6.7.0 > Reported In| | > Product|Plasma Keyboard |kwin > Status|REPORTED |NEEDSINFO > CC| |[email protected], > | |[email protected] > Resolution|--- |WAITINGFORINFO > Assignee|[email protected] |[email protected] > > --- Comment #1 from Nate Graham <[email protected]> --- > I cannot reproduce the issue in KDE Linux with either Plasma Keyboard or > Fcitx > (another input method) selected. > > If it happens with both, it's not a Plasma Keyboard issue; it could > *maybe* be > a Wayland text input issue but given that I can't reproduce it, it may be > caused by a misconfiguration of some type. > > Two questions: > 1. Is this a regression from Plasma 6.6? > 2. Does the same issue happen in a new clean user account with no changes > made > except for turning on IBus or Plasma Keyboard? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
