Bug 508075 - Discover store crashes when attempting to search the store
Summary: Discover store crashes when attempting to search the store
Status: RESOLVED DOWNSTREAM
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 5.24.7
Platform: Pop!_OS Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-08-10 05:47 UTC by Nonameshere1
Modified: 2025-08-10 06:33 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nonameshere1 2025-08-10 05:47:17 UTC
SUMMARY
Whenever I attempt to view any tabs in the Discover store aside from the 4 tabs at the bottom (Installed, Settings, About, and Updates) the application will hang for a few seconds before crashing to the desktop.

STEPS TO REPRODUCE
1. Open the Discover Store
2. Click on Applications, Application Addons, or Plasma Addons tab
3. Wait a few moments as the program hangs and then proceeds to crash

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Current Version, both Pop!OS and KDE Plasma

ADDITIONAL INFORMATION
For some reason this has been an issue with the Discover store for about as long as I have been using it as of around a year ago and I have no idea what is causing this issue
Comment 1 Bug Janitor Service 2025-08-10 06:33:40 UTC
Thank you for the bug report!

However Plasma 5.24.7 no longer receives updates or maintenance from KDE; active versions are 6.4 or newer. Please upgrade to an active version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one.

If you need help with Plasma 5.24.7, please contact your distribution, who bears the responsibility of providing help for older releases that are no longer receiving updates from KDE.

If you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.