Bug 416437 - Search shows entry with no text when searching for "tra" twice
Summary: Search shows entry with no text when searching for "tra" twice
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kwineffects (show other bugs)
Version: 5.17.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 421862 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-01-18 23:40 UTC by carl
Modified: 2021-06-18 03:03 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot of the bug (101.99 KB, image/png)
2020-01-18 23:40 UTC, carl
Details
Differene in model and qml state (118.85 KB, image/png)
2020-03-02 15:38 UTC, David Redondo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description carl 2020-01-18 23:40:10 UTC
Created attachment 125234 [details]
Screenshot of the bug

SUMMARY

Thes Desktop Effects KCM's search shows entry with no text.

STEPS TO REPRODUCE
1. Open Desktop Effects KCM
2. Search for tra
3. show 2 entries with no text 

OBSERVED RESULT

some of the result entries don't have text 

EXPECTED RESULT
all the result entries have text

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE thumbleweed
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.65
Qt Version: 5.13.2

ADDITIONAL INFORMATION
This bug doesn't appear every time :(
Comment 1 Filip Fila 2020-01-18 23:43:57 UTC
I was able to reproduce this as well.

It doesn't happen the first time I type in "tra", only the second time.

When the bug is triggered by typing in "tra", we can untrigger it by writing another letter and then deleting that letter. Then the "tra" search result doesn't show empty entries.

Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0
Comment 2 Nate Graham 2020-01-20 17:46:26 UTC
Can reproduce with Filip's instructions.
Comment 3 Vlad Zahorodnii 2020-01-21 12:54:14 UTC
Hmm, seems like there are some model issues

file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/main.qml:96:19: QML Effect: Binding loop detected for property "implicitHeight"
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/main.qml:96:19: QML Effect: Binding loop detected for property "implicitHeight"
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/main.qml:96:19: QML Effect: Binding loop detected for property "implicitHeight"
kf5.ki18n: "0 instead of 2 arguments to message {Author: %1\nLicense: ...} supplied before conversion."
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:115: TypeError: Value is undefined and could not be converted to an object
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:121:13: Unable to assign [undefined] to bool
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:38:13: Unable to assign [undefined] to bool
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:56:13: Unable to assign [undefined] to int
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:71:17: Unable to assign [undefined] to QString
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:78:17: Unable to assign [undefined] to QString
kf5.ki18n: "0 instead of 2 arguments to message {Author: %1\nLicense: ...} supplied before conversion."
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:115: TypeError: Value is undefined and could not be converted to an object
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:121:13: Unable to assign [undefined] to bool
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:38:13: Unable to assign [undefined] to bool
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:56:13: Unable to assign [undefined] to int
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:71:17: Unable to assign [undefined] to QString
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:78:17: Unable to assign [undefined] to QString
kf5.ki18n: "0 instead of 2 arguments to message {Author: %1\nLicense: ...} supplied before conversion."
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:115: TypeError: Value is undefined and could not be converted to an object
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:121:13: Unable to assign [undefined] to bool
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:38:13: Unable to assign [undefined] to bool
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:56:13: Unable to assign [undefined] to int
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:71:17: Unable to assign [undefined] to QString
file:///usr/share/kpackage/kcms/kcm_kwin_effects/contents/ui/Effect.qml:78:17: Unable to assign [undefined] to QString
Comment 4 David Edmundson 2020-01-21 12:57:20 UTC
I looked into this a bit last night.

Models are fine according to gammaray and modeltest

>QML Effect: Binding loop detected for property "implicitHeight"

I bodge fixed this, and then the problem went away; which makes some sense. If you can't control how many delegates to show you're going to get broken ones.

I would suggest putting any initial work there.

This loop happens because the ColumnLayout width changes, which relays out the text which changes the height. I don't know why that happens.
Comment 5 David Redondo 2020-03-02 15:37:52 UTC
>Models are fine according to gammaray and modeltest
Even if the model is fine, there is something wrong with how it is exposed to the qml side. By repeatedly searching for example for "squash" the category in which the effect appears changes. The correct one would be "Appearance" but I had it appear in accessibility for example.
Comment 6 David Redondo 2020-03-02 15:38:40 UTC
Created attachment 126549 [details]
Differene in model and qml state
Comment 7 Patrick Silva 2020-06-17 16:16:55 UTC
*** Bug 421862 has been marked as a duplicate of this bug. ***
Comment 8 Nate Graham 2021-06-17 19:57:39 UTC
I'm no longer able to reproduce this the way I could before. Can anyone still reproduce it in Plasma 5.22?
Comment 9 Filip Fila 2021-06-17 22:12:50 UTC
(In reply to Nate Graham from comment #8)
> I'm no longer able to reproduce this the way I could before. Can anyone
> still reproduce it in Plasma 5.22?

no
Comment 10 Nate Graham 2021-06-18 03:03:31 UTC
Guess it got fixed along the way somewhere. :)