Bug 2411717

Summary:	[Regression] krunner fails on fedora 43, downgrade fixes the crash
Product:	[Fedora] Fedora	Reporter:	Christian Stadelmann <fedora>
Component:	kf6-krunner	Assignee:	Steve Cossette <farchord>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	43	CC:	emelenas, farchord, kde-sig, klarnorbert, matkaz1003
Target Milestone:	---	Keywords:	Desktop, Regression
Target Release:	---
Hardware:	Unspecified
OS:	Linux
URL:	https://discussion.fedoraproject.org/t/no-application-launcher-load-after-upgrade-to-fedora-43/171374
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Christian Stadelmann 2025-11-01 11:34:47 UTC

Multiple people have reported crashes when starting krunner on Fedora 43 (see attached thread).

A downgrade + reboot helped the users who ran into that problem.

Reproducible: Always

Steps to Reproduce:
1. Update to Fedora 43 with krunner 6.19.0-1
2. Start krunner application launcher
3.
Actual Results:
Application launcher crashes

The error messages look like this:
```
file:///usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/main.qml:21:1: Cannot load library /usr/lib64/qt6/qml/org/kde/plasma/private/kicker/libkickerplugin.so: /lib64/libKF6Runner.so.6: undefined symbol: _ZN14KWaylandExtras18xdgActivationTokenEP7QWindowRK7QString
```

Expected Results:
No crash.

Comment 1 Christian Stadelmann 2025-11-01 11:35:26 UTC

It seems like the URL got lost, here it is: https://discussion.fedoraproject.org/t/no-application-launcher-load-after-upgrade-to-fedora-43/171374

Comment 2 Enrique Meléndez 2025-11-01 13:37:10 UTC

That is correct, I have had the same issue after upgrading to Fedora 43 from Fedora 42. Downgrading to kf6-krunner-6.18-0.1 solves the issue. However, Fedora 42 was already running on version 6.19, so maybe some dependencies went awry.

Comment 3 Norbert 2025-11-01 14:57:53 UTC

I can also confirm this issue, downgrading mentioned package solves the problem.

Comment 4 Steve Cossette 2025-11-01 16:36:46 UTC

https://bodhi.fedoraproject.org/updates/FEDORA-2025-0c9aa5a428 This is very likely to be the fix for the issue. Once this goes live, you should be able to do a full dnf update and get things lined up properly. We missed a package rebuild which caused problems for some users.