Bug 427565

Summary:	Kirigami.SearchField components inside QML KCMs embedded in QWidgets view don't accept dead keys (works fine in sidebar search field)
Product:	[Applications] systemsettings	Reporter:	Thiago Sueto <herzenschein>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	ahiemstra, kde, nate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Thiago Sueto 2020-10-12 01:06:47 UTC

SUMMARY
The new Search field (really appreciated tbh) does not allow accents/dead keys, so áàéóãõ and so on.

STEPS TO REPRODUCE
0. Use a non-English locale that has dead keys (e.g. pt_BR)
1. Open System Settings, then do any of the following:
2a. Use the general search on upper left corner
2b. Go to Workspace Behavior > Desktop Effects
2c. Go to Shortcuts > Shortcuts
2d. Go to Startup and Shutdown > Background Services
3. Attempt to write accented words on the search field

OBSERVED RESULT
Cannot input accents.

EXPECTED RESULT
Should input accents.

Operating System: openSUSE Tumbleweed 20201009
KDE Plasma Version: 5.20.80
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.1
Kernel Version: 5.8.14-1-default

Comment 1 Nate Graham 2020-10-12 19:08:14 UTC

Seems like an issue with the text field component. Moving to qqc2-desktop-style to start with. Could ultimately be a Qt issue with QML-based text fields, maybe.

Comment 2 Arjen Hiemstra 2020-10-12 19:32:34 UTC

Interestingly enough it also doesn't accept my Compose key. Since these are (as far as I know) mostly normal TextFields I expect the issue is in Qt.

Comment 3 Nate Graham 2020-10-12 19:36:38 UTC

Yeah, I can reproduce that.

FWIW the compose key does work for me in the search field in the sidebar, which uses the same Kirigami.SearchField component. I wonder if there's an issue with the QML KCMs being drawn inside a widget or something....

Comment 4 Arjen Hiemstra 2020-10-12 19:58:27 UTC

That could very well be it. I just tested in a pure QML application and there things work.

Comment 5 Nate Graham 2020-10-12 22:29:19 UTC

Found an existing report: Bug 414501.

*** This bug has been marked as a duplicate of bug 414501 ***