Bug 2444046 - Incorrect KDE application launcher icon when user configures dark mode during initial setup
Summary: Incorrect KDE application launcher icon when user configures dark mode during...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-setup
Version: 44
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Neal Gompa
QA Contact:
URL:
Whiteboard: RejectedBlocker AcceptedFreezeException
Depends On:
Blocks: F44FinalFreezeException, FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2026-03-03 02:57 UTC by Derek Enz
Modified: 2026-03-16 17:44 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
KDE in dark mode (846.59 KB, image/png)
2026-03-16 14:06 UTC, Kamil Páral
no flags Details
applying theme (424.33 KB, image/png)
2026-03-16 14:07 UTC, Kamil Páral
no flags Details

Description Derek Enz 2026-03-03 02:57:21 UTC
Description of problem: After installation of Fedora KDE 44 Beta 1.2, the KDE application launcher displays the incorrect logo/icon. Instead of the Fedora logo we see the default KDE logo.


Version-Release number of selected component (if applicable):
Fedora 44 KDE Beta 1.2
KDE Plasma 6.6.1
KDE Frameworks 6.23.0
QT version 6.10.2



How reproducible: Install a fresh Fedora 44 KDE Beta 1.2 image.


Steps to Reproduce:
1.Boot from the Live media. 
2.Run the install of Fedora 44 Beta 1.2
3.Reboot

Actual results:
The default KDE logo is displayed for the application launcher.

Expected results:
Should see the Fedora logo instead.

Additional info: NOTE: Booting and running the Live media, the logo is correct.

Its after the install process where the logo reverts back to default KDE.

Comment 1 Neal Gompa 2026-03-03 12:00:32 UTC
I can't reproduce this with the default flow, but I do see it if I toggle dark mode. So something is misfiring for dark mode.

What is *supposed* to happen is that the plasmoid setup scripts for the application launcher should run on first login with this.

https://pagure.io/fedora-kde/kde-settings/blob/rawhide/f/usr/share/plasma/look-and-feel/org.fedoraproject.fedoradark.desktop/contents/plasmoidsetupscripts

But they are obviously not firing. I'm not sure why though.

Comment 4 Neal Gompa 2026-03-03 14:27:20 UTC
I'm not sure what's up with Forgejo there, but it does resolve on the real system:

ngompa@fedora ~> ls /usr/share/plasma/look-and-feel/org.fedoraproject.fedoradark.desktop/contents/plasmoidsetupscripts/ -hal
total 12K
drwxr-xr-x. 1 root root 154 Feb 23 06:25 ./
drwxr-xr-x. 1 root root 134 Feb 23 06:25 ../
lrwxrwxrwx. 1 root root 100 Jan 12 09:48 org.kde.plasma.kickerdash.js -> ../../../org.fedoraproject.fedora.desktop/contents/plasmoidsetupscripts/org.kde.plasma.kickerdash.js
lrwxrwxrwx. 1 root root  96 Jan 12 09:48 org.kde.plasma.kicker.js -> ../../../org.fedoraproject.fedora.desktop/contents/plasmoidsetupscripts/org.kde.plasma.kicker.js
lrwxrwxrwx. 1 root root  97 Jan 12 09:48 org.kde.plasma.kickoff.js -> ../../../org.fedoraproject.fedora.desktop/contents/plasmoidsetupscripts/org.kde.plasma.kickoff.js
ngompa@fedora ~> file -L /usr/share/plasma/look-and-feel/org.fedoraproject.fedoradark.desktop/contents/plasmoidsetupscripts/org.kde.plasma.kickerdash.js
/usr/share/plasma/look-and-feel/org.fedoraproject.fedoradark.desktop/contents/plasmoidsetupscripts/org.kde.plasma.kickerdash.js: ASCII text
ngompa@fedora ~> file -L /usr/share/plasma/look-and-feel/org.fedoraproject.fedoradark.desktop/contents/plasmoidsetupscripts/org.kde.plasma.kicker.js
/usr/share/plasma/look-and-feel/org.fedoraproject.fedoradark.desktop/contents/plasmoidsetupscripts/org.kde.plasma.kicker.js: ASCII text
ngompa@fedora ~> file -L /usr/share/plasma/look-and-feel/org.fedoraproject.fedoradark.desktop/contents/plasmoidsetupscripts/org.kde.plasma.kickoff.js
/usr/share/plasma/look-and-feel/org.fedoraproject.fedoradark.desktop/contents/plasmoidsetupscripts/org.kde.plasma.kickoff.js: ASCII text

Comment 5 Fedora Blocker Bugs Application 2026-03-12 02:57:56 UTC
Proposed as a Blocker for 44-final by Fedora user ngompa using the blocker tracking app because:

 It violates the criteria on "first boot experience" and "default panel functionality" as the result of toggling dark mode in Plasma Setup results in broken branding and the wrong icon for the application menu, which is very unexpected.

Comment 6 Kamil Páral 2026-03-16 14:04:42 UTC
Here are some additional information that I found out:

* Everything looks correct in default values ("Fedora theme"). The KDE main button has a Fedora logo.
* One way to reproduce this is to enable Dark Mode in KDE initial setup dialog.
* Another way to reproduce this is to go to System Settings -> Colors & Themes -> Global Theme and switch to "Fedora Dark". However, the bug is only reproduced if you apply the theme to "Desktop and window layout", which is disabled by default. The KDE main button loses the Fedora logo branding. If you don't enable "Desktop and window layout" checkbox, you have a dark mode without the bug.
* Vice versa, you can undo this bug by switching to "Fedora" theme while enabling "Desktop and window layout" checkbox, and then optionally switching to "Fedora Dark" theme without enabling "Desktop and window layout" checkbox".

Comment 7 Kamil Páral 2026-03-16 14:06:02 UTC
Created attachment 2133647 [details]
KDE in dark mode

This is how KDE appears in dark mode, when the bug is visible (main button in bottom left doesn't have Fedora logo).

Comment 8 Kamil Páral 2026-03-16 14:07:33 UTC
Created attachment 2133648 [details]
applying theme

This is how you fix the issue when applying Fedora theme, enable "Desktop and window layout" checkbox. Or don't enable it to have the dark mode without the problem.

Comment 9 Lukas Ruzicka 2026-03-16 17:44:12 UTC
AGREED RejectedFinalBlocker AcceptedFinalFreezeException

Discussed at the 2026-03-16 (blocker / freeze exception) review meeting:

There are differing opinions on this, but we noted that the existing criteria were written for 'artwork' that changes per-release and were not meant to cover permanent branding issues. There's some support for adding branding criteria, but the narrow consensus was this is probably a minor enough issue that it shouldn't constitute a blocker even if we do write branding criteria. We're open to reconsidering this if a broad swell of folks who weren't present at the meeting are concerned. It's accepted as an FE as a visible issue in a blocking desktop that can't be resolved with an update.

https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-03-16/f44-blocker-review.2026-03-16-16.01.log.txt


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