Bug 480631 - Searching through effects list breaks the list
Summary: Searching through effects list breaks the list
Status: RESOLVED DUPLICATE of bug 480594
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kwineffects (show other bugs)
Version: 5.93.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-01-31 21:17 UTC by dominik.klementowski
Modified: 2024-02-02 17:38 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dominik.klementowski 2024-01-31 21:17:45 UTC
SUMMARY
I recorded a short video showing the issue. When I look for effects by typing phrases, the list breaks oddly.   It only happens when there are some results and it gets more broken the more times I remove the input field and type something again.

It appears to be maybe be related to localization (based on what I see on the list while searching, but I don't know), mine is pl_PL.UTF-8. Fractional scaling doesn't seem to be related as it reproduces with 100% scale.


STEPS TO REPRODUCE
1. Go to the effects page
2. Type something with results
3. Remove what you just typed and goto 2.

OBSERVED RESULT
Broken effects list

EXPECTED RESULT
Not so broken effects list

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  Arch Linux, kde-unstable/core-testing
(available in About System)
KDE Plasma Version:  5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
Demo video:  https://www.dropbox.com/scl/fi/b120f2ugpr1x3u9b0x6f1/effects-list.mkv?rlkey=i8fsmr8ks2xg3rez92i0c5sl4&dl=0
Comment 1 Vlad Zahorodnii 2024-01-31 21:37:09 UTC
I can reproduce it when using en_US.UTF-8 too
Comment 2 Bug Janitor Service 2024-01-31 22:02:59 UTC
A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/5082
Comment 3 Nate Graham 2024-02-02 17:38:39 UTC

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