Bug 502070 - Flatpak Application Icon Replaced with Wayland Logo in Window Switcher (Plasma 6 on Wayland)
Summary: Flatpak Application Icon Replaced with Wayland Logo in Window Switcher (Plasm...
Status: RESOLVED DUPLICATE of bug 459735
Alias: None
Product: kwin
Classification: Plasma
Component: tabbox (other bugs)
Version First Reported In: 6.3.3
Platform: Flatpak Linux
: NOR minor
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-27 14:29 UTC by abhi9ab
Modified: 2025-04-09 19:12 UTC (History)
2 users (show)

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


Attachments
Image of the bug (142.65 KB, image/jpeg)
2025-03-27 14:30 UTC, abhi9ab
Details

Note You need to log in before you can comment on or make changes to this bug.
Description abhi9ab 2025-03-27 14:29:10 UTC
## System Details:
- Distribution: Fedora 41
- Desktop Environment: KDE Plasma 6.3.3
- Session Type: Wayland
- Flatpak Version: 1.16.0

## Description:
When using Alt+Tab window switcher in large icon mode, the Zen Browser Flatpak application's icon is replaced with the Wayland logo. This occurs only in KDE Plasma 6 on Wayland. The same application shows its correct icon in GNOME 47.

## Steps to Reproduce:
- Install Zen Browser via Flatpak
- Switch to large icon mode in Task Switcher
- Use Alt+Tab to switch between windows
- Observe Zen Browser icon is replaced with Wayland logo

## Expected Behavior:
Zen flatpak application should display its own icon in the window switcher.

## Actual Behavior:
Zen Browser icon is replaced with Wayland logo.

## Additional Notes:
- Icon SVG is present and valid
- Icon displays correctly in other desktop environments
- Logo is correct in case of other Flatpak applications.
Comment 1 abhi9ab 2025-03-27 14:30:30 UTC
Created attachment 179787 [details]
Image of the bug
Comment 2 John Kizer 2025-04-09 19:12:47 UTC
Hi - merging this in with the existing bug report around the core issue of icon inconsistencies between the panel and task switcher. Thanks!

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