Summary: | Impossible to type accented characters in search field unless I type and delete something before | ||
---|---|---|---|
Product: | [Unmaintained] kdeplasma-addons | Reporter: | Patrick Silva <bugseforuns> |
Component: | Application Dashboard | Assignee: | Eike Hein <hein> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | germanoalves, jesaenh, plasma-bugs-null |
Priority: | NOR | ||
Version First Reported In: | 6.1.3 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Patrick Silva
2018-04-23 19:40:45 UTC
Plasma 5.13 on Arch Linux has the same bug. Problem persists in plasma 5.14 only under X11. Cannot reproduce under Wayland. Operating System: Arch Linux KDE Plasma Version: 5.14.0 Qt Version: 5.11.2 KDE Frameworks Version: 5.51.0 *** Bug 406346 has been marked as a duplicate of this bug. *** I have this same problem on Arch Linux with Plasma in the most current version (5.21.1). In fact, this is a very old problem especially in the Wayland session. In the X-Org session, accents in Brazilian Portuguese work normally. Wayland is very complicated. The accents just don't work and even trying to use the automatic corrections from LibreOffice or Calligra, it still doesn't work. I count on the goodwill of the devs of this "Komunity" that I like a lot and I identify myself too much. But I confess that this is a problem that is affecting a lot the use of Brazilians with Plasma. The problem with accents on Wayland session is another bug, see bug 411729 (In reply to Patrick Silva from comment #5) > The problem with accents on Wayland session is another bug, see bug 411729 OK, tks! I just saw this report. It suits my problem more, really. Currently I can't type accented characters on Wayland too. Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Graphics Platform: Wayland Cannot type an accented character on opening. Possibly related to bug 459269. *** This bug has been marked as a duplicate of bug 459269 *** |