Bug 2437944 - The launcher does not start properly on Fedora 44
Summary: The launcher does not start properly on Fedora 44
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-desktop
Version: 44
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: BetaBlocker, F44BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2026-02-09 11:48 UTC by Lukas Ruzicka
Modified: 2026-02-09 20:45 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-02-09 20:45:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Photo witht the error (882.80 KB, image/png)
2026-02-09 11:48 UTC, Lukas Ruzicka
no flags Details

Description Lukas Ruzicka 2026-02-09 11:48:10 UTC
On KDE 44, the 20260209 nightly, the launcher does not start properly. Instead, it shows a dialogue reporting the errors (see attachment). You can also see the problem in the openQA - https://openqa.stg.fedoraproject.org/tests/5882570#step/basic_networking_client/9.

Reproducible: Always

Steps to Reproduce:
1. Install KDE Live from 20260209.
2. Click on the launcher icon.
3. See the results.
Actual Results:
Launcher does not start.

Expected Results:
Launcher should start normally.

Comment 1 Lukas Ruzicka 2026-02-09 11:48:55 UTC
Created attachment 2128760 [details]
Photo witht the error

Comment 2 Fedora Blocker Bugs Application 2026-02-09 11:57:36 UTC
Proposed as a Blocker for 44-beta by Fedora user lruzicka using the blocker tracking app because:

 This violates the criteria for Desktop panel.

https://fedoraproject.org/wiki/Fedora_44_Beta_Release_Criteria#Desktop_panel

Comment 3 Lukas Ruzicka 2026-02-09 12:54:23 UTC
The above problem is not seen on the previous nightly, i.e. 20260208, so the problem must have appeared in the last nightly.

Comment 4 Adam Williamson 2026-02-09 20:45:59 UTC
https://bodhi.fedoraproject.org/updates/FEDORA-2026-9c3da3e12e fixes this.


Note You need to log in before you can comment on or make changes to this bug.