Bug 458651 - ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width"
Summary: ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "...
Status: RESOLVED DUPLICATE of bug 459284
Alias: None
Product: frameworks-kirigami
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.97.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: Not decided
Assignee: kdelibs bugs
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2022-09-02 22:20 UTC by Nathan Price
Modified: 2022-10-31 23:52 UTC (History)
2 users (show)

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

Attachments
Screen shot of journalctl -f (309.84 KB, image/png)
2022-09-02 22:20 UTC, Nathan Price 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nathan Price 2022-09-02 22:20:52 UTC 
Created attachment 151793 [details]
Screen shot of journalctl -f

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. go to system settings -> about this system
2. click "show more info"


OBSERVED RESULT

"kinfocenter[153181]: file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:189:9: QML MouseArea: Binding loop detected for property "width""

EXPECTED RESULT
No system log warnings

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.19.6-arch1-1 (64-bit)
Graphics Platform: Wayland


ADDITIONAL INFORMATION
I have several more areas in the system settings that throw similar errors in the system log. The screenshot shows several lines of these warnings - the entire photo is from one button press. I can open a bunch of bug reports if you want, but I figure I'd ask before clogging up the que.
Comment 1 Nate Graham 2022-10-31 23:52:27 UTC 
*** This bug has been marked as a duplicate of bug 459284 ***