Bug 501221

Summary: KCharSelect search is terribly laggy
Product: [Applications] kcharselect Reporter: uzivatel919
Component: generalAssignee: Christoph Feck <cfeck>
Status: REPORTED ---    
Severity: normal CC: john.kizer
Priority: NOR    
Version First Reported In: 24.12.2   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description uzivatel919 2025-03-08 11:23:22 UTC
SUMMARY

Past several months KCharSelect search is very laggy. This was not used to be and came with some functionality update.

STEPS TO REPRODUCE
1.  Open program.
2.  Seach for "square".

OBSERVED RESULT
- Results are searched even before letter is showed entered.
- Seach is terribly laggy.

EXPECTED RESULT
Smooth search experience as it was to be.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20250305
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.5-1-default (64-bit)
Graphics Platform: X11
Processors: 16 ร— AMD Ryzen 7 3800X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series
Comment 1 Christoph Feck 2025-03-08 12:49:07 UTC
Could you clarify "several months"? There is no commit in kcharselect or kwidgetsaddons since the around August 2024 releases that could affect search speed.
Comment 2 uzivatel919 2025-03-08 13:19:15 UTC
Surely, it could be even more ago. I was expecting fix as with next releases but this never happened,
Comment 3 John Kizer 2025-03-23 06:00:03 UTC
Hi - just to check, are you still observing that with version 24.12.3? Does it occur in a Wayland session as well? And, would it be possible to capture a screen recording of what you're seeing?

Thanks!
Comment 4 uzivatel919 2025-03-23 21:31:01 UTC
Unfortunately, I can't. I migrated recently to Leap because Tumbleweed drove me 2 times to recovery process after update lately.

Further more, I don't have KDE Wayland.

I can tell you that version 23.08.5 does not have this behavior. I thinks there are 2 issues:
- search begins immediately after pressing key, i.e. it starts before key is written to output field
- maybe because of previous or other reason listing is laggy, you can try 'sup' and 'super'
- performance in both version is different
Comment 5 Bug Janitor Service 2025-04-07 03:46:43 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!