Bug 482906 - Certain window icons disappear in the icons-only task manager
Summary: Certain window icons disappear in the icons-only task manager
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager widgets (other bugs)
Version First Reported In: 6.0.1
Platform: Arch Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-08 18:37 UTC by sillybegani
Modified: 2024-03-10 20:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description sillybegani 2024-03-08 18:37:09 UTC 
SUMMARY
On KDE Plasma 6.0.1, certain apps don't show icons in the icons-only task manager. An example app is Ghidra, which I have tested multiple versions of, and they are all affected by this. This only started to happen with the Plasma 6.0 upgrade, and was fine beforehand.

STEPS TO REPRODUCE
1. Download the latest version of Ghidra from its GitHub Releases page, https://github.com/NationalSecurityAgency/ghidra/releases
2. Open Ghidra using the "ghidraRun" shell file provided in its download.
3. Once the main window has finished loading, the icon in the task manager will have disappeared.

OBSERVED RESULT
Ghidra's icon in the manager will have disappeared, and subsequent windows spawned by Ghidra disappear from the taskbar if another window is created by it.

EXPECTED RESULT
All icons should stay where they are and not disappear.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kernel version 6.7.8-arch1-1
(available in About System)
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Comment 1 Nate Graham 2024-03-10 20:48:51 UTC 
This is a bug in the app itself. Most likely it's either not setting a .desktop file properly, or else its .desktop file is malformed, or else it's changing its WM_CLASS value at runtime. All of those would need to be fixed in the app itself.

The reason this started happening in 6.0 is most likely because you're using Wayland now, which is stricter about this stuff than X11 was. On X11; those things were tolerated; on Wayland, no.