Bug 501333

Summary:	One day, plasma-discover just crashes immediately upon selecting.
Product:	[Applications] Discover	Reporter:	RinCasi <miatsukichan>
Component:	discover	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	aleixpol, nate
Priority:	NOR
Version First Reported In:	6.3.2
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	coredump of plasma-discover

Description RinCasi 2025-03-11 07:50:51 UTC

Steps to reproduce:

Operating System: Nobara Linux 41
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.5-200.nobara.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600 6-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor 1: AMD Radeon Graphics
Graphics Processor 2: llvmpipe
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B650 GAMING X AX


Don't exactly know how or why it started like this.

I was going to go install OBS from flathub via Discover only to find out Discover no longer works.

kcrash file reports back empty.

Opening plasma-discover with the terminal only prints out the following information:

``Warning: Program '/usr/bin/plasma-discover' crashed.``

No other information or logs about the crash are found afterwards.

Reinstalling plasma-discover does not fix the issue.

However, I do update my system daily using /usr/bin/nobara-updater. Perhaps an update broke plasma-discover somewhere before?

Comment 1 Nate Graham 2025-03-11 22:29:51 UTC

If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the `coredumpctl` command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!

Comment 2 RinCasi 2025-03-13 01:39:41 UTC

Created attachment 179359 [details]
coredump of plasma-discover

Comment 3 Nate Graham 2025-03-13 04:35:24 UTC


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