Bug 447080 - Discover crashes when clicking on certain search results
Summary: Discover crashes when clicking on certain search results
Status: RESOLVED DUPLICATE of bug 448784
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: 5.23.4
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-16 15:54 UTC by NIk
Modified: 2022-03-25 15:31 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description NIk 2021-12-16 15:54:59 UTC 
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. Open Discover
2. Search for QT Creator
3. Click on the result

OBSERVED RESULT
Discover hangs, all cores pegged at 100%

EXPECTED RESULT
Should open the page of QT Creator (or any other affected app) normally

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Opensuse Tumbleweed 20211214
(available in About System)
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 NIk 2021-12-16 16:09:29 UTC 
Edit: When opened in terminal, I get this error a thousand times:
file:///usr/lib64/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:98:27: QML ScrollBar: Binding loop detected for property "visible"
Comment 2 Nate Graham 2021-12-16 19:10:37 UTC 
As the message says:

***
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
***
Comment 3 Aleix Pol 2021-12-17 01:06:30 UTC 

*** This bug has been marked as a duplicate of bug 446934 ***
Comment 4 Nate Graham 2022-03-25 15:31:58 UTC 

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