Bug 521277

Summary:	discover wont start
Product:	[Applications] Discover	Reporter:	Jarl Gjessing <jarlgjessing>
Component:	discover	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	akselmo, aleixpol, kdedev, sitter
Priority:	NOR
Version First Reported In:	6.6.5
Target Milestone:	---
Platform:	Neon
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=507217 https://bugs.kde.org/show_bug.cgi?id=513569
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jarl Gjessing 2026-06-10 07:40:57 UTC

discovers notification icon appear. But I cannot open it.
This happens everytime, so it is easy to reproduce. I have tried apt reinstall the discover apps, I have tried removing discover cache and config.

Could be a duplicate to: https://bugs.kde.org/show_bug.cgi?id=420652

STEPS TO REPRODUCE
1. start computer
2. login
3. click on discover notification
2. wait :-) 

another option
1. start konsole
2. run plasma-discover
3. nothing happens

OBSERVED RESULT
option 1. Nothing happens
option 2. org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: true
adding empty sources model QStandardItemModel(0x63b922d6e2c0)

EXPECTED RESULT
Discover should show, listing updates

Operating System: KDE neon User Edition
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
Kernel Version: 6.17.0-35-generic (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-10850H CPU @ 2.70GHz
Memory: 48 GiB of RAM (46,7 GiB usable)
Graphics Processor 1: Intel® UHD Graphics
Graphics Processor 2: Quadro T2000
Manufacturer: Dell Inc.
Product Name: Precision 7550

Comment 1 Akseli Lahtinen 2026-06-10 10:33:11 UTC

Can't repro on KDE Linux. Potentially Neon bug?

Operating System: KDE Linux 2026-06-10
KDE Plasma Version: 6.7.80
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
Kernel Version: 7.0.11-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 6600

Comment 2 TraceyC 2026-06-10 18:08:08 UTC

I haven't seen this on either of my Solus systems either, with 6.6.5 and built from git-master

Can you try something?

First, kill any Discover process with
  killall plasma-discover

Then, try launching it with
  plasma-discover --backends flatpak,fwups

If it fails to launch, kill the processes again and try this:
  plasma-discover --backends fwupd,flatpak

Please let us know your results.

Comment 3 Jarl Gjessing 2026-06-11 08:23:42 UTC

(In reply to TraceyC from comment #2)
> I haven't seen this on either of my Solus systems either, with 6.6.5 and
> built from git-master
> 
> Can you try something?
> 
> First, kill any Discover process with
>   killall plasma-discover
> 
> Then, try launching it with
>   plasma-discover --backends flatpak,fwups
> 
> If it fails to launch, kill the processes again and try this:
>   plasma-discover --backends fwupd,flatpak
> 
> Please let us know your results.

Well, actually both options giving backends, works. Trying again without giving backends does not.
Looks like we're into something here :-)

Comment 4 TraceyC 2026-06-11 17:31:31 UTC

Thanks for checking that. It lets us know the flatpak and firmware backends are ok.

Now run this and let us know if Discover launches or not:
plasma-discover --backends fwupd,flatpak,kns-backend

Comment 5 Jarl Gjessing 2026-06-11 17:40:58 UTC

That worked too. Only one of the 3 backends you listed were with -backend, what that on purpose?
I actually tried with all 5 backends, both with and without -backend, and all of them worked.

Comment 6 TraceyC 2026-06-12 22:16:50 UTC

Thanks for the troubleshooting. The developers will need to take a closer look.

Comment 7 Harald Sitter 2026-06-14 17:10:21 UTC

Please get discover stuck.

Then run

killall -ABRT plasma-discover

This should bring up the crash dialog and you can report the stuck process from there. Possibly via the developer information page.

Comment 8 Bug Janitor Service 2026-06-29 03:47:52 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 9 Bug Janitor Service 2026-07-14 03:47:41 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.