We can have different icons for chrome apps, but when they are executed, they assume chrome browser icon identity. Reproducible: Always Steps to Reproduce: 1. install any app, like whatschrome app 2. hold and drag the chrome app from kde launcher to the icon only task manager 3. open it Actual Results: the app instance turns into an chrome instance Expected Results: it stay with it icons identification. The best approach is to turn possible that an icon identity be ruled by windows class, its very consistent and many users utilize this to for example set more uniform windows decoration for chrome apps.
Created attachment 96759 [details] exemple of a chrome app behavior
Git commit 92efc6ca6ec3c1c1c34a777c470337d4fde4b0c1 by Kai Uwe Broulik. Committed on 06/06/2016 at 20:05. Pushed by broulik into branch 'master'. [Libtaskmanager] Add support for regular expression mapping This allows more complicated rules, useful for matching Chrome webapps to their respective desktop file where we need to change crx_foo to chrome-foo-default. Related: bug 356609 FIXED-IN: 5.7.0 Differential Revision: https://phabricator.kde.org/D1673 M +6 -0 libtaskmanager/taskmanagerrulesrc M +47 -0 libtaskmanager/xwindowtasksmodel.cpp http://commits.kde.org/plasma-workspace/92efc6ca6ec3c1c1c34a777c470337d4fde4b0c1
This issue happens for me in Wayland in Plasma 5.20 and 5.21. Switching to X11 it works as expected.
*** Bug 431288 has been marked as a duplicate of this bug. ***
*** Bug 424613 has been marked as a duplicate of this bug. ***
*** Bug 439104 has been marked as a duplicate of this bug. ***
*** Bug 447845 has been marked as a duplicate of this bug. ***
This is an upstream issue which will be fixed by https://chromium-review.googlesource.com/c/chromium/src/+/3383817, once it's merged.
well, it's not really strictly an upstream issue. Chrome adding support for our non-standard hint is nice and fixed the issue, but there's still a bug in our XWayland support (as described in https://bugs.kde.org/show_bug.cgi?id=447845) that needs fixing
OK, re-opened that.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1396
My two pennies worth: Just updated Chrome to v99. I use Ozone/Wayland backend. This release sets proper Icons for Chrome apps for me. Tested with Spotify and Tidal. The icon is also properly set for all effects presenting window with its icon visible, i.e. the overview effect.
Confirming this works with both Chrome 99.0.4844.51 and Brave 1.36.111 - the icons work as expected.
Maybe I have a similar problem https://bugs.kde.org/show_bug.cgi?id=452005
Git commit 7b94f03c0f5fec052454a1c8d6faec0aff2ce0cb by Nicolas Fella. Committed on 14/04/2022 at 11:14. Pushed by nicolasfella into branch 'master'. [libtaskmanager] Consider resource name for XWayland windows Like we do in an X11 session Related: bug 447845 M +1 -1 libtaskmanager/waylandtasksmodel.cpp https://invent.kde.org/plasma/plasma-workspace/commit/7b94f03c0f5fec052454a1c8d6faec0aff2ce0cb
Sorry to reopen but I still have not the right icon on X11 on Plasma 5.24.5, google chrome 102
The KDE fix is in Plasma 5.25. Please re-open only once you're using that version, if it's still happening.
Created attachment 149416 [details] attachment-22754-0.html sorry, I didn't understand, my mistake
This is still happening for me with both Brave and MS Edge. Microsoft Edge Version 102.0.1245.44 (Official build) (64-bit) Brave Version 1.39.122 Chromium: 102.0.5005.115 (Official Build) (64-bit) Works as expected on X11. Operating System: openSUSE Tumbleweed 20220614 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Graphics Platform: Wayland
on X11 the bug is still there with google chrome
(In reply to Guido from comment #20) > on X11 the bug is still there with google chrome Operating System: Manjaro Linux KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.5-1-MANJARO (64-bit) Graphics Platform: X11
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
Hello, same problem : Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.7-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland What's weird it's that when app is starting, icon is appearing correctly, then it is replaced with the Chrome's one. I'm using Kinoite but tested using Google Chrome (105.0.5195.102) installed via RPM and Ungoogled Chromium (105.0.5195.102) installed via flatpak. Thank you
Git commit 1e6180d8e75b10e97926d308fe9df38b710a91fe by Mladen Milinkovic. Committed on 14/10/2022 at 13:52. Pushed by nicolasfella into branch 'master'. Handle multiple desktop files with different StartupWMClass Some system installed apps define common/default StartupWMClass in system-installed .desktop file. Application then create extra .desktop files in user's local applications directory with additional (more specific) StartupWMClass entry. This patch will match specific window class (WM_CLASS instance name) before matching common window class (WM_CLASS class name). See: https://www.x.org/releases/X11R7.7/doc/xorg-docs/icccm/icccm.html#WM_CLASS_Property M +7 -7 libtaskmanager/tasktools.cpp https://invent.kde.org/plasma/plasma-workspace/commit/1e6180d8e75b10e97926d308fe9df38b710a91fe
Git commit 735f350c1506bb06e87fdd9a151eed323384452e by Nicolas Fella, on behalf of Mladen Milinkovic. Committed on 14/10/2022 at 14:12. Pushed by nicolasfella into branch 'Plasma/5.26'. Handle multiple desktop files with different StartupWMClass Some system installed apps define common/default StartupWMClass in system-installed .desktop file. Application then create extra .desktop files in user's local applications directory with additional (more specific) StartupWMClass entry. This patch will match specific window class (WM_CLASS instance name) before matching common window class (WM_CLASS class name). See: https://www.x.org/releases/X11R7.7/doc/xorg-docs/icccm/icccm.html#WM_CLASS_Property (cherry picked from commit 1e6180d8e75b10e97926d308fe9df38b710a91fe) M +7 -7 libtaskmanager/tasktools.cpp https://invent.kde.org/plasma/plasma-workspace/commit/735f350c1506bb06e87fdd9a151eed323384452e
KDE Plasma 5.26.1 did not fix this issue for me.
[Reopening according to the comment]
(In reply to keydieyeah from comment #26) > KDE Plasma 5.26.1 did not fix this issue for me. What OS are you using? Wayland or X11? Google Chrome or Chromium? thanks
(In reply to Mladen Milinkovic, Max from comment #28) > (In reply to keydieyeah from comment #26) > > KDE Plasma 5.26.1 did not fix this issue for me. > > What OS are you using? > Wayland or X11? > Google Chrome or Chromium? > thanks I'm using Arch Linux/Wayland/NVIDIA. I tried it with Brave and Chromium from the Arch repository. I also tried with Chrome and Edge in Flathub repository. I'm having the same problem with all of them. When the web application and browser are open at the same time, they merge into a single icon. I don't know if this is just happening to me. Thanks.
(In reply to keydieyeah from comment #29) > (In reply to Mladen Milinkovic, Max from comment #28) > > (In reply to keydieyeah from comment #26) > > > KDE Plasma 5.26.1 did not fix this issue for me. > > > > What OS are you using? > > Wayland or X11? > > Google Chrome or Chromium? > > thanks > > I'm using Arch Linux/Wayland/NVIDIA. > I tried it with Brave and Chromium from the Arch repository. I also tried > with Chrome and Edge in Flathub repository. > I'm having the same problem with all of them. When the web application and > browser are open at the same time, they merge into a single icon. > I don't know if this is just happening to me. > Thanks. The last patch (5.26.1) fixed it for me with Brave/Chromium from Arch repository - only difference from you is I'm still using X11. Will try tomorrow with Wayland and hopefully reproduce/fix it, if no one else is looking into it already.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2264
Also it's not resolved for me (Chrome, KDE Neon 5.26.2 wayland) Every Chrome app goes under the same icon. The behavior is normal under X11
It has not fixed for me either. Neon 5.26.2, all chrome app icons appear under the browser's icon.
Additional KWin changes are required to fully fix it for some people; see https://invent.kde.org/plasma/kwin/-/merge_requests/3113. That's only in Plasma 5.27, so folks who are still affected will have to wait until then.
FYI, you can use window rules to set the correct icon, as a temporary fix before the above mentioned 5.27 release: 1. System Settings - Window Management - Window Rules - Add New... 2. Bring the buggy app window side-by-side with system settings. 3. Click "Detect Window Properties..." in the bottom. 4. Move the crosshair to the buggy window and click. 5. Click "Window class (application)". 6. Click "Add Property..." in the bottm left. 7. Click "Desktop file name". 8. Enter the base name of the desktop file (e.g. for vscode, "visual-studio-code"). 9. Click "Apply". 10. The icon should be fixed immediately.
(In reply to Jin Liu from comment #35) > FYI, you can use window rules to set the correct icon, as a temporary fix > before the above mentioned 5.27 release: > > 1. System Settings - Window Management - Window Rules - Add New... > 2. Bring the buggy app window side-by-side with system settings. > 3. Click "Detect Window Properties..." in the bottom. > 4. Move the crosshair to the buggy window and click. > 5. Click "Window class (application)". > 6. Click "Add Property..." in the bottm left. > 7. Click "Desktop file name". > 8. Enter the base name of the desktop file (e.g. for vscode, > "visual-studio-code"). > 9. Click "Apply". > 10. The icon should be fixed immediately. You can find the base name of the desktop file by right-clicking on the app icon in Kickoff and select "Edit".
I'm reopening this since I can reproduce it on a fully updated Neon Unstable (Plasma 5.26.80, Frameworks 5.100.0, and QT 5.15.7) and Chrome Dev (109.0.5410.0). It's possible to trigger the bug if you launch a web application while the browser is already open. If the browser is closed and you open a web application and then open the browser, the web application will keep its own icon and the browser will also have its own icon (as expected), however, if you open any other web application it will be grouped with the browser window. Mind you this is while running the browser in its default XWayland mode. If you make the browser open in native Wayland mode (go to chrome:flags and change the flag "Preferred Ozone platform" to Wayland and restart the browser) the behavior will change. Now, opening the browser will make it always have a generic Wayland icon, but web apps will have their own icon (as expected), no matter if the browser is opened first or not.
I see the problem. The problem isn't that the web app has the wrong icon, that has been fixed, but web apps and normal windows are grouped together. Manually ungrouping them shows that each has the appropriate icon
For me changing Chrome's flag to wayland solved the issue. Now the webapps have their respective icons as expected
Confirmed. Running chrome://flags searching for wayland and enabling the 2 flags and restart chrome, means that the app opens correctly.
*** Bug 381266 has been marked as a duplicate of this bug. ***
Confirmed for me too. Setting #ozone-platform-hint at chrome://flags solved it on KDE with Wayland
*** Bug 449045 has been marked as a duplicate of this bug. ***
*** Bug 474760 has been marked as a duplicate of this bug. ***
*** Bug 481976 has been marked as a duplicate of this bug. ***
Running chrome://flags searching for wayland I find only one setting, Preferred Ozone platform. If I set it to Wayland or Auto, this issue stops occurring. However, another issuer occurs instead, see bug 482258
This is still happening for me running: KDE Plasma Version - 6.0.5 KDE Frameworks Verion - 6.4.0 Chromium - 127.0.6533.119 Arch Linux Setting "Preferred Ozone platform" to anything other than X11 (or Default) makes so opening a pinned task creates a transparent window with the wayland logo with crazy artifacts. If I can provide any more logs or info please inform me which, I will gladly provide them.
The artifacts were solved by removing "--profile-directory=Default" from the webapp command but it still creates a new window with the wrong icon, for reference my command is, that run with artifacts: "chromium --class=discord.com,Chromium-browser --profile-directory=Default --app=https://discord.com" running the following with Preferred Ozone platform set to wayland as suggested works but do not resolve the issue as it creates a new window with the wayland logo, not over the existing pin: "chromium --class=discord.com,Chromium-browser --app=https://discord.com"
(In reply to arthur.caccavo from comment #48) > The artifacts were solved by removing "--profile-directory=Default" from the > webapp command but it still creates a new window with the wrong icon, for > reference my command is, that run with artifacts: > > "chromium --class=discord.com,Chromium-browser --profile-directory=Default > --app=https://discord.com" > > running the following with Preferred Ozone platform set to wayland as > suggested works but do not resolve the issue as it creates a new window with > the wayland logo, not over the existing pin: > "chromium --class=discord.com,Chromium-browser --app=https://discord.com" running "chromium --app=https://discord.com" in the terminal with Preferred Ozone platform set to wayland creates non-pinnable window with the wayland logo and produces the following output: [35995:35995:0823/173029.358652:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=SCANOUT [35995:35995:0823/173029.358743:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=GPU_READ [35995:35995:0823/173029.358776:ERROR:shared_image_factory.cc(1039)] CreateSharedImage: could not create backing. [35995:35995:0823/173029.358804:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=SCANOUT [35995:35995:0823/173029.358827:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=GPU_READ [35995:35995:0823/173029.358850:ERROR:shared_image_factory.cc(1039)] CreateSharedImage: could not create backing. [35995:35995:0823/173029.358872:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=SCANOUT [35995:35995:0823/173029.358894:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=GPU_READ [35995:35995:0823/173029.358915:ERROR:shared_image_factory.cc(1039)] CreateSharedImage: could not create backing. [35995:35995:0823/173029.358948:ERROR:shared_image_manager.cc(223)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox. [35995:35995:0823/173029.358995:ERROR:gpu_service_impl.cc(1147)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly. [35936:35936:0823/173029.364939:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=8704 [36091:36091:0823/173029.525281:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=SCANOUT [36091:36091:0823/173029.525346:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=GPU_READ [36091:36091:0823/173029.525380:ERROR:shared_image_factory.cc(1039)] CreateSharedImage: could not create backing. [36091:36091:0823/173029.525410:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=SCANOUT [36091:36091:0823/173029.525437:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=GPU_READ [36091:36091:0823/173029.525463:ERROR:shared_image_factory.cc(1039)] CreateSharedImage: could not create backing. [36091:36091:0823/173029.525493:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=SCANOUT [36091:36091:0823/173029.525519:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=GPU_READ [36091:36091:0823/173029.525544:ERROR:shared_image_factory.cc(1039)] CreateSharedImage: could not create backing. [36091:36091:0823/173029.525580:ERROR:shared_image_manager.cc(223)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox. [36091:36091:0823/173029.525629:ERROR:gpu_service_impl.cc(1147)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly. [35936:35936:0823/173029.531762:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=8704 [36144:36144:0823/173029.642992:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=SCANOUT [36144:36144:0823/173029.643048:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=GPU_READ [36144:36144:0823/173029.643090:ERROR:shared_image_factory.cc(1039)] CreateSharedImage: could not create backing. [36144:36144:0823/173029.643127:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=SCANOUT [36144:36144:0823/173029.643154:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=GPU_READ [36144:36144:0823/173029.643182:ERROR:shared_image_factory.cc(1039)] CreateSharedImage: could not create backing. [36144:36144:0823/173029.643216:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=SCANOUT [36144:36144:0823/173029.643242:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= RGBA_8888 and usage=GPU_READ [36144:36144:0823/173029.643267:ERROR:shared_image_factory.cc(1039)] CreateSharedImage: could not create backing. [36144:36144:0823/173029.643313:ERROR:shared_image_manager.cc(223)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox. [36144:36144:0823/173029.643351:ERROR:gpu_service_impl.cc(1147)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly. [35936:35936:0823/173029.649134:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=8704 [36030:7:0823/173029.718623:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. [0823/173029.736091:ERROR:elf_dynamic_array_reader.h(64)] tag not found [36030:10:0823/173029.745990:ERROR:shared_image_interface_proxy.cc(130)] Buffer handle is null. Not creating a mailbox from it. [36030:10:0823/173029.746042:ERROR:one_copy_raster_buffer_provider.cc(348)] Creation of StagingBuffer's SharedImage failed. [36030:10:0823/173029.746081:ERROR:shared_image_interface_proxy.cc(130)] Buffer handle is null. Not creating a mailbox from it. [36030:10:0823/173029.746101:ERROR:one_copy_raster_buffer_provider.cc(348)] Creation of StagingBuffer's SharedImage failed. [36030:10:0823/173029.746133:ERROR:shared_image_interface_proxy.cc(130)] Buffer handle is null. Not creating a mailbox from it. [36030:10:0823/173029.746153:ERROR:one_copy_raster_buffer_provider.cc(348)] Creation of StagingBuffer's SharedImage failed. [36030:10:0823/173029.746181:ERROR:shared_image_interface_proxy.cc(130)] Buffer handle is null. Not creating a mailbox from it. [36030:10:0823/173029.746200:ERROR:one_copy_raster_buffer_provider.cc(348)] Creation of StagingBuffer's SharedImage failed. [36030:10:0823/173029.746228:ERROR:shared_image_interface_proxy.cc(130)] Buffer handle is null. Not creating a mailbox from it. [36030:10:0823/173029.746246:ERROR:one_copy_raster_buffer_provider.cc(348)] Creation of StagingBuffer's SharedImage failed. [35936:35936:0823/173030.109220:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=133 running on non-wayland mode produces no output whatsoever
Can you try again with latest kwin git master? https://invent.kde.org/plasma/kwin/-/commit/193c069b885b60de3d4f4fa18df9841849a4d325 should fix this issue, at least it works here with regular Chrome in X11 mode and some PWAs
That's great! Let's call it fixed. For folks who still experience issues, let's get new bug reports, as they may have different root causes.
*** Bug 494593 has been marked as a duplicate of this bug. ***