chrome is installed from flatpak, and then install 3 pwa applications from chrome, none of them showing correct application icon
.desktop file in .local/share/application looks as
they are showing correct icons, I found that if I set system icon theme to Breeze, which shipped with kubuntu, PWA apps are showing correct icons. If set icon theme to a download icon theme, these PAW apps show chrome icon only
Comment 22
Latest Kde Neon and Chrome here, X11, same problem and an interesting information:
It all works properly when I use the icon sets that came with my default system (Breeze, breeze dark, oxygen) but it doesn’t when I use other icon themes that I installed later through plasma settings. Anyway I think I had the same problem with lubuntu 20.04
Please also notice that if you manually change the icon it will work as expected, doesn’t matter the icon set
also, chrome apps manually created by --app=www.duckduckgo.com work properly, doesn’t matter the icon set
Did you only test the Flatpak or also a version from the distribution package manager? As far as I can tell, the Chrome Flatpak correctly creates the PWA shortcut with the correct icons.
I only tried flatpak, flatpak now is my top priority source to install app.
Thanks for information, I think I met the same plasma bug as you mentioned. I will wait for it updates.
This bug is waiting on upstream Wayland updates, so it isn’t a Plasma bug per se – there’s currently no way to do it in Wayland. But the good news is that an extension has already been proposed and went through a surprisingly long debate about how to accomplish it. It’ll likely be a bit before it is available, but there is strong momentum.
I was having this issue on GNOME for months after switching my apps to Wayland to support fractional scaling. In addition to showing the wrong icon, attempting to switch to an open PWA window using a hotkey/wm switcher would re-launch a new instance of the app instead of focusing the open window.
The fix was to set the StartupWMClass in the .desktop file to match the true wmclass. E.g. set StartupWMClass to chrome-abcd...-Default instead of crx_abcd....
In my case, I used Looking Glass to find the true wmclass of the launched window, then I edited the StartupWMClass in the file to match it. This fixed both the icon and the ability to focus open windows.
Hopefully this is helpful even if it’s rather late!